From owner-freebsd-current Mon May 15 02:56:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA24129 for current-outgoing; Mon, 15 May 1995 02:56:09 -0700 Received: from easynet.com (easyr.easynet.net [198.67.38.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA24121 for ; Mon, 15 May 1995 02:56:05 -0700 Received: by easynet.com (Smail3.1.28.1 #7) id m0sAwsd-000rdbC; Mon, 15 May 95 02:56 WET DST Message-Id: From: brian@mediacity.com (Brian Litzinger) Subject: keyboard troubles To: freebsd-current@FreeBSD.org Date: Mon, 15 May 1995 02:56:03 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 745 Sender: current-owner@FreeBSD.org Precedence: bulk On about a 2 day old -current, I've run into a little problem. The power went out on a system, and when it rebooted one of the filesystems was corrupted in a way that the auto fsck gave up and I got the 'blah blah or press enter for shell:' prompt. Unfortuntely, the keyboard did not respond. Not even the numlock light would change. Before that point the keyboard had worked fine, including typing '/kernel -s'. I tried a different keyboard and when the system got to the same spot and lights on the keyboard starting blinking on and off and spurious garbage key strokes we being generated all by themselves. I then rebooted with a kernel that was approximately a week older and everything worked fine. Brian Litzinger brian@easynet.com