public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan <wfilardo@fuse.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Mouse under 2.5.3-dj3
Date: Thu, 07 Feb 2002 21:54:19 -0500	[thread overview]
Message-ID: <3C633DDB.9050607@fuse.net> (raw)

To follow up on my previous postings of a long while ago.

I have a very boring trackpad mouse on a Sony VAIO R505JE laptop.  At 
least, 2.4.18-pre7 thinks it's normal PS/2 and uninteresting.  2.5.3-dj* 
on the other hand, seems to be horribly confused.  I rebuilt it with 
everything mouse related as modules just so I didn't have to reboot when 
it misdetected my mouse.

First, I modprobe mousedev, then psmouse.
Mousedev always is cool and loads without a problem, printing out its 
"PS/2 mouse device common for all mice" message.

~90% of the time, psmouse does not detect a mouse.  Doesn't work, obviously.
~5% of the time, psmouse reports I have a "PS/2 Generic Mouse on 
isa0060/serio1".
    At such times, the mouse works, but a complete cross on the trackpad 
is ~100 pixels at best.
~1% of the time, psmouse blurts "Failed to enable mouse on 
isa0060/serio1"  Here the mouse does not work.
~4% of the time, psmouse prints "PS/2 Logitech Mouse on isa0060/serio1" 
 This is the correct mode of behavior.

As it is I run "modprobe mousedev; while < /dev/zero; do modprobe 
psmouse; echo -n "a"; sleep 1; done" and wait for the Logitech message 
to give the loop a Ctrl-C.  There has to be a better way, and more 
information I can provide.

FYI, keyboard glitches *seem* to have disappeared.

--Nathan



             reply	other threads:[~2002-02-08  2:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08  2:54 Nathan [this message]
2002-02-08  7:20 ` Mouse under 2.5.3-dj3 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=3C633DDB.9050607@fuse.net \
    --to=wfilardo@fuse.net \
    --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