From owner-freebsd-questions Tue Feb 19 9:13:22 2002 Delivered-To: freebsd-questions@freebsd.org Received: from nelly.internal.irrelevant.org (irrelevant.demon.co.uk [158.152.220.121]) by hub.freebsd.org (Postfix) with ESMTP id A5BE137B405 for ; Tue, 19 Feb 2002 09:13:16 -0800 (PST) Received: from laptop.internal.irrelevant.org ([192.168.253.2]) by nelly.internal.irrelevant.org with esmtp (Exim 3.34 #1) id 16dDpC-0002Ip-00; Tue, 19 Feb 2002 17:13:06 +0000 Subject: Re: Keyboard probing problem during installation From: Simon Dick To: Randy Pratt Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <200202191648.g1JGmPU20658@mail.ezwv.com> References: <200202191648.g1JGmPU20658@mail.ezwv.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.2 Date: 19 Feb 2002 17:13:44 +0000 Message-Id: <1014138828.10554.16.camel@laptop.internal.irrelevant.org> Mime-Version: 1.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2002-02-19 at 16:57, Randy Pratt wrote: > I'm helping a friend to install FreeBSD on his machine 250 miles away. > We're having some trouble with keyboard detection on versions later than 4.0. > Version 4.0 detected the keyboard and the probing finished: > > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > > Using version 4.4 or 4.5 (cdroms), the installation seemed to hang when it > started probing hardware. After doing some digging (man boot), I found that > if the keyboard is not detected, the output is sent to the serial port > instead of the internal display which is why it appeared to hang. > > In checking the mail archives, I found there was a change to the way the > keyboard was probed between 4.0 and 4.1. The atbkd driver flag > FAIL_IF_NO_KBD (0x1) was added along with other changes for USB support. > Changing this flag in the hardware configuration didn't seem to help (0x0, > 0x2, 0x3). > > We also tried some different booting options: boot -P, boot -D and boot -h. > A few combinations of boot options and keyboard flags were tried also. Any > suggestions for a combination to try would be appreciated. > > The Plug and Play option was set to off during all the testing. > > It doesn't seem to be an issue with the keyboard itself since two keyboards > were tried. There are no problems with keyboard detection on his windows or > Corel Linux installations. > > This box is a Gateway PII 450 using an Advaced Logic Reseach motherboard > and Phoenix bios 4.0 Release 6. > > An installation of 4.0 could probably be accomplished but it would be better > if a later version could be used. Of course, upgrading from 4.0 would pose a > problem also. > > Any insight, direction or suggestions would be appreciated. I'm not sure > what to suggest to him to try at this point. I've put the hand-transcribed > probe results from 4.0 at the end for reference. Its understood that there > may be other hardware issues after installation. I know that feeling well, my desktop PC never gets it's keyboard detected by FreeBSD, if you can get to the visual configuration screen then you can change the atkbd flags to 0x0 which should allow you to use it. I admit that I've started building my own releases with that flag set to 0x0 though as the visual config sometimes doesn't work here :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message