Date: Wed, 07 Oct 1998 14:40:26 +0200 From: Stefan Eggers <seggers@semyam.dinoco.de> To: "Viren R. Shah" <viren@rstcorp.com> Cc: freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: boot loader problems.. Message-ID: <199810071240.OAA25584@semyam.dinoco.de> In-Reply-To: Your message of "Tue, 06 Oct 1998 13:35:36 EDT." <199810061735.NAA00682@jabberwock.rstcorp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hit [enter] to boot immediately or .... > > prompt. > > At this point my /boot/boot.conf file was empty. > > I had to put a "boot /kernel.aout" into the /boot/boot.conf file. My Known bug. Has to do with the BIOS using keyboard code in the boot loader. Happens for me (Award Modular BIOS 4.51PG) when I either abort the memory check at cold start or have a boot password and thus entered it. If there were no keypresses the code worked for me as expected, though it is incorrect. > Is there an intermediate solution where it will wait 5 seconds before > autobooting kernel.aout? Don't do any keypresses before you reach the boot loader. :-( At least with my BIOS correct keyboard code doesn't work (tried it yesterday evening) and I don't know why. It could be a BIOS bug or a bug with returning flags in the new boot loader's VM86 code I think. I don't know enough of it at present do decide what of these both it is. You could use a serial console instead of keyboard/video card. Then you won't see this problem for obvious reasons - it uses different code for I/O then. An unused old PC with Dos+Terminal emulator or using a.out FreeBSD will do for this. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810071240.OAA25584>