Date: Wed, 6 Sep 2000 10:36:49 +0100 From: simond@irrelevant.org To: Doug White <dwhite@resnet.uoregon.edu> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with installing 4.1-RELEASE Message-ID: <20000906103649.C27237@irrelevant.org> In-Reply-To: <Pine.BSF.4.21.0009051121500.70399-100000@resnet.uoregon.edu>; from dwhite@resnet.uoregon.edu on Tue, Sep 05, 2000 at 11:23:05AM -0700 References: <20000902204907.A5182@irrelevant.org> <Pine.BSF.4.21.0009051121500.70399-100000@resnet.uoregon.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 05, 2000 at 11:23:05AM -0700, Doug White wrote: > On Sat, 2 Sep 2000 simond@irrelevant.org wrote: > > > Hiya, is there any reason why "flags 0x1" got added to the atkbd0 line > > somewhere between 4.0 and 4.1? I'm asking as when I was trying to install > > 4.1-RELEASE it wasn't recognising the keyboard, installing with 4.0-RELEASE > > worked, after which I tried cvsuping to 4.1-STABLE which still didn't work. > > I believe this is to facilitate USB keyboards. From the atkbd man page: > > bit 0 (FAIL_IF_NO_KBD) > By default the atkbd driver will install even if a keyboard is > not actually connected to the system. This option prevents the > driver from being installed in this situation. > > If the atkbd driver loads it will become the default keyboard even if a > USB keyboard is present. > > If your keyboard controller is busted then you can try removing the flag. Yeah, that's what I ended up doing, by installing 4.0 and going to 4.1S without the flag, it works, but it doesn't seem ideal to cause the installation CD to hang on some keyboard controllers (the Via Apollo Pro on the Asus A7V in my case). -- Simon Dick simond@irrelevant.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000906103649.C27237>