Results 1 to 4 of 4
I have 2 mice, one works one doesn't.
The one that doesn't work is a usb "wireless intellimouse explorer" It has 7 buttons (scroller counts as 3, up, down, push)
...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 11-04-2004 #1Linux User
- Join Date
- Jul 2004
- Posts
- 256
X.org mouse config?
I have 2 mice, one works one doesn't.
The one that doesn't work is a usb "wireless intellimouse explorer" It has 7 buttons (scroller counts as 3, up, down, push)
I can't figure out which protocol to use. Whatever I try the mouse either jumps to the corners and stays there, or I can move the mouse *okay* but only up-down, not left-right.
I know the problem is with the MouseUSB, because if I comment that out in my ServerLayout, my first mouse works fine.
What Protocol do I need for my second mouse?
xorg.confMaybe this boot output will helpCode:Section "InputDevice" # Identifier and driver Identifier "MouseUSB" Driver "mouse" Option "Protocol" "ExplorerPS/2"#"IntelliMousePS/2" #"auto" Option "Device" "/dev/input/mice" Option "Buttons" "7" #5 Option "ZAxisMapping" "6 7" #4 5 EndSection Section "ServerLayout" Identifier "Simple Layout" Screen "Screen 1" InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" InputDevice "MouseUSB" "SendCoreEvents" EndSectionCode:[jake@localhost: ~]$ dmesg | grep usb usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb.c: new USB bus registered, assigned bus number 1 usb.c: new USB bus registered, assigned bus number 2 usb.c: new USB bus registered, assigned bus number 3 usb.c: new USB bus registered, assigned bus number 4 usb.c: USB device 2 (vend/prod 0x45e/0x59) is not claimed by any active driver. usb.c: registered new driver usbmouse input0: Microsoft Microsoft Wireless Intellimouse Explorer® 1.0A on usb2:2.0 usbmouse.c: v1.6:USB HID Boot Protocol mouse driver usb.c: registered new driver hiddev usb.c: registered new driver hid
--monkey
- 11-06-2004 #2Linux Newbie
- Join Date
- Jul 2004
- Location
- Oklahoma City, OK
- Posts
- 232
Keep in mind, I'm running Slackware and I've never tried to set up a 7 button mouse.
The first change I'd make would be to change the protocol to IMPS/2. Then, I'd make a change to the ServerLayout. Make "SendCoreEvents" "AlwaysCore".
Also, make sure you have the values correct for ZAxisMapping. You might try "4 5" instead of "6 7".OH NOOOOO!!!!!! You did it the way I said?
- 11-06-2004 #3Linux User
- Join Date
- Jul 2004
- Posts
- 256
I'm also running slackware.
I just tried protocol IMPS/2 then I tried ExplorerPS/2. Neither worked.
Code:Section "InputDevice" Identifier "MouseUSB" Driver "mouse" Option "Protocol" "ExplorerPS/2"#"IntelliMousePS/2" #"auto" #Option "Protocol" "IMPS/2" #usb microsoft intellimouse explorer wireless Option "Device" "/dev/input/mice" Option "Buttons" "7" Option "ZAxisMapping" "6 7" Option "Emulate3Buttons" "no" #not needed? EndSection Section "ServerLayout" InputDevice "Mouse1" "CorePointer" #ps/2 mouse that works InputDevice "Keyboard1" "CoreKeyboard" #jake added: usb mouse InputDevice "MouseUSB" "SendCoreEvents" #USB mouse doesn't work EndSectionI know the wheel will not be scrolling, but once I get the correct protocol, I can useU-Turn:
Also, make sure you have the values correct for ZAxisMapping. You might try "4 5" instead of "6 7".To get the wheel to scroll.Code:$ xmodmap -e "pointer = 1 2 3 6 7 4 5"
Here's the logs,Code:(**) MouseUSB: Device: "/dev/input/mice" (**) MouseUSB: Protocol: "IMPS/2" (**) Option "SendCoreEvents" (**) MouseUSB: always reports core events (**) Option "Device" "/dev/input/mice" (**) Option "Buttons" "7" (**) Option "Emulate3Buttons" "no" (**) Option "ZAxisMapping" "6 7" (**) MouseUSB: ZAxisMapping: buttons 6 and 7 (**) MouseUSB: Buttons: 7 (II) XINPUT: Adding extended input device "MouseUSB" (type: MOUSE) (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other) (II) Mouse1: ps2EnableDataReporting: succeeded (II) MouseUSB: ps2EnableDataReporting: succeeded
They don't appear to have anything wrong...Code:(**) MouseUSB: Device: "/dev/input/mice" (**) MouseUSB: Protocol: "ExplorerPS/2" (**) Option "SendCoreEvents" (**) MouseUSB: always reports core events (**) Option "Device" "/dev/input/mice" (**) Option "Buttons" "7" (**) Option "Emulate3Buttons" "no" (**) Option "ZAxisMapping" "6 7" (**) MouseUSB: ZAxisMapping: buttons 6 and 7 (**) MouseUSB: Buttons: 7 (II) XINPUT: Adding extended input device "MouseUSB" (type: MOUSE) (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other) (II) Mouse1: ps2EnableDataReporting: succeeded (II) MouseUSB: ps2EnableDataReporting: succeeded
Maybe I need to update my kernel/kernel modules? I found this when searching, I don't know what it means:
Any ideas? I'm stumped.This is definately so, because ehci is only for USB 2.0, ohci and uhci only for 1.*.stormer wrote:
Attention!
ehci-hcd is no enough driver support to get the wheel working whit sis usb controller.
You have to compile ohci-hcd too, with both every thing works find with IMPS/2 drivers.
It is true for both 2.4 and 2.6 kernel.
Have fun!
p.s. It is probably the same whit Via chips using uhci-hcd.
--monkey
- 11-06-2004 #4Linux User
- Join Date
- Jul 2004
- Posts
- 256
What is usbmouse? Some reason if I remove that module, my mouse now works...
Is it too old or something? I'm using slack10 but I haven't updated my kernel 2.4.26--monkey


Reply With Quote
