From: Mikael Pettersson <mikpe@csd.uu.se>
To: vojtech@suse.cz
Cc: linux-kernel@vger.kernel.org
Subject: PS/2 mouse problems with 2.5 input drivers
Date: Sun, 16 Feb 2003 11:30:34 +0100 (MET) [thread overview]
Message-ID: <200302161030.LAA18138@kim.it.uu.se> (raw)
Vojtech,
The 2.5 input layer sometimes mishandles my PS/2 mice.
On my Dell Latitude, the external PS/2 mouse works, but the
sensitivity is way down compared to the 2.4 PS/2 driver.
(As in: I have to move the mouse much further with 2.5 to
move the mouse pointer a given distance on the screen.)
On resuming after suspend (apm), the mouse goes bonkers.
Even the tiniest mouse movement or key press seems to generate
too many and bogus events (it wreaks havoc in my xterm), the
PS/2 interrupt count goes up rapidly, and I get "psmouse.c:
Lost synchronization, throwing N bytes away." (for N in 1-3).
This is the last major HW-related problem I have with 2.5, and
it basically makes it impossible for me to use 2.5 on my laptop.
(Also, it seems the input layer detects most of my mice as
"ImPS/2 Generic Wheel Mouse", even though only one of them
is a wheel mouse. I don't know if that's a problem.)
/Mikael
next reply other threads:[~2003-02-16 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-16 10:30 Mikael Pettersson [this message]
2003-04-13 17:01 mikpe
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=200302161030.LAA18138@kim.it.uu.se \
--to=mikpe@csd.uu.se \
--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®