How to install on a PC Engines APU1C board?
-
And if I leave the USB stick with TinyCore Linux attached to the system, it happily boots pfSense (SD card is first in the boot order) and goes all the way through the interface setup. Then I could use the webGUI, wizard, reboot - everything.
I shutdown and removed the USB stick - now I have the mountroot problem.
Put the USB stick back, and it boots fine.
So the USB stick slows something down in the boot sequence that lets it work. I guess I will leave the USB stick inserted for now, while I play. -
And if I leave the USB stick with TinyCore Linux attached to the system, it happily boots pfSense (SD card is first in the boot order) and goes all the way through the interface setup. Then I could use the webGUI, wizard, reboot - everything.
I shutdown and removed the USB stick - now I have the mountroot problem.
Put the USB stick back, and it boots fine.
So the USB stick slows something down in the boot sequence that lets it work. I guess I will leave the USB stick inserted for now, while I play.Just out of curiosity, what happens if you use 20000 instead of 10000?
-
I moved on to the 2nd APU1C unit. Updated the firmware to 5 Apr 2014 (I like to start with the latest when testing/learning and not bother about what was wrong with old stuff)
Installed 2.2 on SD card - pfSense-2.2-DEVELOPMENT-4g-amd64-nanobsd-20140417-0415.img.gz
It boots fine, no mountroot issue, so no need to do any ctrl-C and magic commands.
Assigned interfaces, then went through the webGUI wizard. I have done multiple restarts, and multiple halt, power cycle, boot sequences. Every time it has booted fine. So the timing issue does not seem to be there in FreeBSD 10/pfSense 2.2.
Now I will go back to the 1st unit and answer the question:Just out of curiosity, what happens if you use 20000 instead of 10000?
-
Just out of curiosity, what happens if you use 20000 instead of 10000?
No joy, I still get the "mountroot" prompt.
I tried 100000 also.
I wonder what I am doing different to everyone else? -
pfSense-2.2-DEVELOPMENT-4g-amd64-nanobsd-20140417-1054.img worked for me. but the 2.1.1 no 2.1.2 no joy.
-
Make sure you are setting:
kern.cam.boot_delay=10000I mistakenly typed it with a . instead of an _ in one post.
-
I cant seem to get CTRL-C to work in PUTTY. all I can get to is a mountroot> prompt
Another user reported a similar issue, not likely to be user-error on both cases.
That was me. I tried 3 different terminal programs before I found one that would accept keyboard input. This is the first time I have ever had a problem with putty. But this is the first time I have ever used it with an actual serial cable….
-
That did it Dotdash
set kern.cam.boot_delay=10000
then type
boot
Log in to the webgui and go to diagnostics, edit file.
Enter:/boot/loader.conf ( this was different for me I didn't have a /boot/loader.conf.local)
at the end of the file . Then enter:
kern.cam.boot_delay=10000
Save and your done.
I used the pfSense-2.1.2-RELEASE-4g-amd64-nanobsd-20140410-0542.img file
and I used a 8G SD card
I had to use ZOC/Pro 6.56 terminal emulator to get it to work on windows 7 :D -
@dotdash - I pasted from the original instructions early in this thread. They say boot.delay, can you edit that and make it boot_delay to help other mortals who cut-and-paste in future?
It worked first time when I used the correct command :)
-
@dotdash - I pasted from the original instructions early in this thread. They say boot.delay, can you edit that and make it boot_delay to help other mortals who cut-and-paste in future?
Sorry, I tried and it tells me that I cannot edit the topic…
EDIT: GruensFroeschli used his mod powers to edit the original post, so it is now correct. Danke. -
I think all found out the solution, but: Perhaps that helps for others
https://forum.pfsense.org/index.php?topic=75427.0