Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA204 ; Fri, 29 Jan 93 13:00:29 EST
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!bogus.sura.net!udel!gatech!news.byu.edu!ux1!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386bsd] X broken with new patchkit ?
Message-ID: <1993Jan28.175619.15857@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <4374@wzv.win.tue.nl>
Date: Thu, 28 Jan 93 17:56:19 GMT
Lines: 27
In article <4374@wzv.win.tue.nl> guido@gvr.win.tue.nl (Guido van Rooij) writes:
>I installed the new patchkit a few days ago. I also had keycap-0.1.1 (codrv)
>installed. This used to work fine, but now that I've installed the new
>patchkit, the keyboard isn't functioning quite well anymore when using X.
>Symptoms are that after pressing a key you have to wiat several seconds
>for the key to become visible on your xterm UNLESS you move your mouse..
>then the char immediately shows up. Anyone having the same behaviour?
Obvious select() problem -- make sure the right device is selected in the
com driver (0 instead of 1 or 1 instead of 2. This was in the previous
patch kit, and I don't think it was removed.
Until this is fixed by you, you will find your X server eating inordinate
amounts of CPU most of the time.
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------