Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!walter!qualcom.qualcomm.com!servo.qualcomm.com!karn From: karn@servo.qualcomm.com (Phil Karn) Subject: does XFree86-1.3 and/or codrv actually work? Message-ID: <1993Jun28.072719.16216@qualcomm.com> Sender: news@qualcomm.com Nntp-Posting-Host: servo.qualcomm.com Organization: Qualcomm, Inc Date: Mon, 28 Jun 1993 07:27:19 GMT Lines: 33 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). When I fell back to pccons, the keyboard started working again. Then I 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? My system is a fairly generic 486-DX2-66 with VESA local bus VGA and Adaptec SCSI interface. It was quite solid until I started upgrading this weekend. Phil