Bug 1878 - evdev keyboard driver, keycode issues
Summary: evdev keyboard driver, keycode issues
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/Keyboard (show other bugs)
Version: 6.8.1
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-22 00:27 UTC by Matthias Urlichs
Modified: 2005-08-25 05:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Matthias Urlichs 2004-11-22 00:27:13 UTC 
I am trying to use one of my USB keyboards with this input setting:

Section "InputDevice"
    Identifier  "Keyboard"
    Driver      "kbd"
    Option      "Protocol"      "evdev"
    Option      "Dev Name"      "*Multimedia Keyboard*"

    Option      "AutoRepeat"    "250 30"
    Option      "XkbRules"      "xfree86"
    Option      "XkbModel"  "pc104"
    Option      "XkbLayout" "de"
EndSection

Everything works, with one exception: the key less/greater/bar, formerly keycode
94, has moved to keycode 7.

$ xev
[...]
KeyPress event, serial 24, synthetic NO, window 0x2c00001,
    root 0x3a, subw 0x0, time 33338310, (117,54), root:(195,131),
    state 0x0, keycode 7 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:

KeyRelease event, serial 24, synthetic NO, window 0x2c00001,
    root 0x3a, subw 0x0, time 33338310, (117,54), root:(195,131),
    state 0x0, keycode 7 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes:

Unfortunately xmodmap refuses to assign any meaning to that key:

 $ xmodmap -e "keycode 7 = less greater bar"
xmodmap:  commandline:0:  bad keycode value (out of range)
xmodmap:  1 error encountered, aborting.
 $
Comment 1 Adam Jackson 2005-08-25 22:43:51 UTC 
the 'evdev' protocol is not part of any official xorg release.  you may wish to
report this bug to your distribution, since they have patched that protocol into
their release.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.