From owner-freebsd-mobile Sun Jan 5 07:14:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA02285 for mobile-outgoing; Sun, 5 Jan 1997 07:14:48 -0800 (PST) Received: from trapdoor.aracnet.com (root@trapdoor.aracnet.com [204.188.47.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA02280 for ; Sun, 5 Jan 1997 07:14:45 -0800 (PST) Received: from eris.beattie.aracnet.com (ppp-h11.aracnet.com [204.188.47.204]) by trapdoor.aracnet.com (8.7.4/8.6.9) with SMTP id HAA26849; Sun, 5 Jan 1997 07:15:05 -0800 Date: Sun, 5 Jan 1997 07:10:19 -0800 (PST) From: Brian Beattie X-Sender: beattie@eris.beattie.aracnet.com To: Kazutaka YOKOTA cc: mobile@freebsd.org, Nate Williams Subject: Re: Tecra 730 In-Reply-To: <199701050759.QAA24361@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- On Sun, 5 Jan 1997, Kazutaka YOKOTA wrote: > > I think there can be two possible reasons why the keyboard looks > locked up while the mouse continues to work: > > The first possibility is that this is real lock up; the keyboard and > the keyboard controller cannot communicate properly. Communication > MAY be restored by instructing the keyboard controller to test the > keyboard port. This can be done from the console driver, but in > practice it would be difficult for the driver to decide when it should > do it. > > The second possible explanation is that due to a lost keyboard > interrupt, shift, ctrl, alt, num lock, or whatever shift/lock state > change is not seen by the console driver or the X server and a key > stroke is not interpreted properly, thus, the keyboard looks locked up > despite that key scan codes are received by the console driver. You > may be able to recover from this by tapping these shift/lock keys > several times. The interrupt problem existed before, and we have been > hoping to eliminate it with the new syscons/psm/kbdio drivers, but... > > >> The keyboard still locks up under X + fvwm-1.24r, restarting the X > >> server brings the keyboard back. > > > >*sigh* I suspect you could switch to another virtual terminal and do the > >same thing, but w/out a keyboard it's kinda hard. :( > > Well, it appears that the second explanation above is more likely to > be the case, as I don't think resetting the X server affect the state > of the data line between the keyboard and the keyboard controller in > any way. > I'll try the hitting the shift/ctrl/alt/num lock keys while the keyboard is locked up and see what happens and let you know the results. Brian Beattie | From an MIT job ad "Applicants must also have http://www.aracnet.com/~beattie | extensive knowledge of UNIX, although they beattie@aracnet.com | should have sufficently good programming taste Fax (503)331-8186 | to not consider this an achievement." -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBMs/EF1QwtztGaITFAQGBUwQAqxuRZo65biu0kG5hqzEs+Q/T0iqx3A1y K3nFa0bxIS/aO0vzPgiIfWTXW2eAf1fHzUIVRC7UcgMI54/YUS5+Rhf6+G9m2dbL 5W4q51rRe8m5v8SQ32Mp5x97qikjhyc03ts4cyEkGPZFhpGNkSkoVqDxQ6dHjHWC YinzZhaFMCs= =Jctm -----END PGP SIGNATURE-----