From: Vojtech Pavlik <vojtech@suse.cz>
To: jbradford@dial.pipex.com
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: 2.5.X breaks PS/2 mouse
Date: Fri, 4 Oct 2002 22:15:54 +0200 [thread overview]
Message-ID: <20021004221554.A49104@ucw.cz> (raw)
In-Reply-To: <200210042020.g94KKQX4007896@darkstar.example.net>; from jbradford@dial.pipex.com on Fri, Oct 04, 2002 at 09:20:26PM +0100
On Fri, Oct 04, 2002 at 09:20:26PM +0100, jbradford@dial.pipex.com wrote:
> 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
This is OK.
> 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
Also OK.
> 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
Also OK.
> Once booted:
>
> Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:
Good, this is expected.
> Just to clarify, I am not trying to use them both at the same time.
Not sure if that would work, it might - depends on the notebook keyboard
controller hardware.
> X also works with the external PS/2 mouse,
Good.
> but not the dedicated trackball.
What are the exact symptoms? Does gpm work? Does cat /dev/psaux work? Does cat
/dev/input/mice work? What does cat /proc/bus/input/devices say in the
case it doesn't work? ....
> Any suggestions?
Just questions at this time ...
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-10-04 20:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 20:20 2.5.X breaks PS/2 mouse jbradford
2002-10-04 20:15 ` Vojtech Pavlik [this message]
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=20021004221554.A49104@ucw.cz \
--to=vojtech@suse.cz \
--cc=jbradford@dial.pipex.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 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.