login
Search
I am a debian user and I recently upgraded my kernel from 2.4.X to 2.6.10.
My mouse wheel does not seem to be working, while the mouse works in all other ways.
xev does not show any output when i spin the mouse wheel.
cat /dev/input/mice does not show any output when i spin the mouse wheel.
My XF86Config-4 mouse section is:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Buttons" "5"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
EndSection
I have tried removing "Buttons" 5
I have tried ImPS/2 protocol.
$ cat /proc/bus/input/devices
...
I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103
dmesg has this towards the end of it... but i suspect it is unrelated
atkbd.c: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0).
atkbd.c: Use 'setkeycodes e03e ' to make it known.
atkbd.c: Unknown key released (translated set 2, code 0xbe on isa0060/serio0).
atkbd.c: Use 'setkeycodes e03e ' to make it known.
It is a microsoft intellimouse... but i tried switching in a few other mice and had the same problem.
Any help would be much apprieciated, im out of ideas on my own....
thanks in advance,
jason
USB?
The P: Phys=isa0060/serio1/input0 line indicates, that your mouse is connected through the PS/2 mouse port, not USB. (Btw: the error messages in dmesg talk about isa0060/serio0, which is 'the other' PS/2-connector, namely the keyboard).
If cat /dev/inout/mice really shows nothing (you should pipe it through hd (hexdump) to see the NUL bytes), you will not get far with the X configuration, because the kernel never creates the wheel events. Are there module parameters or similar, which can make the kernel do that?
My mice (both fully working in parallel, in particular the scroll wheels) show as
, so nothing looks wrong about your mouse.
'cat /dev/input/mice | hex' gives lots of '08 00 00' byte sequences both for scrolling up and down.
USB controller
Hey
I was having this same problem today with my brand-spankin' nforce3 board. I don't know if this changed from 2.4 to 2.6, but the kernel config defaults to USB-UHCI host controller which is typically used for via and intel chipsets. The nforce3, however, uses the OHCI host controller. So, cd ..linux-2.6.10 , make menuconfig, device drivers, usb support, select OHCI HCD support. recompile, etc.
This was drivin' me nuts. Same exact thing..mouse works but no wheel . It took my usb printer not working for me to figure it out.
Hope that helps
j
(From thread creator) [quo
(From thread creator)
[quote]
I was having this same problem today with my brand-spankin' nforce3 board. I don't know if this changed from 2.4 to 2.6, but the kernel config defaults to USB-UHCI host controller which is typically used for via and intel chipsets. The nforce3, however, uses the OHCI host controller. So, cd ..linux-2.6.10 , make menuconfig, device drivers, usb support, select OHCI HCD support. recompile, etc.
[/quote]
Yeah, something similar to that turned out to be the problem. I went into my kernel config and flipped on about 5 more usb options and it started working. It is fixed now. Thanks!
[quote]
The P: Phys=isa0060/serio1/input0 line indicates, that your mouse is connected through the PS/2 mouse port, not USB.
[/quote]
Nope it still reports that Phys=... and it is definitely plugged into a usb port. My PS2 port is empty.
Protocol could still be wrong
Have you tried the ExplorerPS/2 protocol? That's the one I use on my box, and it seems to work (Logitech mouse).