From owner-freebsd-current Mon Feb 19 00:15:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA10013 for current-outgoing; Mon, 19 Feb 1996 00:15:03 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA09988 for ; Mon, 19 Feb 1996 00:14:58 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA14526; Mon, 19 Feb 1996 09:14:07 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA13037; Mon, 19 Feb 1996 09:14:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA11333; Mon, 19 Feb 1996 09:11:53 +0100 (MET) From: J Wunsch Message-Id: <199602190811.JAA11333@uriah.heep.sax.de> Subject: Re: Keyboard lockout on 2.x.x To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Mon, 19 Feb 1996 09:11:52 +0100 (MET) Cc: KentH@HNS.St-Louis.Mo.US Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602190351.VAA00546@gwydion.hns.st-louis.mo.us> from "Kent Hamilton" at Feb 18, 96 09:51:10 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk As Kent Hamilton wrote: > > > > When exactly does it lock up? > > Ohh, sorry, I've seen this mentioned here before so I guess I thought > it was a well known problem. I'm using syscon and when flipping to a > different vt you'll get locked out. Does this happen for all keyboards? Does disconnecting/reconnecting the keyboard help? Keyboard lockup during VT switch is most likely due to a collision on the keyboard interface arising out of simultaneously sending a character code, while the driver is sending a SET LEDS command to the keyboard. The keyboard serial interface hasn't been designed to be two-way, but later (for the PC/AT) been used for this. Since you can rlogin into the machine, try compiling the kbdio(8) hacker's tool from /usr/src/usr.sbin/pcvt/kbdio, and see if you could also issue a keyboard reset. Sorry, no man page, only the usage help (try -h). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)