*BSD News Article 38703


Return to BSD News archive

Xref: sserve comp.os.386bsd.bugs:2682 comp.os.386bsd.questions:14853
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!werple.apana.org.au!otis.apana.org.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!sol.ctr.columbia.edu!howland.reston.ans.net!swrinde!pipex!sunic!psinntp!psinntp!psinntp!uprc.com!cygnus!z056716
From: z056716@uprc.com (LaCoursiere J. D. (Jeff))
Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions
Subject: keyboard probs
Date: 30 Nov 1994 17:20:51 GMT
Organization: Union Pacific Resources Corp.
Lines: 25
Distribution: world
Message-ID: <3bic9j$t7v@clavin.uprc.com>
Reply-To: z056716@uprc.com
NNTP-Posting-Host: cygnus.uprc.com
Keywords: keyboard hang


I have been running 1.1.5.1 for about three months now on a 486DX2/66 (Intel)
with no problems.  I have a BOCA 16 port serial card with five modems hanging
off it at the moment.  Western Digital SVGA, vanilla I/O card, Adaptec 1542B.
Just yesterday, I came home to find that my keyboard would not respond.  The
system was up in X on virtual console 1.  Mouse still worked and I could cut and
paste text between xterm windows.  I cut and pasted a "fastboot" and the machine
came up with full keyboard support.  I thought nothing of it and went along merrily
until just a half hour later, I lost it again.  Appears to happen if I leave the 
keyboard idle for 10 minutes or so.  Thought it might have something to do with X,
so I rebooted again and went to eat dinner.  When I got back, I saw the getty on
console 1, but couldn't type a damn thing.  Could still dial-in, however, and
everything appeared to be working fine from that end.  Even rebuilt a kernel while
dialed in; took out some questionable stuff like the WINE support I wasn't using.
Haven't tested if that fixed it yet (still at the office).  I tried another keyboard
while it was in the locked state, but nothing.  I have seen problems like this
mentioned in the FAQ, but 1) it was working fine for some time; all of a sudden
started this crap, 2) the problems in the FAQ appear to be related to boot trouble,
i.e. hold down right shift until it boots and then it is OK....   doesn't appear
to be related to me...

j