From owner-freebsd-hardware Thu Dec 24 00:08:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00443 for freebsd-hardware-outgoing; Thu, 24 Dec 1998 00:08:17 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from toad.async.org (hun-al1-24.ix.netcom.com [205.184.6.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00438 for ; Thu, 24 Dec 1998 00:08:10 -0800 (PST) (envelope-from dono@async.org) Received: from localhost (dono@localhost) by toad.async.org (8.9.1a/8.9.1a) with ESMTP id CAA00550; Thu, 24 Dec 1998 02:06:48 -0600 (CST) Date: Thu, 24 Dec 1998 02:06:47 -0600 (CST) From: Pilo Phlat To: questions@feebsd.org, hardware@FreeBSD.ORG Subject: Keyboard (PS/2?) problems 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 Hello, I have a PS/2 keyboard here, from "PC Concepts". It is the split-key (ergonomic), 107-key version (not the 109-key w/ touchpad). The keyboard is connected to a FreeBSD 2.2.8-RELEASE machine, with syscons driver, psm driver for the PS/2 mouse, and so on (mail me if you need to see the entire kernel config). The problem is that somewhat randomly (I cannot repeat this on-demand), about every 2-3 days (sometimes not even 1 day, sometimes 4-5 days) of being up, the keyboard freezes. It is usually after switching virtual consoles (with alt+Fkey). I could not find a way to reset the keyboard after it froze, and had to reboot the machine remotely. When I un-plug the keyboard and plug it back in, the Num/Caps/Scroll lock LEDs flash, but the keyboard is still frozen. Only way I could get it back to work is by rebooting the machine. It seems, though, that this is a problem with the keyboard itself, not FreeBSD (I haven't verified this). I've had this problem with Linux and Windows 98 as well, but in those cases, simply un-plugging and plugging the keyboard back in fixes the problem. Assuming that this is a problem with the keyboard, is there way to prevent this somehow (I doubt it, but ...)? If not, is there any way to reset it, so that I could use the keyboard again without rebooting (something like /usr/sbin/kcon -R won't help, since I'm using the syscons driver, not pcvt)? If any of you readers have experienced a similar problem with the same kind of keyboard, or a different kind, I'd like to know. Thanks for your time. -d. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message