Re: bad scancode for USB keyboard

[Vojtech Pavlik <vojtech _at_ xxxxxxx>]

On Wed, Jan 07, 2004 at 03:27:42AM +0100, Bernardo Innocenti wrote:

> >I have the same problem with a Logitech cordless desktop.
> >I can easily change the keycode to generate the right characters when in 
> >console-mode, but XFree gives that key and the Print Screen key the same 
> >keycode.
> >After changing the xmodmap I can get the unmodified character, 
> >but modifiers doesn't work, it just gives me the same character not 
> >matter what modifier I use (shift, alt, alt_gr etc.)
> 
> I had fixed my console keymap too, but I've not been able to
> figure out how to change the X keymap.  I've been looking in
> the /usr/X11R6/lib/X11/xkb/ directory, but perhaps XKB is not
> being used for old-style keyboard mapping?
> 
> Could you provide detailed instructions?  C coding with missing
> backslash and bar keys is quite hard :-)
> 
> Of course, I still thing its' a 2.6 kernel bug and it should be
> fixed.  Vojtech, do you have an idea why it's happening?

The reason is that this key is not the ordinary backslash-bar key, it's
the so-called 103rd key on some european keyboards. It generates a
different scancode.

2.4 used the same keycode for both the scancodes, 2.6 does not, so that
it's possible to differentiate between the keys on keyboards that have
both this one and also the standard backslash-bar.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo _at_ vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/