Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!news.cnri.reston.va.us!newsserver.jvnc.net!gmd.de!mururoa!veit
From: veit@mururoa.gmd.de (Holger Veit)
Subject: Re: does XFree86-1.3 and/or codrv actually work?
Message-ID: <1993Jun28.102903.12571@gmd.de>
Sender: veit@mururoa (Holger Veit)
Nntp-Posting-Host: mururoa
Organization: GMD - German National Research Center for Computer Science
References: <1993Jun28.072719.16216@qualcomm.com>
Date: Mon, 28 Jun 1993 10:29:03 GMT
Lines: 65
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).
Codrv does not expect the system to be in scan mode 2, it actually switches
it into this mode (in kbd_warmreset()). If you back out the reset keyboard code
from kbd_coldreset, which seems to be sometimes necessary to get bad
kbd controllers running, be sure to leave kbd_warmreset() in kbd_coldreset.
This is the only reason I can figure out which causes the system to
remain in scan 1 mode. I haven't seen any reports so far that there are
kbd controllers out there which do not understand scan 2 mode (and thus
ignore the setting of the KC8_TRANS bit). Your system seems to be the first
ever; so if this is true, please post the specification of the board
and the keyboard controller: This appears to be not "IBM compatible",
because since the earliest IBM 6MHz AT every 8042 knows this scan mode 2
(although it is not used very often).
You can compile the kernel with options XTKBDMODE; in this case codrv
uses scan 1 codes and translates them to the internal form used.
|>
|> 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.
I have XFree86-1.3 running with pk-0.2.4 and the codrv version from the pk
without problems, and I believe that at least the XFree86-1.3/pccons
config has been tested as well during the long alpha/beta phase of pk-0.2.4.
Maybe the system you have is no longer exactly 386bsd-0.1-srcdist+patchkit,
but was modified by several other patches.
|>
|> 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
--
Dr. Holger Veit | INTERNET: Holger.Veit@gmd.de
| | / GMD-SET German National Research | Phone: (+49) 2241 14 2448
|__| / Center for Computer Science | Fax: (+49) 2241 14 2342
| | / P.O. Box 13 16 | Had a nightmare yesterday:
| |/ Schloss Birlinghoven | My system started up with
DW-5205 St. Augustin, Germany | ... Booting vmunix.el ...