On Fri, May 07, 2004 at 08:06:37PM +0900, Rob wrote:If I understand the process correctly, settings in /boot/loader.conf override settings in /boot.config as the boot loader happens after the boot blocks. Thus by setting "comconsole" will negate any settings in /boot.config. Setting in both places is redundant and may cause problems for you when troubleshooting.
Stijn Hoop wrote:
On Fri, May 07, 2004 at 05:01:29PM +0900, Rob wrote:Ah, thanks. I don't have a /boot.config yet. Are you sure this file goes
Funny, that I'm struggling with opposite problem: I do not get theYou probably need to tell the kernel to use the serial console:
boot messages over the serial cable, but do get the login prompt,
which I do not understand :(.
# echo '-h' > /boot.config
in the top-root directory? Or in /boot/... ?
Yes, top-root /. Check the handbook, section 17.6:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
You made me research a little more on this. I do have a file /boot/loader.conf.
How about having in here the line
console="comconsole"
(to divert it from the default: console="vidconsole") ?
Or will that not do the same?
Having -h in /boot.config will also allow the boot blocks to output to your serial console. I suspect console="comconsole" would help the loader + kernel. It certainly couldn't hurt I guess :)
For my serial console, I set my kernel flag to 0x10 so I have console options without recompiling. Then I do my serial console settings in /boot.config as it happens earlier in the boot stage and thus, I get my serial console a little sooner.
HTH,
Drew
-- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More!
http://www.alchemistswarehouse.com
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
