Skip to contentSkip to conversation

More mouse wheel problems

DISCUSSION Alex 2 participants 4 messages Feb 9, 2004

lore
Share & tools
lore

Alex

author
#0 lore raw

Hi,
I know mouse wheel problems have been discussed, but I am still having them even with the proper fixes. I have a generic-looking IBM optical wheel USB mouse, Model Number MO28B0 (O's could be zeros and vice versa).

In the 2.4 kernels, the USB mouse would register with the following message:

Nov  4 03:53:16 localhost kernel: usb.c: registered new driver usbmouse
Nov  4 03:53:16 localhost kernel: input0: ARROW STRONG USB 3D Mouse on usb1:3.0
Nov  4 03:53:16 localhost kernel: usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

Once I upgraded to 2.6.2, the mouse is identified as follows:

Feb  4 12:29:07 localhost kernel: input: ImPS/2 Generic Wheel Mouse on isa0060/serio1

The problem is that the mouse wheel does not work. My XF86Config-4 contains:
Section "InputDevice"

        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/input/mouse0"
        Option          "Protocol"              "ImPS/2"
        Option          "ZAxisMapping"          "4 5"

EndSection

I have tried with ExplorerPS/2 as suggested before, as well as with /dev/input/mice.

Trying to perform some diagnostics, I used hexdump and cat to look at the output of /dev/input/mouse0 and /dev/input/mice. In both cases, the devices produced quite a lot of output for mouse movement and button presses - for all three buttons - but no output whatsoever for wheel movements. Does this mean that the problem is with the kernel?

Thanks for your time,
Alex Khripin

#1 lore raw
Quoted 5 lines · Alex

Hi,
I know mouse wheel problems have been discussed, but I am still having them even with the proper fixes. I have a generic-looking IBM optical wheel USB mouse, Model Number MO28B0 (O's could be zeros and vice versa).

Quoted 7 lines

In the 2.4 kernels, the USB mouse would register with the following message:

Nov  4 03:53:16 localhost kernel: usb.c: registered new driver usbmouse
Nov  4 03:53:16 localhost kernel: input0: ARROW STRONG USB 3D Mouse on usb1:3.0
Nov  4 03:53:16 localhost kernel: usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

Once I upgraded to 2.6.2, the mouse is identified as follows:

Feb  4 12:29:07 localhost kernel: input: ImPS/2 Generic Wheel Mouse on isa0060/serio1

You moved the mouse from USB to PS/2 between the kernel upgrade? Where the mouse doesn't work properly - on USB or PS/2? They're wildly different interfaces and the mouse is using a different protocol on either.

Quoted 27 lines

The problem is that the mouse wheel does not work. My XF86Config-4 contains:
Section "InputDevice"

        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/input/mouse0"
        Option          "Protocol"              "ImPS/2"
        Option          "ZAxisMapping"          "4 5"

EndSection

I have tried with ExplorerPS/2 as suggested before, as well as with /dev/input/mice.

Trying to perform some diagnostics, I used hexdump and cat to look at the output of /dev/input/mouse0 and /dev/input/mice. In both cases, the devices produced quite a lot of output for mouse movement and button presses - for all three buttons - but no output whatsoever for wheel movements. Does this mean that the problem is with the kernel?

Thanks for your time,
Alex Khripin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
author
#2 lore raw

The mouse is in USB in both cases. I'll see if I can dig up my USB <-> PS/2 converter and try the mouse in PS/2 mode. But in this case, the mouse stayed plugged into USB the whole time.
-Alex

Quoted 50 lines · Vojtech Pavlik
Quoted 5 lines · Alex

Hi,
I know mouse wheel problems have been discussed, but I am still having them even with the proper fixes. I have a generic-looking IBM optical wheel USB mouse, Model Number MO28B0 (O's could be zeros and vice versa).

Quoted 7 lines

In the 2.4 kernels, the USB mouse would register with the following message:

Nov  4 03:53:16 localhost kernel: usb.c: registered new driver usbmouse
Nov  4 03:53:16 localhost kernel: input0: ARROW STRONG USB 3D Mouse on usb1:3.0
Nov  4 03:53:16 localhost kernel: usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

Once I upgraded to 2.6.2, the mouse is identified as follows:

Feb  4 12:29:07 localhost kernel: input: ImPS/2 Generic Wheel Mouse on isa0060/serio1

You moved the mouse from USB to PS/2 between the kernel upgrade? Where the mouse doesn't work properly - on USB or PS/2? They're wildly different interfaces and the mouse is using a different protocol on either.

Quoted 27 lines

The problem is that the mouse wheel does not work. My XF86Config-4 contains:
Section "InputDevice"

        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/input/mouse0"
        Option          "Protocol"              "ImPS/2"
        Option          "ZAxisMapping"          "4 5"

EndSection

I have tried with ExplorerPS/2 as suggested before, as well as with /dev/input/mice.

Trying to perform some diagnostics, I used hexdump and cat to look at the output of /dev/input/mouse0 and /dev/input/mice. In both cases, the devices produced quite a lot of output for mouse movement and button presses - for all three buttons - but no output whatsoever for wheel movements. Does this mean that the problem is with the kernel?

Thanks for your time,
Alex Khripin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#3 lore raw
Quoted 3 lines · Alex

The mouse is in USB in both cases. I'll see if I can dig up my USB <-> PS/2 converter and try the mouse in PS/2 mode. But in this case, the mouse stayed plugged into USB the whole time.

Then you forgot to load the USB drivers and the BIOS is doing emulation of a PS/2 mouse. That'd explain the wheel problem, too. You need to load the USB (uhci/ohci-hcd, and hid) drivers.

Quoted 21 lines

-Alex

Quoted 18 lines · Vojtech Pavlik
Quoted 5 lines · Alex

Hi,
I know mouse wheel problems have been discussed, but I am still having them even with the proper fixes. I have a generic-looking IBM optical wheel USB mouse, Model Number MO28B0 (O's could be zeros and vice versa).

Quoted 7 lines

In the 2.4 kernels, the USB mouse would register with the following message:

Nov  4 03:53:16 localhost kernel: usb.c: registered new driver usbmouse
Nov  4 03:53:16 localhost kernel: input0: ARROW STRONG USB 3D Mouse on usb1:3.0
Nov  4 03:53:16 localhost kernel: usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

Once I upgraded to 2.6.2, the mouse is identified as follows:

Feb  4 12:29:07 localhost kernel: input: ImPS/2 Generic Wheel Mouse on isa0060/serio1

You moved the mouse from USB to PS/2 between the kernel upgrade? Where the mouse doesn't work properly - on USB or PS/2? They're wildly different interfaces and the mouse is using a different protocol on either.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR