Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA242 ; Sun, 31 Jan 93 13:59:03 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!caen!saimiri.primate.wisc.edu!usenet.coe.montana.edu!gemini.oscs.montana.edu!osynw From: osynw@gemini.oscs.montana.edu (Nate Williams) Subject: Re: [386bsd] X broken with new patchkit ? Message-ID: <1993Jan28.213428.24762@coe.montana.edu> Keywords: n Sender: usenet@coe.montana.edu (USENET News System) Organization: Montana State University References: <4374@wzv.win.tue.nl> <1993Jan28.175619.15857@fcom.cc.utah.edu> Date: Thu, 28 Jan 1993 21:34:28 GMT Lines: 25 In article <1993Jan28.175619.15857@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes: >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. Unfortunately, there are some patches in the com driver that make those patches obsolete. Anyone willing to make those patches for the stock com driver? I'm sure it's trivial, but I haven't had more than 5 hours of sleep/night this week, and this evening is no exception. Nate -- osynw@terra.oscs.montana.edu | A hacker w/out a home. work: (406) 994-5991 | Keeper of the Unofficial 386BSD Bug Report home: (406) 586-0579 | Please send bugs and/or fixes you find.