Date: Fri, 18 Oct 1996 10:05:53 +0200 (MET DST) From: sos@freebsd.org To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-hackers@freebsd.org Subject: Re: 2.2-961006-SNAP keyboard lockup Message-ID: <199610180805.KAA13462@ra.dkuug.dk> In-Reply-To: <199610180727.JAA25957@uriah.heep.sax.de> from "J Wunsch" at Oct 18, 96 09:27:41 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to J Wunsch who wrote:
>
> 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.
I'd say almost impossible job...
> > 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. :)
Should I take that as a compliment ?? :)
Actually this is a bitch to solve, none of my machines (or the collection
of strange kbd controllers I have), exhibits this lockup behavior, so
I have no chances for finding a solution to this, but be assured that
if I get ahold of hardware with the problem I'll hunt it, its real annoying...
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610180805.KAA13462>