From: jbradford@dial.pipex.com
To: vojtech@suse.cz
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.X breaks PS/2 mouse
Date: Fri, 4 Oct 2002 21:20:26 +0100 [thread overview]
Message-ID: <200210042020.g94KKQX4007896@darkstar.example.net> (raw)
One of my 486 laptops has a special port on the side, for a dedicated trackball. I always assumed that it was electrically identical to the standard PS/2 mouse port, which is also present.
With 2.2.x, (I haven't tried 2.4.x on this machine), both the dedicated trackball and a standard external PS/2 mouse work fine, using /dev/psaux.
With 2.5.40, however, the behavior is as follows:
Booting:
With no pointing devices connected, just the port is detected:
serio: i8042 AUX port at 0x60, 0x64 irq 12
With the dedicated trackball connected, it also gets detected:
input: PS/2 Generic mouse on isa0060/serio1
serio: i8042 AUX port at 0x60, 0x64 irq 12
Same with a PS/2 mouse, it also gets detected:
input: PS/2 Generic mouse on isa0060/serio1
serio: i8042 AUX port at 0x60, 0x64 irq 12
Once booted:
Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:
Just to clarify, I am not trying to use them both at the same time.
X also works with the external PS/2 mouse, but not the dedicated trackball.
Any suggestions?
John.
next reply other threads:[~2002-10-04 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 20:20 jbradford [this message]
2002-10-04 20:15 ` 2.5.X breaks PS/2 mouse Vojtech Pavlik
2002-10-04 20:52 ` jbradford
2002-10-04 20:45 ` Vojtech Pavlik
2002-10-04 21:01 ` jbradford
2002-10-04 22:25 ` jbradford
2002-10-07 12:09 ` Vojtech Pavlik
2002-10-07 12:46 ` jbradford
2002-10-07 12:42 ` Vojtech Pavlik
2002-10-07 14:17 ` jbradford
2002-10-07 14:23 ` Vojtech Pavlik
2002-10-07 20:15 ` jbradford
2002-10-07 20:08 ` Vojtech Pavlik
2002-10-07 23:47 ` Thomas Molina
2002-10-07 15:25 ` [FUNNY] " jbradford
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=200210042020.g94KKQX4007896@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.