From: Alex <akhripin@mit.edu>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Alex <akhripin@mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: More mouse wheel problems
Date: Mon, 9 Feb 2004 17:29:31 -0500 [thread overview]
Message-ID: <20040209222930.GX18567@open-boozeware.mit.edu> (raw)
In-Reply-To: <20040209220523.GA827@ucw.cz>
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
On Mon, Feb 09, 2004 at 11:05:23PM +0100, Vojtech Pavlik wrote:
> On Mon, Feb 09, 2004 at 12:24:48PM -0500, Alex wrote:
> > 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
>
> 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.
>
> >
> > 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 majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
>
> --
> Vojtech Pavlik
> SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-02-09 22:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 17:24 Alex
2004-02-09 22:05 ` Vojtech Pavlik
2004-02-09 22:29 ` Alex [this message]
2004-02-09 23:08 ` Vojtech Pavlik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040209222930.GX18567@open-boozeware.mit.edu \
--to=akhripin@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®