Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!uunet!opl.com!cass.ma02.bull.com!melb.bull.oz.au!sjg From: sjg@melb.bull.oz.au (Simon J Gerraty) Newsgroups: comp.os.386bsd.bugs Subject: No response from keyboard Keywords: ttyin pccons Message-ID: <1993May12.140704.22966@melb.bull.oz.au> Date: 12 May 93 14:07:04 GMT Organization: Bull HN Information Systems Australia Lines: 40 This problem has gone from bad to worse. I'm running 386bsd-0.1 PatchKit 0.2.3 Hardware is 486-33 with Opti chipset and AMI bios. This is the same hardware that could not boot the original Tiny386bsd due to problems with the keyboard controller. Originally I used to find that about once per week I'd come to the console to find that it would not respond to the keyboard. Fortunately I run X and the mouse still works, so killing the console window stops X and I have a keyboard again. Note this is not X's fault as the same thing happens when X is not running - but your only option then is to hit the reset button. Since installing patchkit 0.2.3, the keyboard hang is a daily event! I have had a look at the interrupt routines in pccons.c and added a few bits of inb() outb() magic on port 0x61 to ack the char to the keyboard controller, but this has not helped. Curiously, I don't recall the keyboard ever locking up while I was busy typing - only when the machine has been idle over night. There must be some bit of keyboard control logic misssing but I don't know what. For what its worth, all the hung ksh's are waiting on channel "ttyin" and hiting keys does not register as 'w' (I added 'w' and 'ps -axl' to my twm menu so I could run them even when the keyboard was stuffed) still shows the pty to be idle. Any help appreciated. Same goes for any patches to st.c or aha1542.c that fix the "soft error's" on my 60Mb archive tape drive. -- Simon J. Gerraty <sjg@zen.void.oz.au> (home) #include <disclaimer> /* imagine something *very* witty here */