From owner-freebsd-isp Thu Mar 14 9:59:17 2002 Delivered-To: freebsd-isp@freebsd.org Received: from floyd.getsetnet.net (floyd.gnulife.org [199.86.41.27]) by hub.freebsd.org (Postfix) with ESMTP id 0902837B419 for ; Thu, 14 Mar 2002 09:59:12 -0800 (PST) Received: by floyd.getsetnet.net (Postfix, from userid 1000) id 1AC29431BE; Thu, 14 Mar 2002 12:01:54 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by floyd.getsetnet.net (Postfix) with ESMTP id 00D014309D for ; Thu, 14 Mar 2002 12:01:53 -0600 (CST) Date: Thu, 14 Mar 2002 12:01:53 -0600 (CST) From: Jamie Ostrowski To: freebsd-isp@FreeBSD.org Subject: Problem with keyboard on FreeBSD Message-ID: <20020314115743.N28153-100000@floyd.getsetnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I am running FreeBSD 4.5 RELEASE on an x86 hardware based server. If the keyboard happens to come unplugged, upon plugging it back in there is no response from the system. I have to reboot for the keyboard to start working again. The problem is that I have to shut the machine down hard in order to do this, since the keyboard is unresponsive. Obviously the disks complain when I bring the machine up again, and this is a production server. If a keyboard accidentaly comes unplugged, is there anything you can do to get the system to interact with it rather than powering down and restarting? Thanks, - Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message