Bug 11163 - X's evdev input driver ignoring some keycodes from kernel evdev module
Summary: X's evdev input driver ignoring some keycodes from kernel evdev module
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/evdev (show other bugs)
Version: 7.4 (2008.09)
Hardware: Other All
: medium normal
Assignee: Peter Hutterer
QA Contact: Xorg Project Team
URL: http://bugs.gentoo.org/show_bug.cgi?i...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-05 17:03 UTC by Joe H
Modified: 2010-11-18 20:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Joe H 2007-06-05 17:03:46 UTC
Cross-posting this at the request of distro bug handler:
http://bugs.gentoo.org/show_bug.cgi?id=180708

Keyboard is a Logitech MX 3200.  Running Xorg 7.2.0, evdev driver 1.1.5, and gnome 2.18.1

The main problem is that events which generate output when doing "cat /dev/input/eventX" do not generate any events when running xev in X.  That includes *all* of the extra/multimedia keys on the MX3200 keyboard.  The kernel does not report any errors about keycodes being unset.
Comment 1 Paul de Vrieze 2008-12-05 07:29:14 UTC
Make sure it is not related to bug #11227
Comment 2 Peter Hutterer 2008-12-18 02:29:24 UTC
Please download http://people.freedesktop.org/~whot/evtest.c, compile it with
"gcc -o evtest evtest.c" and then run it as root with "./evtest
/dev/input/eventX" where X is the number for the device. You can get the
number by looking at /proc/bus/input/devices.

What keycodes do the keys report? If the keycodes are > 255, there's nothing
we can do about it at the moment. In that case, please close this bug as
CANTFIX.
Comment 3 Peter Hutterer 2009-02-03 02:08:55 UTC
No reply from reporter, closing.
Comment 4 Gilboa Davara 2010-03-10 11:48:26 UTC
I just noticed this bug.
Hopefully you won't mind that I'm reopening it.

Fedora 12, x86_64, Xorg 7.4.

Evtest output:
Input driver version is 1.0.0
Input device ID: bus 0x3 vendor 0x46b product 0xff10 version 0x110
Input device name: "American Megatrends Inc. Virtual Keyboard and Mouse"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 1 (Esc)
    Event code 2 (1)
    Event code 3 (2)
    Event code 4 (3)
    Event code 5 (4)
    Event code 6 (5)
    Event code 7 (6)
    Event code 8 (7)
    Event code 9 (8)
    Event code 10 (9)
    Event code 11 (0)
    Event code 12 (Minus)
    Event code 13 (Equal)
    Event code 14 (Backspace)
    Event code 15 (Tab)
    Event code 16 (Q)
    Event code 17 (W)
    Event code 18 (E)
    Event code 19 (R)
    Event code 20 (T)
    Event code 21 (Y)
    Event code 22 (U)
    Event code 23 (I)
    Event code 24 (O)
    Event code 25 (P)
    Event code 26 (LeftBrace)
    Event code 27 (RightBrace)
    Event code 28 (Enter)
    Event code 29 (LeftControl)
    Event code 30 (A)
    Event code 31 (S)
    Event code 32 (D)
    Event code 33 (F)
    Event code 34 (G)
    Event code 35 (H)
    Event code 36 (J)
    Event code 37 (K)
    Event code 38 (L)
    Event code 39 (Semicolon)
    Event code 40 (Apostrophe)
    Event code 41 (Grave)
    Event code 42 (LeftShift)
    Event code 43 (BackSlash)
    Event code 44 (Z)
    Event code 45 (X)
    Event code 46 (C)
    Event code 47 (V)
    Event code 48 (B)
    Event code 49 (N)
    Event code 50 (M)
    Event code 51 (Comma)
    Event code 52 (Dot)
    Event code 53 (Slash)
    Event code 54 (RightShift)
    Event code 55 (KPAsterisk)
    Event code 56 (LeftAlt)
    Event code 57 (Space)
    Event code 58 (CapsLock)
    Event code 59 (F1)
    Event code 60 (F2)
    Event code 61 (F3)
    Event code 62 (F4)
    Event code 63 (F5)
    Event code 64 (F6)
    Event code 65 (F7)
    Event code 66 (F8)
    Event code 67 (F9)
    Event code 68 (F10)
    Event code 69 (NumLock)
    Event code 70 (ScrollLock)
    Event code 71 (KP7)
    Event code 72 (KP8)
    Event code 73 (KP9)
    Event code 74 (KPMinus)
    Event code 75 (KP4)
    Event code 76 (KP5)
    Event code 77 (KP6)
    Event code 78 (KPPlus)
    Event code 79 (KP1)
    Event code 80 (KP2)
    Event code 81 (KP3)
    Event code 82 (KP0)
    Event code 83 (KPDot)
    Event code 86 (102nd)
    Event code 87 (F11)
    Event code 88 (F12)
    Event code 96 (KPEnter)
    Event code 97 (RightCtrl)
    Event code 98 (KPSlash)
    Event code 99 (SysRq)
    Event code 100 (RightAlt)
    Event code 102 (Home)
    Event code 103 (Up)
    Event code 104 (PageUp)
    Event code 105 (Left)
    Event code 106 (Right)
    Event code 107 (End)
    Event code 108 (Down)
    Event code 109 (PageDown)
    Event code 110 (Insert)
    Event code 111 (Delete)
    Event code 119 (Pause)
    Event code 125 (LeftMeta)
    Event code 126 (RightMeta)
    Event code 127 (Compose)
  Event type 4 (Misc)
    Event code 4 (ScanCode)
  Event type 17 (LED)
    Event code 0 (NumLock)
    Event code 1 (CapsLock)
    Event code 2 (ScrollLock)
    Event code 3 (Compose)
    Event code 4 (Kana)
  Event type 20 (Repeat)
Grab succeeded, ungrabbing.
Testing ... (interrupt to exit)
^C

I tried the different extended keys after the "Testing" part - but no output.

- Gilboa
Comment 5 Gilboa Davara 2010-03-10 11:53:54 UTC
Not sure that this is not a kernel issue:
cat /dev/input/event7 (in my case) doesn't produce any events for some of the special keys. (E.g. FN-F2)
The weird thing is that cat /dev/input/event7 doesn't produce any events when I press FN-F1, but xev does show an event.

What should I test next?

- Gilboa
Comment 6 Peter Hutterer 2010-03-10 17:41:32 UTC
sorry, which keys don't work?

(In reply to comment #5)
> Not sure that this is not a kernel issue:
> cat /dev/input/event7 (in my case) doesn't produce any events for some of the
> special keys. (E.g. FN-F2)

cat is pretty bad for dumping these, use evtest or hexdump to check for events coming out of the devices. I notice this is a KVM switch, not an actual keyboard - do you have the keyboard behind the KVM?
Comment 7 Peter Hutterer 2010-11-18 20:28:50 UTC
closing again, 8 months silence


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.