From: Vojtech Pavlik <vojtech@suse.cz>
To: jbradford@dial.pipex.com
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.X breaks PS/2 mouse
Date: Fri, 4 Oct 2002 22:45:47 +0200 [thread overview]
Message-ID: <20021004224547.A49400@ucw.cz> (raw)
In-Reply-To: <200210042052.g94KqQmB008165@darkstar.example.net>; from jbradford@dial.pipex.com on Fri, Oct 04, 2002 at 09:52:26PM +0100
On Fri, Oct 04, 2002 at 09:52:26PM +0100, jbradford@dial.pipex.com wrote:
> > > 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.
>
> I tried it, and it seems to get really confused - constant stream of seemingly random error messages.
>
> > > X also works with the external PS/2 mouse,
> >
> > Good.
> >
> > > but not the dedicated trackball.
> >
> > What are the exact symptoms?
>
> No data at all from it.
>
> > Does gpm work?
>
> No.
>
> > Does cat /dev/psaux work?
>
> It doesn't say No such device, it just hangs, giving no data for the trackball, but works fine for the generic mouse.
>
> > Does cat /dev/input/mice work?
>
> Yes, it does the same as /dev/psaux
>
> > What does cat /proc/bus/input/devices say in the
> > case it doesn't work? ....
>
> I: Bus=0011 Vendor=0002 Product=0001 Version=0000
> N: Name="PS/2 Generic Mouse"
> P: Phys=isa0060/serio1/input0
> H: Handlers=mouse0
> B: EV=7
> B: KEY=70000 0 0 0 0 0 0 0 0
> B: REL=3
>
> That's for both the generic mouse and the trackball.
Ok. Can you try the usual #define I8042_DEBUG_IO in
drivers/input/serio/i8042.h?
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-10-04 20:40 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
2002-10-04 20:52 ` jbradford
2002-10-04 20:45 ` Vojtech Pavlik [this message]
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=20021004224547.A49400@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.