On 12/5/2011 6:24 PM, Jed Clear wrote: > On Dec 5, 2011, at 3:03 PM, Jim Pingle wrote: >> I did make one change. Because that image does not have the serial >> console enabled I mounted the image on another FreeBSD box and activated >> the serial console in /boot/loader.conf.local like so: >> boot_multicons="YES" >> boot_serial="YES" > > Did you create a /boot.config file with -h in it? > > In fact that's all I have done, I don't have the two settings above in my > loader.conf file. Of course I run my console at 9600 so didn't need those. > To run at 19200, you also need comconsole_speed="19200" in your > loader.conf[.local] file. You also need to edit /etc/ttys to keep the 19200 > speed. I found the path of least resistance was to change the comBIOS speed > setting to 9600 once, so I could use the FreeBSD defaults w/o having to > remember to tweak each build in multiple places. > > I'm running NanoBSD 8.2R-p2 on a net5501.
Yeah my NanoBSD image did have -h in boot.config but the memstick did not, though since the memstick did continue on past the boot I didn't go back to try that. It may be worth trying out though. Thanks for the suggestions. You don't need to alter ttys on recent FreeBSD versions. You can do it all with loader.conf tunables now. Not sure exactly when that changed, but I added some GUI code to pfSense (for 2.1) to select whatever serial port speeds are desired there and it's worked great on my ALIX with NanoBSD and the net6501 with a full install. I could see some stages of the boot loader not drawing correctly if only using the loader tunables, but it should continue past those to the ones that do. Though I may need to try again tomorrow and manually set the speed to match the speed I have in the Soekris' BIOS. That would explain it stopping at the spinner for NanoBSD when I was booting off a hard drive, but it doesn't explain stopping at the hash marks when trying to boot from USB or the issue mounting root from a memstick, though the latter is probably more FreeBSD-related as Soren said. I'll have another run at that sometime this week, time permitting. The issue of NanoBSD stopping with the hash marks booting from USB is likely due to having multiple bootable slices on the media and using the boot manager. I suspect (and will try this also) that if I wipe that bit out and just use a standard mbr that it may work fine to boot the first slice. When we got into trouble on older BIOS implementations with ALIX and WRAP for example they worked fine with one slice but not two. Not sure how much trouble that would be to fix up in the BIOS here, if it's possible. Jim _______________________________________________ Soekris-tech mailing list [email protected] http://lists.soekris.com/mailman/listinfo/soekris-tech
