1 |
Albert Hopkins schrieb: |
2 |
> I'm going to guess that the keyboard driver or something is interfering |
3 |
> with the evdev driver? Or you don't have proper evdev support in the |
4 |
> kernel? Or is your xorg.conf telling X to use a different driver? |
5 |
> |
6 |
> I don't have access to a Gentoo machine right now, but when I look at a |
7 |
> similar machine (same exact keyboard though). I get this: |
8 |
> |
9 |
> $ egrep -i '(key|evdev)' /var/log/Xorg.0.log |
10 |
> (II) Cannot locate a core keyboard device. |
11 |
> (==) intel(0): video overlay key set to 0x101fe |
12 |
> (II) Initializing built-in extension XKEYBOARD |
13 |
> (II) LoadModule: "evdev" |
14 |
> (II) Loading /usr/lib64/xorg/modules/input//evdev_drv.so |
15 |
> (II) Module evdev: vendor="X.Org Foundation" |
16 |
> (II) ThinkPad Extra Buttons: Found keys |
17 |
> (II) ThinkPad Extra Buttons: Configuring as keyboard |
18 |
> (II) XINPUT: Adding extended input device "ThinkPad Extra |
19 |
> Buttons" (type: KEYBOARD) |
20 |
> (**) Option "xkb_rules" "evdev" |
21 |
> (**) Option "xkb_model" "evdev" |
22 |
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Found keys |
23 |
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Configuring as |
24 |
> keyboard |
25 |
> (II) XINPUT: Adding extended input device "Microsft Microsoft Wireless |
26 |
> Desktop Receiver 3.1" (type: KEYBOARD) |
27 |
> (**) Option "xkb_rules" "evdev" |
28 |
> (II) config/hal: Adding input device AT Translated Set 2 keyboard |
29 |
> (**) AT Translated Set 2 keyboard: always reports core events |
30 |
> (**) AT Translated Set 2 keyboard: Device: "/dev/input/event4" |
31 |
> (II) AT Translated Set 2 keyboard: Found keys |
32 |
> (II) AT Translated Set 2 keyboard: Configuring as keyboard |
33 |
> (II) XINPUT: Adding extended input device "AT Translated Set 2 |
34 |
> keyboard" (type: KEYBOARD) |
35 |
> (**) Option "xkb_rules" "evdev" |
36 |
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Found keys |
37 |
> (II) Microsft Microsoft Wireless Desktop Receiver 3.1: Configuring as |
38 |
> keyboard |
39 |
> (II) XINPUT: Adding extended input device "Microsft Microsoft Wireless |
40 |
> Desktop Receiver 3.1" (type: KEYBOARD) |
41 |
> (**) Option "xkb_rules" "evdev" |
42 |
> (II) Sleep Button: Found keys |
43 |
> (II) Sleep Button: Configuring as keyboard |
44 |
> (II) XINPUT: Adding extended input device "Sleep Button" (type: |
45 |
> KEYBOARD) |
46 |
> (**) Option "xkb_rules" "evdev" |
47 |
> (**) Option "xkb_model" "evdev" |
48 |
> (II) Video Bus: Found keys |
49 |
> (II) Video Bus: Configuring as keyboard |
50 |
> (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD) |
51 |
> (**) Option "xkb_rules" "evdev" |
52 |
> (**) Option "xkb_model" "evdev" |
53 |
> (II) Power Button: Found keys |
54 |
> (II) Power Button: Configuring as keyboard |
55 |
> (II) XINPUT: Adding extended input device "Power Button" (type: |
56 |
> KEYBOARD) |
57 |
> (**) Option "xkb_rules" "evdev" |
58 |
> (**) Option "xkb_model" "evdev" |
59 |
> |
60 |
> Not that it is XINPUT that is driving my keyboard, not Keyboard1. So |
61 |
> I'm guessing it's the X config. |
62 |
|
63 |
Might be. Do you have any keyboard section in xorg.conf? |
64 |
I assume I could get rid of xorg.conf at all but whenever I tried that |
65 |
my X11 didn't start up anymore ... |
66 |
|
67 |
> Then again, it might be gpm. Are you using gpm? Maybe it's grabbing |
68 |
> the keyboard and not letting X have it. |
69 |
|
70 |
No gpm running. |
71 |
|
72 |
Stefan |