From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: logitech mouseMan wheel doesn't work with 2.6.5
Date: Tue, 20 Apr 2004 07:14:56 -0700 [thread overview]
Message-ID: <40853060.2060508@bigfoot.com> (raw)
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.
Here's the most basic/simple situation/symptoms:
I stop X, read bytes from /dev/psaux (c program, using open and
read). for each mouse action there are few bytes read, usually number
(depends on action), 8 (almost all the time, at least for clicks)), few
zeros. I don't have exact log but here's what it looked like:
left click: some number, 8, 0, 0
middle click: some number, 8, 0, 0
right click: some number, 8, 0, 0
side button: middle click number, 8, 0, 0
wheel clockwise: 8, 0, 0
wheel counterclockwise: 8, 0, 0
exact numbers don't matter (I think), the point is that it is not
possible to tell side button click from middle click and the wheel
rotation sends same info no matter in which direction the wheel is
rotated, it seems to miss the first byte that in case of other buttons
tells what's going on.
BTW X windows is confused in the same way (I guess because that's
what it gets from kernel driver - using xev I found that it thinks the
sidebutton is button 2 and that turning the wheel is not an event at all).
any ideas how to make kernel understand the mouse better? or is this
a kernel bug? I've read that kernel now interprets the mouse protocol -
but there doesn't seem to be a way to indicate to kernel which protocol
to use...
system:
debian unstable
kernel-source-2.6.5
logitech cordless mouseMan wheel
mouse connected via /dev/psaux
mouse related kernel config:
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1280
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1024
CONFIG_INPUT_MOUSEDEV_PSAUX_ENABLE=y
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set
...
#
# Input Device Drivers
#
...
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
the mouse used to work with 2.2 and 2.4 kernels.
TIA
erik
next reply other threads:[~2004-04-20 14:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 14:14 Erik Steffl [this message]
2004-04-20 15:22 ` logitech mouseMan wheel doesn't work with 2.6.5 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
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=40853060.2060508@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