Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!pipex!uknet!cf-cm!paul From: paul@isl.cf.ac.uk (Paul) Subject: Re: does XFree86-1.3 and/or codrv actually work? Message-ID: <1993Jun28.110255.10868@cm.cf.ac.uk> Sender: news@cm.cf.ac.uk (Network News System) Organization: /usr/local/lib/rn/organisation References: <1993Jun28.072719.16216@qualcomm.com> Date: Mon, 28 Jun 1993 11:02:53 +0000 Lines: 53 In article <1993Jun28.072719.16216@qualcomm.com> karn@servo.qualcomm.com (Phil Karn) writes: > >This weekend I installed patchkit 0.2.4 and upgraded to XFree86-1.3 >with codrv. > >Big mistake. > >codrv doesn't work at all on my system. As far as I can tell with a >couple of printfs, the keyboard is still producing "set 1" scan codes >(e.g., when you hit the '1' key it produces 02 hex, and when you >release the key, it produces 82 hex). This is the mode used by the >original pccons and by syscons (which I had been using successfully >until now). > >But the new codrv seems to expect the keyboard to be in "scan set 2" >(e.g., when you hit '1' it produces 16 hex, and when you release it >you get f0 16). At least it seems this way from the hardwired codes in >a switch statement that looks for meta keys. When I try to run this >driver, I get garbage whenever I type. (Output to the display is >fine). I too have had problems with codrv. In my case I don't get anything from the keyboard at all. It's completely dead, won't even light the leds with a caps lock. It does absolutely nothing. In my case too my display is fine. If I log in from somewhere else and cat to the screen there's no problem. It's just the keyboard that's dead > >When I fell back to pccons, the keyboard started working again. Then I Yes, mine works fine with pccons. Seems like codrv isn't totally portable across all hardware as yet. >tried to bring up Xfree86-1.3. This consistently rebooted the system. >I fell back to XFree86-1.2. This *also* rebooted the system. So something >else must have changed in the 0.2.4 patchkit that has broken something. > >Before spend a lot of time backing everything out to try to track down >the problem further, has anyone else encountered these symptoms? Holger said he'd tried codrv with and without the patchkti and it works. Have you tried codrv before. If it worked before tha patchkit but not after then suspect the patchkit but from what I've tried I don't think it's to blame. Haven't treid XFree86-1.3 yet so can't comment on that. -- Paul Richards, University of Wales, College Cardiff Internet: paul@isl.cf.ac.uk spedpr@thor.cf.ac.uk