Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.windows.x
Subject: Re: Sun Keyboard problem?
Message-ID: <8024@auspex.auspex.com>
Date: 24 May 91 23:23:06 GMT
Article-I.D.: auspex.8024
References: <1991May17.171718.12393@nntp-server.caltech.edu> <1991May17.182610.3613@thyme.jpl.nasa.gov>
Organization: Auspex Systems, Santa Clara
Lines: 20

>And you can clearly see that 0 is legal.

No, you can clearly see that 0 is legal *only* if sunKeySyms[0].map is
not NULL, and if you take a look at "mit/server/ddx/sun/sunKeyMap.c",
you'll see that it *is* NULL.

0 is KB_KLUNK; only some old and, well, *klunky*, at this point, Sun-1s
had the "klunker" Micro Switch 1032D32-2 keyboard; I don't know if
anybody's done an X server port to them (the MIT server doesn't support
them out of the box).

Goodness knows why KIOCTYPE is reporting that he has a KB_KLUNK; the
"sleep()" you recommend might fix the problem.

>Are you sure it isn't -1?  If so I used to see this all the time running 
>xdm.  Sun's keyboard and/or kbd driver takes almost half a second to 
>"settle down" and return the correct keyboard type after a mode set.

It's the keyboard; the driver resets the keyboard whenever the
translation mode is changed, and the reset takes a while to complete.