From owner-freebsd-current  Sun Jul 14 07:10:06 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA13009
          for current-outgoing; Sun, 14 Jul 1996 07:10:06 -0700 (PDT)
Received: from dworshak.cs.uidaho.edu (dworshak.cs.uidaho.edu [129.101.100.160])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA12976
          for <current@freebsd.org>; Sun, 14 Jul 1996 07:10:02 -0700 (PDT)
Received: from waldrog.cs.uidaho.edu (waldrog.cs.uidaho.edu [129.101.100.23]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id HAA22488 for <current@freebsd.org>; Sun, 14 Jul 1996 07:10:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by waldrog.cs.uidaho.edu (8.7.5/1.0) with SMTP id HAA05601 for <current@freebsd.org>; Sun, 14 Jul 1996 07:09:59 -0700 (PDT)
X-Authentication-Warning: waldrog.cs.uidaho.edu: Host localhost [127.0.0.1] didn't use HELO protocol
To: current@freebsd.org
Subject: Re: keyboard/console problems? 
In-reply-to: Your message of "Sun, 14 Jul 1996 02:43:25 PDT."
             <5480.837337405@waldrog.cs.uidaho.edu> 
Date: Sun, 14 Jul 1996 07:09:58 PDT
Message-ID: <5599.837353398@waldrog.cs.uidaho.edu>
From: faried nawaz <nawaz921@cs.uidaho.edu>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

i wrote...
   
 Sometimes my keyboard ends up in a weird state: I can't switch console ttys;
 no keyboard input is accepted (even under X with "secure keyboard turned on");
 and it appears that the control key is "stuck" (clicking on any window appears
 as if i'd held down the control key before clicking).

I got a lot of them last night and decided to switch to the july 3rd kernel.
I got "stuck" again within minutes of booting off the older kernel.

I have checked all the cables; nothing seems wrong.

I did a sup & make world on Friday.

I've noticed that the control key doesn't stick always; once it was the
meta key, and a few times the mouse worked normally (could cut & paste).
I'm now running xev to observe this problem if it reoccurs.

One thing I forgot to mention was that I can "cure" this problem when under
X by just killing my Xsession and logging in again via xdm.


faried.