Date: Mon, 14 Jul 1997 17:07:04 +0200 (MET DST) From: Udo Wolter <uwp@ukrv.de> To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Cc: uwp@ukrv.de, bugs@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: PS/2 and Keycode bug Message-ID: <9707141507.AA16510@merlin.ukrv.de> In-Reply-To: <199707081711.CAA13841@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Jul 9, 97 02:11:06 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> >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 !!!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9707141507.AA16510>