Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!swrinde!news.uh.edu!uuneo.neosoft.com!blkbox!cbevis From: cbevis@blkbox.com (Cameron Bevis) Newsgroups: comp.os.386bsd.questions Subject: Keyboard Lockup Problems Date: 29 Jun 1994 22:47:54 GMT Organization: The Black Box, Houston, Tx (713) 480-2686 Lines: 41 Message-ID: <2ustmq$4fm@blkbox.blkbox.COM> NNTP-Posting-Host: blkbox.com X-Newsreader: TIN [version 1.2 PL2] Hello all. I have a problem wherein the keyboard locks up occasionally. I can dial into the system after a lockup, and everything works great, just no keyboard input from the console. This is a very duplicable problem if I just bang on CapsLock or NumLock really quickly and also happens when switching to/from virtual screens. This question seems to be popping up intermittently in the "questions" newsgroup from since at least December. Things I have tried: pcons and sysons: same thing calling in from tty00 and "echo"ing to that console: same thing killing caches, shadow bios The rest of the solutions in the group regarding this question have been installation related, with one exception: "put a 250ms delay before any port I/O involving the LEDs" Has anybody done this? Where in the kernel sources/config is this done? Were there any successes not mentioned in the group? My hardware: Packard Bell Legend 610 486SX-33 6 MB RAM ps/2 (the little jack) keyboard and ps/2 mouse disabled Conner CP30204 200MB Hard Drive My software FreeBSD 1.1-Release GENERICAH kernel with syscons (just like covered in the faq) and un-needed devices deleted Thanks in advance for your help. Cam Bevis Digital Solutions, Inc. cbevis@blkbox.com cbevis@digsol.jpunix.com