You are not logged in.
Hi guys!
Recently I bought a Sharkoon Drakonia gaming mouse. I knew there were problems getting this mouse working at all, but since there is a patch I bought it anyway. As long as the patch hasn't found it's way into the kernel, I'm using this package from AUR. Until now, it works pretty good, except one thing:
If I check the buttons with "xev | grep button", button 1-9 work perfectly. But if I click button 10 (the lowest thumb button) the output I get says, its button 1 and button 11 (at the right side of the mouse) seems to be not recognized at all and gives me no output.
Here's the relevant part of xorg.conf:
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
#InputDevice "Mouse0" "CorePointer"
InputDevice "Evdev Mouse" "CorePointer"
Option "BlankTime" "60"
Option "StandbyTime" "60"
Option "SuspendTime" "60"
Option "OffTime" "60"
EndSection
[...]
Section "InputDevice"
Identifier "Evdev Mouse"
Driver "evdev"
Option "Name" "Holtek USB Gaming Mouse"
Option "evBits" "+1-2"
Option "keyBits" "~272-287"
Option "relBits" "~0-2 ~6 ~8"
Option "Pass" "3"
Option "Protocol" "auto"
Option "Buttons" "11"
Option "ButtonMapping" "1 2 3 4 5 6 7 8 9 10 11"
Option "CorePointer"
EndSection
Is there any possibility to get these two buttons working?
Belshi
Offline
Try with `xinput test <id>` (`xinput list` to find the id). Also, check xev's output without filtering it.
Offline
The unfiltered output from xev:
Clicking the lowest thumb button and left button give me the same output:
ButtonPress event, serial 33, synthetic NO, window 0x3a00001,
root 0x292, subw 0x0, time 9242572, (163,165), root:(164,244),
state 0x0, button 1, same_screen YES
ButtonRelease event, serial 33, synthetic NO, window 0x3a00001,
root 0x292, subw 0x0, time 9242636, (163,165), root:(164,244),
state 0x100, button 1, same_screen YES
same for xinput test:
button press 1
button release 1
Clicking button 11 doesn't do anything.
I noticed that when I do a xinput list, the my mouse is listed under "Virtual core pointer" as well as under "Virtual core keyboard".
$ xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ HID 046a:0023 id=10 [slave pointer (2)]
⎜ ↳ Holtek USB Gaming Mouse id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ UVC Camera (046d:0825) id=8 [slave keyboard (3)]
↳ HID 046a:0023 id=9 [slave keyboard (3)]
↳ Holtek USB Gaming Mouse id=11 [slave keyboard (3)]
↳ Eee PC WMI hotkeys id=13 [slave keyboard (3)]
Is that a normal behaviour?
Last edited by Belshi (2013-07-26 12:06:46)
Offline
I might be wrong, but I think you should add
MatchIsPointer "yes"
in the section with `Driver "evdev"` — without it X will try to apply those settings to other evdev devices (not only the mouse).
This should fix the keyboard output of `xinput list`, although I have no idea how to fix your main problem. I'd say it's something with the driver, since with misconfigured X you should get at least *something* when pressing button 11.
Some ideas:
$ xinput get-button-map <id> # although, as stated above, I don't think the problem is here
$ xinput list-props <id> # may be useful for people who know about this more than I do
Offline
only adding
MatchIsPointer "on" # in other examples 'on' was used instead of 'yes'
breaks Xorg. It doesn't even start. But thanks for the hint, I'll try it again later
xinput get-button-map <id> gives me the same list of numbers which is defined under "ButtonMapping" in my xorg.conf.
- - -
EDIT:
I was wrong with the button map. It shows me 13 buttons:
$ xinput get-button-map 12
1 2 3 4 5 6 7 8 9 10 11 12 13
- - -
xinput list-props <id>
gives me the following output:
$ xinput list-props 12
Device 'Holtek USB Gaming Mouse':
Device Enabled (142): 1
Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (268): 0
Device Accel Constant Deceleration (269): 1.000000
Device Accel Adaptive Deceleration (270): 1.000000
Device Accel Velocity Scaling (271): 10.000000
Device Product ID (262): 1241, 41063
Device Node (263): "/dev/input/event13"
Evdev Axis Inversion (272): 0, 0
Evdev Axes Swap (274): 0
Axis Labels (275): "Rel X" (152), "Rel Y" (153), "Rel Horiz Wheel" (267), "Rel Dial" (291), "Rel Vert Wheel" (292)
Button Labels (276): "Button Left" (145), "Button Middle" (146), "Button Right" (147), "Button Wheel Up" (148), "Button Wheel Down" (149), "Button Horiz Wheel Left" (150), "Button Horiz Wheel Right" (151), "Button Side" (289), "Button Extra" (290), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265), "Button Unknown" (265)
Evdev Middle Button Emulation (277): 1
Evdev Middle Button Timeout (278): 50
Evdev Third Button Emulation (279): 0
Evdev Third Button Emulation Timeout (280): 1000
Evdev Third Button Emulation Button (281): 3
Evdev Third Button Emulation Threshold (282): 20
Evdev Wheel Emulation (283): 0
Evdev Wheel Emulation Axes (284): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (285): 10
Evdev Wheel Emulation Timeout (286): 200
Evdev Wheel Emulation Button (287): 4
Evdev Drag Lock Buttons (288): 0
Last edited by Belshi (2013-07-26 13:24:21)
Offline