Personally, I'm keen with the fact that the problem is known, its understood
there isn't an easy fix, and I have a work around.
-Brian
>
> 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. M
y
> > "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 prob
ing
> > may need some work for Athlon processors, so i'm cc'ing this to the hacker
s
> > 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 [EMAIL PROTECTED]
> > 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, \\ [EMAIL PROTECTED]
> \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
