Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2025 comp.os.386bsd.questions:8087 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!natinst.com!hrd769.brooks.af.mil!hrd769.brooks.af.mil!not-for-mail From: burgess@hrd769.brooks.af.mil (Dave Burgess) Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Subject: Re: @#%^$! keyboard troubles AGAIN!!! Date: 19 Jan 1994 10:36:08 -0600 Organization: Armstrong Laboratory, Brooks AFB, TX Lines: 36 Message-ID: <2hjni6$hvc@hrd769.brooks.af.mil> References: <199401182225.RAA07076@freenet.buffalo.edu} <2hijgp$ngu@pdq.coe.montana.edu} NNTP-Posting-Host: hrd769.brooks.af.mil In article <2hijgp$ngu@pdq.coe.montana.edu}, Nate Williams <nate@bsd.coe.montana.edu} wrote: }In article <199401182225.RAA07076@freenet.buffalo.edu}, }Christopher L. Mikkelson <ae516@freenet.buffalo.edu} wrote: }}Hello all! }} I have been having troubles with X and my keyboard. While running an }}xinit session, with xterm and Seyon, I noticed that I was losing keys. }}Not dropping characters, mind you, but LOSING KEYS! First, I noticed }}that I wasn't sending any <RET}s, but had to send a ^M instead of pressing }}the ENTER key. Then I start to lose other charachters from the screen. }}Has anyone else had any such troubles? } }Most often the cause of this is from X and another process trying to }both access the keyboard, but since you are running xinit this shouldn't }be the problem. } }What console driver are you using? } I thought I would let you know that I am having a similar problem with my system. I am running NetBSD-current, and have only recently started having this kind of problem. I am running innd in the background, but it is attached to the console. Once in a while, I will be typing on the keyboard and innd will kick in to receive news. They keyboard goes completely dead for all intents and purposes. The spooky part was that this morning, after the news.daily job ran, the keyboard was back... I still don't know if it is because of the FAST Noops option, or a old statically linked innd. I will play with it a little more and see what I can figure out. -- TSgt Dave Burgess NCOIC Applications Programming Branch US Strategic Command, Offutt AFB, NE burgessd@j64.stratcom.af.mil