From: jbradford@dial.pipex.com
To: vojtech@suse.cz (Vojtech Pavlik)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.X breaks PS/2 mouse
Date: Mon, 7 Oct 2002 15:17:13 +0100 (BST) [thread overview]
Message-ID: <200210071417.g97EHDjG006197@darkstar.example.net> (raw)
In-Reply-To: <20021007144250.A626@ucw.cz> from "Vojtech Pavlik" at Oct 07, 2002 02:42:50 PM
> > > > Pressing the left button, then the right button, (this is complete, and follows the above immediately):
> > > >
> > > > i8042.c: 01 <- i8042 (interrupt, aux, 12) [230409]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230410]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230411]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230548]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230552]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230554]
> > > > i8042.c: 02 <- i8042 (interrupt, aux, 12) [231505]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231506]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231507]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231694]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231695]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231696]
> > > >
> > > > So, it definitely seems to be sending data to the port... Strange...
> > >
> > > It must work. I'm really wondering why it doesn't. What happens when you
> > > load the 'evbug' module?
> >
> > I can't very easily - the kernel on the machine doesn't have kernel module
> > support enabled, and with 4MB RAM, it's really painfully slow to work with
> > if I use a kernel with modules enabled. If there is no other way to debug
> > it, I can try, but it's a last resort :-)
>
> Do you have 'evdev' (Event interface) compiled in? It'd be a replacement
> for evbug ...
I didn't, but I've compiled a new kernel with it in. Unfortunately, it doesn't seem to do anything useful :-(.
cat /dev/input/eventX | hexdump
returns nothing, not even for keyboard events, which makes me think I've gone wrong somewhere :-/
> > Something that occurred to me, and I could be totally wrong here, but
> > is it possible that the trackball is being detected as a "generic
> > mouse" when it isn't one?
>
> Most likely (95%) it behaves a generic ps/2 mouse. After all, it seems
> to send generic ps/2 data. Why the data isn't getting through, is the
> question.
>
> > I tried connecting the generic mouse, disconnecting it, and then
> > connecting the trackball, and saw in dmesg that some kind of handshake
> > was going on. This was completely different for mouse and trackball.
> > Would it be any use to post this output?
>
> If it was different, then definitely!
Sorry, I was wrong, I think I pressed a mouse button whilst connecting it and mis-read the info. The init is exactly the same.
However, the data sent from each one seems to be very different, (I've re-formatted this a bit to save space, but it's from the dmesg output):
mouse
Left button - 09 00 00 08 00 00
Right button - 0a 00 00 08 00 00
trackball
Left button - 01 00 00 00 00 00
Right button - 02 00 00 00 00 00
> > If the evbug module is the only way to go, I'll try it, but it'll
> > probably take me the rest of the day, (seriously) :-).
>
> Let's try other ways before that.
Good idea :-)
John.
next prev parent reply other threads:[~2002-10-07 14:06 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
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 [this message]
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=200210071417.g97EHDjG006197@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.