From owner-freebsd-current Sun Jul 14 21:41:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24092 for current-outgoing; Sun, 14 Jul 1996 21:41:59 -0700 (PDT) Received: from gdi.uoregon.edu ([128.223.186.250]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA24072 for ; Sun, 14 Jul 1996 21:41:57 -0700 (PDT) Received: (from dwhite@localhost) by gdi.uoregon.edu (8.6.12/8.6.12) id VAA00276; Sun, 14 Jul 1996 21:41:55 -0700 Date: Sun, 14 Jul 1996 21:41:55 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: faried nawaz cc: current@freebsd.org Subject: Re: keyboard/console problems? In-Reply-To: <5599.837353398@waldrog.cs.uidaho.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 14 Jul 1996, faried nawaz 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. My computer (in general under any OS) has a fried keyboard controller that will lock up the keyboard. I wonder if yours just developed one. Sometimes switching terminals from X will stick the Cntrl key, just hit it and it should unlock. This is 2.1-R. > 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. I have to cold boot the machine :( Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major