From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: logitech mouseMan wheel doesn't work with 2.6.5
Date: Sat, 24 Apr 2004 00:27:39 -0700 [thread overview]
Message-ID: <408A16EB.30208@bigfoot.com> (raw)
In-Reply-To: <200404202326.24409.kim@holviala.com>
Kim Holviala wrote:
> On Tuesday 20 April 2004 17:14, Erik Steffl wrote:
>
>
>> it looks that after update to 2.6.5 kernel (debian source package but
>>I guess it would be the same with stock 2.6.5) the mouse wheel and side
>>button on Logitech Cordless MouseMan Wheel mouse do not work.
>
>
> Try my patch for 2.6.5: http://lkml.org/lkml/2004/4/20/10
>
> Build psmouse into a module (for easier testing) and insert it with the proto
> parameter. I'd say "modprobe psmouse proto=exps" works for you, but you might
> want to try imps and ps2pp too. The reason I wrote the patch in the first
> place was that a lot of PS/2 Logitech mice refused to work (and yes, exps
> works for me and others)....
didn't help, I still see (without X running):
8, 0, 0 any button down
9, 0, 0 left button up
12, 0, 0 wheel up, sidebutton up
10, 0, 0 right button up
8, 0, 0 wheel rotation (any direction)
except of some protocols (IIRC ps2pp, bare, genps) ignore wheel
completely. is there any way to verify which protocol the mouse is
using? modprobe -v printed different messages for each protocol so I
think that worked (it said Generic Explorer etc.)
I tried: exps, imps, ps2pp, bare, genps
any ideas?
the mouse says: Cordless MouseMan Wheel (Logitech), it has left/right
buttonss, wheel that can be pushed or rotated and a side button, not
sure how to better identify it. With 2.4 kernels it used to work with X
using protocol MouseManPlusPS/2.
erik
next prev parent reply other threads:[~2004-04-24 7:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 14:14 logitech mouseMan wheel doesn't work with 2.6.5 Erik Steffl
2004-04-20 15:22 ` Paul Rolland
2004-04-20 15:36 ` Craig Bradney
2004-04-20 18:14 ` Kim Holviala
2004-04-20 19:06 ` Erik Steffl
2004-04-20 20:18 ` Craig Bradney
2004-04-20 19:03 ` Erik Steffl
2004-04-20 20:26 ` Kim Holviala
2004-04-20 23:31 ` Erik Steffl
2004-04-20 23:41 ` Randy.Dunlap
2004-04-24 7:27 ` Erik Steffl [this message]
2004-04-24 8:41 ` Craig Bradney
2004-04-27 23:18 ` Erik Steffl
2004-04-27 23:29 ` Craig Bradney
2004-04-27 23:56 ` Erik Steffl
2004-04-28 7:13 ` Craig Bradney
2004-04-28 7:22 ` Kim Holviala
2004-04-28 8:21 ` Erik Steffl
2004-04-28 8:36 ` Craig Bradney
2004-04-28 12:41 ` Dmitry Torokhov
2004-04-28 18:47 ` Erik Steffl
2004-04-28 23:24 ` Dmitry Torokhov
2004-04-29 6:34 ` Erik Steffl
2004-06-02 23:39 ` Vojtech Pavlik
[not found] <1N4qh-4Ct-13@gated-at.bofh.it>
2004-04-21 16:08 ` Frank Otto
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=408A16EB.30208@bigfoot.com \
--to=steffl@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
/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