I have an xGene (P/N 01027) wireless keyboard/mouse. X identifies it as a "HOLTEK Wireless Keyboard/Mouse(2.4G)". My problems with the mouse depend on which version of hal I'm using and on which X mouse driver I use in xorg.conf (mouse or evdev). Here are the details, and the corresponding Xorg error messages: With hal-0.5.9.1-r3: xf86-input-mouse: good, no problems! xf86-input-evdev: no cursor movement (EE) ioctl EVIOCGBIT 0 failed: Inappropriate ioctl for device (EE) Mouse1: cannot load bits (EE) PreInit returned NULL for "Mouse1" With hal-0.5.10: xf86-input-mouse: no X axis movement expected keysym, got XF86Info: line 914 of inet evdev: leds are 0x0 for device 4 (EE) HOLTEK Wireless Keyboard/Mouse(2.4G): Unable to parse 'RelAxis 0' as a map specifier. (EE) HOLTEK Wireless Keyboard/Mouse(2.4G): AbsoluteTouch: 'DIGI_Touch' does not exist. expected keysym, got XF86Info: line 914 of inet evdev: leds are 0x0 for device 5 expected keysym, got XF86Info: line 914 of inet evdev: leds are 0x0 for device 6 xf86-input-evdev: no X axis movement (EE) ioctl EVIOCGBIT 0 failed: Inappropriate ioctl for device (EE) Mouse1: cannot load bits (EE) PreInit returned NULL for "Mouse1" expected keysym, got XF86Info: line 914 of inet evdev: leds are 0x0 for device 3 (EE) HOLTEK Wireless Keyboard/Mouse(2.4G): Unable to parse 'RelAxis 0' as a map specifier. (EE) HOLTEK Wireless Keyboard/Mouse(2.4G): AbsoluteTouch: 'DIGI_Touch' does not exist. expected keysym, got XF86Info: line 914 of inet evdev: leds are 0x0 for device 4 expected keysym, got XF86Info: line 914 of inet evdev: leds are 0x0 for device 5 The keyboard works fine with both hal versions and both the xf86-input-keyboard and xf86-input-evdev drivers, although evdev causes X to throw some errors about the keyboard. Reproducible: Always Steps to Reproduce: 1. plug in a HOLTEK Wireless Keyboard/Mouse 2. use one of the above configurations 3. launch X Here are the relevant sections of my xorg.conf: Section "ServerLayout" Identifier "Simple Layout" Screen "Screen 1" 0 0 InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" EndSection Section "InputDevice" Identifier "Keyboard1" Driver "keyboard" Option "AutoRepeat" "500 30" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "Auto" # Auto detect Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5" EndSection
Created attachment 148893 [details] emerge --info
With the newer hal, X won't listen to your xorg.conf. It will always use the evdev driver if it's installed. This sounds to me like the evdev driver doesn't work for you.
It sounds like this is a bug in evdev. Where is the most appropriate place to report this?
(In reply to comment #3) > It sounds like this is a bug in evdev. Where is the most appropriate place to > report this? evdev's changed a lot lately. Could you test the latest development version? Here's how to do this: emerge layman autounmask echo 'source /usr/portage/local/layman/make.conf' >> /etc/make.conf layman -L layman -a x11 autounmask x11-drivers/xf86-input-evdev-9999 emerge xf86-input-evdev
Oops, forgot to follow up: evdev from git works great. Hopefully this will be in the next release.
Worked for me like a charm. Thanks a lot people, this had me running around in circle for days.
This looks fixed to me, thanks to the newer evdev drivers. If you disagree, please reopen.
