From owner-freebsd-bugs Mon Jul 14 08:07:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA25631 for bugs-outgoing; Mon, 14 Jul 1997 08:07:29 -0700 (PDT) Received: from gatekeeper.ukrv.de (gatekeeper.ukrv.de [193.175.72.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA25621 for ; Mon, 14 Jul 1997 08:07:24 -0700 (PDT) Received: by gatekeeper.ukrv.de; (5.65/1.1.8.2/17Oct95-0336PM) id AA02656; Mon, 14 Jul 1997 17:07:12 +0200 Received: from mailhost(193.175.66.33) by gatekeeper.ukrv.de via smap (V1.3-JSC) id sma022890; Mon Jul 14 17:07:10 1997 Received: from merlin.ukrv.de by mailhost.ukrv.de; (5.65/1.1.8.2/08Mar95-0213PM) id AA11413; Mon, 14 Jul 1997 17:07:05 +0200 Received: by merlin.ukrv.de (4.1/UKRV-Gen PCG 0.1) id AA16510; Mon, 14 Jul 97 17:07:05 +0200 From: Udo Wolter Message-Id: <9707141507.AA16510@merlin.ukrv.de> Subject: Re: PS/2 and Keycode bug In-Reply-To: <199707081711.CAA13841@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jul 9, 97 02:11:06 am" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Mon, 14 Jul 1997 17:07:04 +0200 (MET DST) Cc: uwp@ukrv.de, bugs@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp X-Mailer: ELM [version 2.4ME+ PL31 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >But the keyboard never > >comes back, I never get any console until I reboot. > > What happens if you hit Num-Lock, Caps-Lock or Scroll-Lock? If > hitting these keys changes the keyboard LEDs, the keyboard driver is > working. Another way to test the keyboard driver is to login to the Nope, they're not working. > system via telnet or rlogin from another host, become root, and issue > `kbdcontrol -r fast < /dev/ttyv0'. If the keyboard driver is dead, the > command will fail. But this command is ok when trying it from root. No error when I'm using it from a rlogin terminal. Btw., I have to use root, because while starting X I log out from the syscons-console. > You see, there always is a possibility that it is either the window > manager or a client program that is not responding to mouse or > keyboard input, and the keyboard and mouse drivers are sending correct > data to the X server. But what is it in my case ? Bye, Udo -- Udo Wolter, email: uwp@cs.tu-berlin.de !!! LOW-TECH Page: http://low-tech.home.ml.org !!!