Date: Thu, 16 Mar 2000 16:50:24 -0800 From: Mike Smith <msmith@freebsd.org> To: "Brian J. McGovern" <mcgovern@spoon.beta.com> Cc: brent@kearneys.ca, questions@freebsd.org, hackers@freebsd.org, jfn@enteract.com Subject: Re: AMD Athlon and booting Message-ID: <200003170050.QAA00506@mass.cdrom.com> In-Reply-To: Your message of "Thu, 16 Mar 2000 19:11:38 EST." <200003170011.TAA33374@spoon.beta.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This has nothing to do with Athlon processors and everything to do with buggy BIOS code that doesn't set the "extended keyboard present" bit. Feel free to check the (very simple) code in boot2 that performs keyboard detection, and if you've got any better ideas on how to make this work properly, we're all ears. 8) > Hey, guys. I went a slightly different route than playing with the numlock key > to get FreeBSD running. The problem seems to really be the -P (probe the > keyboard) boot option, and it setting -D and -h when it doesn't find it. My > "workaround" was to make boot floppies, and edit boot.conf to remove the -P > (or delete the file if there are no other options). > > Once done, it just happily boots up and installs. Looks like keyboard probing > may need some work for Athlon processors, so i'm cc'ing this to the hackers > list, so hopefully, some console guru can take a look at it. > > Also, if no one has done it so far, let me know, and I'll submit a pr. > > -Brian > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003170050.QAA00506>