From owner-freebsd-bugs Sun Jul 6 21:30:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA23027 for bugs-outgoing; Sun, 6 Jul 1997 21:30:05 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA23019; Sun, 6 Jul 1997 21:30:02 -0700 (PDT) Date: Sun, 6 Jul 1997 21:30:02 -0700 (PDT) Message-Id: <199707070430.VAA23019@hub.freebsd.org> To: freebsd-bugs Cc: From: Kazutaka YOKOTA Subject: Re: i386/4030: syscons thinks CTRL is always pressed Reply-To: Kazutaka YOKOTA Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR i386/4030; it has been noted by GNATS. From: Kazutaka YOKOTA To: ac199@hwcn.org Cc: FreeBSD-gnats-submit@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: i386/4030: syscons thinks CTRL is always pressed Date: Mon, 07 Jul 1997 12:49:25 +0900 >>Number: 4030 >>Category: i386 >>Synopsis: syscons thinks CTRL pressed, must reboot [repeatable] >>Confidential: no >>Severity: critical >>Priority: medium >>Responsible: freebsd-bugs >>State: open >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Fri Jul 4 06:20:01 PDT 1997 >>Last-Modified: >>Originator: Tim Vanderhoek >>Organization: >Syscons users >>Release: FreeBSD 2.2.2-RELEASE i386 [snip] >>Description: > >I use a modified keyboard map. /usr/share/syscons/keymaps/my.map >has the following line modified, > > 090 cr rctrl rctrl rctrl rctrl rctrl rctrl rctrl O > >When I act as described in "How-To-Repeat", syscons will begin thinking >that one of the ctrl keys is always pressed. ie. pressing a `d' sends >^D. It then becomes necessary to reboot (since the computer is quite >unusable). If X is running, it, of course, is not affected. Try this patch for /sys/i386/isa/syscons.c. --- syscons.c-1.220 Mon Jun 30 22:31:49 1997 +++ syscons.c Mon Jul 7 12:35:14 1997 @@ -3039,7 +3039,7 @@ /* Check for make/break */ action = key->map[state]; if (scancode & 0x80) { /* key released */ - if (key->spcl & 0x80) { + if (key->spcl & (0x80>>state)) { switch (action) { case LSH: shfts &= ~1; >This did not happen (I don't _believe_ it happened) in the SNAP of 2.2 >that I had been running before. If the above patch works, then the problem did happen in the past too, I guess. Kazu