From owner-freebsd-questions Wed Feb 7 8:50:10 2001 Delivered-To: freebsd-questions@freebsd.org Received: from routermonkey.com (fry.routermonkey.com [204.209.9.25]) by hub.freebsd.org (Postfix) with ESMTP id 31EA737B491 for ; Wed, 7 Feb 2001 08:49:53 -0800 (PST) Received: (from jason@localhost) by routermonkey.com (8.11.1/8.11.1) id f17GoL406310 for freebsd-questions@freebsd.org; Wed, 7 Feb 2001 09:50:21 -0700 (MST) (envelope-from jason) Date: Wed, 7 Feb 2001 09:50:20 -0700 From: Jason F Wells To: freebsd-questions@freebsd.org Subject: Keyboard detection in 4.2-RELEASE, 4.2-STABLE Message-ID: <20010207095020.A6097@fry.routermonkey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's problem I've been having for some time that I haven't been able to find a solution to. We have several FreeBSD servers in our server room, and our crude-but-effective method for administering them has been to use a central monitor and keyboard which we plug into the servers as necessary. (We don't have a KVM box.) This has always worked fine until we started installing FreeBSD 4.2 on our servers. Now we find that if a server is rebooted without the keyboard connected when it boots, if we plug in a keyboard after the fact it doesn't work. If the keyboard is connected at boot time, it can be unplugged and plugged back in without any problem. This seems to affect all the machines we have, from our latest and greatest Dual PIII box down to my own personal P166. Does anyone know what's causing this, and more importantly, how to disable it so that things work like they used to? Thanks, Jason. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message