Bug 8412 - evdev keyboard NumLock switching on IBM ThinkPad
Summary: evdev keyboard NumLock switching on IBM ThinkPad
Status: RESOLVED DUPLICATE of bug 14061
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/evdev (show other bugs)
Version: 7.0 (2005.12)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Zephaniah E. Hull
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-24 04:11 UTC by Andre Colomb
Modified: 2008-09-08 23:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Andre Colomb 2006-09-24 04:11:35 UTC
I have an IBM ThinkPad running Linux 2.6.18. To switch the NumLock state on the
internal keyboard, I have to press the Shift + ScrollLock keys. On the console,
this works fine, but in X I get the following events from xev:

---SNIP---
KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x4c, subw 0x1400002, time 3749488372, (56,62), root:(960,578),
    state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x4c, subw 0x1400002, time 3749488919, (56,62), root:(960,578),
    state 0x1, keycode 77 (keysym 0xfef9, Pointer_EnableKeys), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x4c, subw 0x1400002, time 3749489054, (56,62), root:(960,578),
    state 0x1, keycode 77 (keysym 0xfef9, Pointer_EnableKeys), same_screen YES,
    XLookupString gives 0 bytes: 

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x4c, subw 0x1400002, time 3749489430, (56,62), root:(960,578),
    state 0x1, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
---SNIP---

That results in neither the internal keypad (alternate Symbols on some keys) nor
my USB keyboard's keypad generating any more keypad events, but mouse events
instead.

Is there a way to make this key combination work as it does on the console?

I am using the xf86-input-evdev driver version 1.1.2 (Debian version 1.1.2-2)
with the following xorg.conf directives:

Section "InputDevice"
        Identifier      "Thinkpad Keyboard"
        Driver          "evdev"
        Option          "CoreKeyboard"
        Option          "Name"                  "AT Translated Set 2 keyboard"
        Option          "XkbRules"              "xorg"
        Option          "XkbModel"              "evdev"
        Option          "XkbLayout"             "de"
        Option          "XkbVariant"            "nodeadkeys"
EndSection

Section "InputDevice"
        Identifier      "USB Keyboard"
        Driver          "evdev"
        Option          "SendCoreEvents"        "on"
        Option          "Name"                  "HID 046a:0001"
        Option          "XkbRules"              "xorg"
        Option          "XkbModel"              "evdev"
        Option          "XkbLayout"             "us"
#       Option          "XkbVariant"            "basic"
EndSection

Thanks!
Andre
Comment 1 Alex Deucher 2006-09-27 07:31:20 UTC
see the numlock section on this page:
http://www.thinkwiki.org/wiki/How_to_get_special_keys_to_work

NumLock

On the ThinkPad X21, T20, T21, T30, X31, T43, R51 and possibly other models, X
does not recognize the keycode for NumLk = Shift+ScrLk. To fix this, add the
following to ~/.Xmodmap in your home directory or /etc/X11/Xmodmap and run
xmodmap, ex: xmodmap ~/.Xmodmap:

keycode 77 = Num_Lock
Comment 2 Daniel Stone 2007-02-27 01:33:41 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 3 Rolf Leggewie 2008-08-08 18:44:39 UTC
Is this still a problem?

I'm also having problems with numlock, but they are a bit different: https://bugs.launchpad.net/ubuntu/+bug/182421
Comment 4 Josh Triplett 2008-09-08 23:16:06 UTC

*** This bug has been marked as a duplicate of bug 14061 ***


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.