Date: Fri, 18 Oct 1996 09:27:41 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: 2.2-961006-SNAP keyboard lockup Message-ID: <199610180727.JAA25957@uriah.heep.sax.de> In-Reply-To: <199610171704.LAA18599@rocky.mt.sri.com> from Nate Williams at "Oct 17, 96 11:04:29 am"
next in thread | previous in thread | raw e-mail | index | archive | help
As Nate Williams wrote: > I can also lockup vty switching by attempting to switch out of X before > it's completely initialized, which confuses the heck out of syscons. If This is an artifact of the way how VT switching in X11 is handled (the so-called ``process mode'' of the VT). The keyboard lockups are most likely bus arbitration failures for the keyboard bus. The keyboard bus has been designed to be uni-directional, and abused as a bi-directional bus later. There's no hardware support for an arbitration protocol, this is what makes it a fairly hard job to get it right. > it's any consolation, the *exact* same behavior occurs under SCO, so > syscons is doing a pretty good job of emulating both the good and bad > features of the SCO console driver. :) Btw., i've also seen SCO's jamming the keyboard of an HP Vectra (which is a _supported_ machine for SCO!) right at the first press of the CapsLock key. -- 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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610180727.JAA25957>