From owner-freebsd-hackers Fri May 30 07:58:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA19292 for hackers-outgoing; Fri, 30 May 1997 07:58:18 -0700 (PDT) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA19285 for ; Fri, 30 May 1997 07:58:16 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id KAA07964; Fri, 30 May 1997 10:52:04 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id KAA04020; Fri, 30 May 1997 10:57:44 -0400 (EDT) Message-Id: <199705301457.KAA04020@bmcgover-pc.cisco.com> To: stogdon.psd@navir.navy.mil cc: hackers@freebsd.org Subject: Re: Keyboard lockup problem (was: Need help) Date: Fri, 30 May 1997 10:57:43 -0400 From: Brian McGovern Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have seen this problem before on a Dell P75 and a P100 where the keyboard and mouse are PS/2 styles. Usually, unplugging the mouse and/or generating keyboard and mouse interrupts during the bootup would let you slide past the problem. I think (I have not investigated this sufficiently to be sure) that it has something to do with how FreeBSD is reseting this particular set of kerboard/mouse controllers. This message is to act more of a confirmation that this isn't one particular machine, but a group of them. I have, however, had the boot disk work on other Dells of the same type. The only thing that made this one different was that the flash ROM code for the machine had been upgraded to the "latest" release for that particular machine (I wasn't the one who was responsible for doing it, so details are second hand). Perhaps this ROM change was sufficient to cause the problem (probably was), rather than it being a change in the FreeBSD console driver. -Brian