From: Kim Holviala <kim@holviala.com>
To: linux-kernel@vger.kernel.org
Cc: Vitez Gabor <gabor@swszl.szkp.uni-miskolc.hu>
Subject: Re: 2.6.5 : problem with MS Intellimouse Explorer buttons when using X
Date: Sun, 11 Apr 2004 22:16:33 +0300 [thread overview]
Message-ID: <200404112216.33308.kim@holviala.com> (raw)
In-Reply-To: <20040410135327.GA12573@swszl.szkp.uni-miskolc.hu>
On Saturday 10 April 2004 16:53, Vitez Gabor wrote:
> I recently ugraded from 2.4.23 to 2.6.5. Everything works fine, except for
> my mouse: when I press the buttons on the left side of the mouse, the
> system generates button press/release events for the proper buttons and for
> the buttons on the top of the mouse. The mouse worked well with 2.4.23.
2.4 and 2.6 handle mouse differently; 2.4 has /dev/psaux which is just a
direct channel into the port while 2.6 inteprets all mouse stuff and
regenerates a virtual /dev/psaux.
Try modprobing the even device (modprobe evdev) to get /dev/input/event?. Then
run hexdump -C /dev/input/event1 (or whatever even device represents your
mouse) to see what REALLY happens in the kernel. Don't worry about the first
8 octets, the stuff you want is in the last 8. Might be a good idea to switch
to a console so that extra mouse clicks won't do any strange things.
> Option "Protocol" "ExplorerPS/2"
> # Option "Protocol" "ImPS/2"
> Option "Buttons" "7"
> Option "ZAxisMapping" "6 7"
I use an Explorer at work, don't have the Buttons directive at all and my
ZAxMap is "4 5". That way everything works, but the side buttons are missing.
That's with 2.6.5 and Gentoo.
Kim
next prev parent reply other threads:[~2004-04-11 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 13:53 2.6.5 : problem with MS Intellimouse Explorer buttons when using X Vitez Gabor
2004-04-11 19:16 ` Kim Holviala [this message]
2004-04-12 10:16 ` Vitez Gabor
2004-04-13 5:46 ` Kim Holviala
2004-04-13 5:47 ` Kim Holviala
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=200404112216.33308.kim@holviala.com \
--to=kim@holviala.com \
--cc=gabor@swszl.szkp.uni-miskolc.hu \
--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