*BSD News Article 25768


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!sgiblab!swrinde!cs.utexas.edu!howland.reston.ans.net!newsserver.jvnc.net!a3bee2.radnet.com!gaboon!dmk
From: dmk@gaboon.UUCP (Dave Knight)
Subject: Bug in Console Driver?
Message-ID: <1994Jan8.143107.14276@gaboon.UUCP>
Organization: Voket Org.
X-Newsreader: Tin 1.1 PL5
Date: Sat, 8 Jan 1994 14:31:07 GMT
Lines: 28

NetBSD 0.9 (from the InfoMagic CDROM) runs fine for me ( 12MB RAM, 386DX/33,
Conner IDE 340MB (WD ctlr), CDC-9471 300MB SCSI (AHA1542B ctlr), WD8003E Enet, 
and a Herc/MONO video card, except for one ANNOYING thing:

	If I hit any of the "lock" keys (CapsLock, ScrollLock or NumLock)
	on the console (pc3) the keyboard HANGS!

I can rlogin from another node and kill the pgms/shell and I get a login
prompt on the console, login again and everything is OK until the next time
I (accidentally) hit one of the "magik" keys.  

As the problem does not occur for anything other than the console keyboard
(when rlog'd in from another node, the lock keys work as expected), I suspect
that to problem is in the console keyboard driver.

I looked at the keyboard driver and saw some case stmts without defaults
that concerned the 3 lock keys.  I provided (reasonable?) "default" cases
and rebuilt the kernel without any improvement.  Several other more
adventurous attempts resulted in unusable kernels.

If this is a "known problem", please point me at a patch or workaround.  
If not, perhaps one of you BSD kernel hackers can point this old SYSV
hacker to the path of enlightenment (for the console/keybd driver, at least).

Thanks...

BTW, is there a driver or patch that supports multiple virtual consoles
like those available in the various SYSV Unix's and clones?