From owner-freebsd-hardware Wed Mar 18 14:26:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07762 for freebsd-hardware-outgoing; Wed, 18 Mar 1998 14:26:11 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from junior.thinkwell.com (junior.thinkwell.com [207.8.90.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07680 for ; Wed, 18 Mar 1998 14:26:00 -0800 (PST) (envelope-from aa@thinkwell.com) Received: from localhost (aa@localhost) by junior.thinkwell.com (8.8.5/8.8.5) with SMTP id QAA00201 for ; Wed, 18 Mar 1998 16:26:12 -0600 (CST) Date: Wed, 18 Mar 1998 16:26:12 -0600 (CST) From: Allan Alford X-Sender: aa@junior To: freebsd-hardware@FreeBSD.ORG Subject: Sporadic Keyboard Failure with 2.2.2-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running a standard roll-your-own Penitum mid-tower system with a large 5-pin DIN keyboard, and periodically while in FreeBSD/XWindows the keyboard just suddenly fails to work. Mouse still works o.k. to exit X-Windows, but keyboard doesn't respond - don't even get numlock/capslock lights. I work mostly in X-Windows, so I'm not sure if it's valid to point out that: a) This never happens when the machine is in Win95 mode. b) This never happens when the machine is in unix command-prompt mode. Any ideas? - Allan aa@thinkwell.com <<< "Hacking today for a better tomorrow..." >>> aa@jump.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message