Option to boot other slice?
-
The NanoBSD images don't have that menu with safe mode and such.
I'm not sure why you aren't seeing that message, but it shows up for me on ALIX, on my VMs, and anywhere else I've put NanoBSD.
As a test, can you try the 1.2.3-RELEASE NanoBSD image on a spare CF just to see if that shows you the menu?
I suppose it may be that the menu only shows up for a second, perhaps something particular to your hardware/BIOS is skipping it somehow… If anyone else was having or reporting the issue I might suspect something had happened to the builder that made them disappear.
-
I just wrote out a fresh snapshot from this morning to a CF on my ALIX and I get the menu still. Here is what the first part of my boot output looks like:
1 pfSense 2 pfSense F6 PXE Boot: 1 /boot.config: -h Consoles: serial port BIOS drive C: is disk0 BIOS 640kB/261120kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org, Mon Oct 4 00:14:46 EDT 2010) Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x88055c data=0x3c9594+0x9bd20 / \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 2 seconds...
-
Hi jimp,
Ah, so that's where I should be looking!
I do get an unusual accented letter "a" at the start of the "/boot.config: -h" line in the serial output that doesn't appear to have been copied over in my prior message…
I don't get the first 5 lines of your output, I assume they are the cause of the odd "a" character...maybe this is a problem with term settings more than anything.
I'll try some other term programs & see if one of those seems to work better. If I have no luck there I'll try a fresh 1.2.3 install.
Also, I think post #3 in the thread has one other person seeing the same problem.
-Will
-
It's possible that it may be coming in at a different speed, if your BIOS does any kind of serial redirection you might check the speed settings there, dial them down to 9600.
-
Hi jimp,
Ah, so that's where I should be looking!
I do get an unusual accented letter "a" at the start of the "/boot.config: -h" line in the serial output that doesn't appear to have been copied over in my prior message…
I don't get the first 5 lines of your output, I assume they are the cause of the odd "a" character...maybe this is a problem with term settings more than anything.
I'll try some other term programs & see if one of those seems to work better. If I have no luck there I'll try a fresh 1.2.3 install.
Also, I think post #3 in the thread has one other person seeing the same problem.
-Will
With version 1.2.3 the same thing happens, do not see the option
shift slice -
Something I just had remembered, if you have a keyboard plugged in, it might cause some ambiguity in where the boot choice menu is displayed. If no keyboard is found, it should definitely be printing to the serial port.