Summary: | evdev doesnt reports multimedia keys events from a device that is both mouse and kbd | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matheus Izvekov <mizvekov> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | kanelxake, pauldv |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matheus Izvekov
2006-04-08 17:38:15 UTC
Are you trying to use evdev for both the mouse and keyboard? If not, please give that a shot. Then it doesnt work, i cant get the keyboard to work at all with evdev. Here is the device section i wrote for it: Section "InputDevice" Identifier "Keyboard0" Driver "evdev" Option "Protocol" "Auto" Option "Device" "/dev/input/event0" EndSection ..and using evdev for both the mouse and keyboard is nothing I recommend unless you try the latest version of evdev (1.1.0) which was released the day before this bug was created. It needs an update for xkbvdata also (currently I am running csv-version of this, but will bump locally an report back). This version is a rewrite to make for example the keyboard-support a little bit better.... I will try it when it hits portage, but i cant get evdev to work even with a keyboard alone. Remove "Protocol" and see what happends... removing the "Protocol" line didnt help. as usual i dont get any errors in the log file, just: (**) Option "CoreKeyboard" (**) Keyboard0: Core Keyboard (**) Keyboard0: Device: "/dev/input/event0" (II) Keyboard0: Found keys (II) Keyboard0: Configuring as keyboard Just tried the evdev from cvs. With it, keyboard kind of works. All the alphanumeric ones works, but many keys have weird/swapped codes (like the directional arrows, win key, menu key, all the ones just above the directional keys, and maybe others i didnt test). Mouse works ok still, although i still cant get those "keyboard events" to work with it. Interesting part of the log: (II) evdev brain: Rescanning devices (1). (**) Option "CoreKeyboard" (**) Keyboard0-usb-0000:00:02.0-1/input0: Core Keyboard (**) Option "XkbModel" "pc105" (**) Option "XkbLayout" "us" (**) Option "XkbVariant" "intl" (II) evdev brain: Rescanning devices (2). (**) Option "CorePointer" (**) Mice0-usb-0000:00:02.0-1/input1: Core Pointer (II) Mice0-usb-0000:00:02.0-1/input1: Found 36 absolute axes. (II) Mice0-usb-0000:00:02.0-1/input1: Configuring as pointer. (**) Mice0-usb-0000:00:02.0-1/input1: Configuring in Absolute mode. (**) Mice0-usb-0000:00:02.0-1/input1: AbsoluteScreen: 0. (II) Mice0-usb-0000:00:02.0-1/input1: Found 8 relative axes. (II) Mice0-usb-0000:00:02.0-1/input1: Configuring as pointer. (**) Mice0-usb-0000:00:02.0-1/input1: HWHEELRelativeAxisButtons: 6 7. (**) Mice0-usb-0000:00:02.0-1/input1: WHEELRelativeAxisButtons: 4 5. (II) Mice0-usb-0000:00:02.0-1/input1: Found 60 mouse buttons (II) Mice0-usb-0000:00:02.0-1/input1: Configured 64 mouse buttons (II) XINPUT: Adding extended input device "Mice0-usb-0000:00:02.0-1/input1" (type: KEYBOARD) (II) XINPUT: Adding extended input device "Keyboard0-usb-0000:00:02.0-1/input0" (type: KEYBOARD) (II) XINPUT: Adding extended input device "evdev brain" (type: evdev brain) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other) (II) Keyboard0-usb-0000:00:02.0-1/input0: Init (**) Mice0-usb-0000:00:02.0-1/input1: 36 valuators. (EE) evdev_btn.c (90): Registering 64 buttons. (II) Mice0-usb-0000:00:02.0-1/input1: Init (II) evdev brain: Rescanning devices (3). (II) Keyboard0-usb-0000:00:02.0-1/input0: On (II) Mice0-usb-0000:00:02.0-1/input1: On OPk, what I know want you too check is whether you have xkbdata och xkeyboard-config installed on your system. If you have xkbdata pull it from cvs and install it, if you have xkeyboard do a local bump of it to 0.8 (just comment out the patch, I have not checked if it is needed anymore). After that add Option "XkbModel" "evdev" to your Section "InputDevice" Identifier "Keyboard0" To be honest I have not yet gotten the multimedia-kerys working myself yet, but I at least got events from most of them (I think there is one or two I have no reaction in xev for). So I guess the rest is just me being lazy. Oh, and I tried local bump of evdev, it will not merge with xorg-server less then 1.0.99.992 (i think it was, it dies during configuration). Anyhow that version is not yet in portage, so I guess we just have to wait for xorg-server-1.1.0 before trying out that package. I tried emerging them, but xkeyboard-config blocks xkbdata. I didnt use portage to try evdev from cvs, i just pulled the sources and compiled them, and put the evdev_drv.so in the correct directory, saving a backup of the old one. You need to unmerge xkbdata and emerge xkeyboard-config. tried with xkeyboard-config-0.8 and XkbModel "evdev" Now almost everything is ok with the keyboard. the only wrong mapping is the "Menu" key which is wrongly mapped to symbol XF86Back. But still, the main problem is still not solved, i dont get any keyboard events from the mouse device when i use it with evdev, so i cant confirm on the mappings of the multimedia keys, because they come from that channel. Oh, forgot to mention, for some reason Super_L is not working alright. with xev i see the events from it pressing and releasing, but xbindkeys and windowmaker are not recognising some shortcuts i configured, like mod4+f. In fact, the "Capture" thing in wmakerconf for configuring the keyboard shortcuts doesnt get that im pressing the windows key. Please report results with xkeyboard-config 0.8, evdev driver 1.1.1 and reopen. Nothing really changed, all the problems i mentioned persist with evdev 1.1.1 and xkeyboard-config 0.8 Go ahead and file this upstream against the evdev driver at bugs.freedesktop.org in the xorg product. Attach your xorg.conf and /var/log/Xorg.0.log. Then post the URL here. Before doing so, make sure you can reproduce it when you aren't using any binary drivers. Thanks! |