From: Derek Chen-Becker <derek@chen-becker.org>
To: Kim Holviala <kim@holviala.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Troubleshooting PS/2 mouse in 2.6.5
Date: Tue, 27 Apr 2004 08:06:01 -0600 [thread overview]
Message-ID: <408E68C9.5010102@chen-becker.org> (raw)
In-Reply-To: <408E64EB.6080204@chen-becker.org>
Derek Chen-Becker wrote:
> Kim Holviala wrote:
>
>> On Monday 26 April 2004 20:53, Derek Chen-Becker wrote:
>>
>>
>>> I'm upgrading my workstation from 2.4.22 to 2.6.5 and everything is
>>> working great except for /dev/input/mice: it doesn't appear to be
>>> producing anything, even if I cat it. I've checked and both dmesg and
>>> /proc/bus/input/devices show the mouse handler loaded and show the mouse
>>> as recognized.
>>
>>
>>
>> What do the system logs say? I suggest you build psmouse into a module
>> so that you can modprobe/rmmod it to test stuff without rebooting.
>>
OK, this is weird. I changed psmouse to be a module and now it works (I
also made gameport a module). Here's /proc/bus/input/devices from when
it *didn't* work:
I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel 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=103
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd
B: EV=120003
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: LED=7
And here's from when it *does* work:
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd
B: EV=120003
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: LED=7
I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel 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=103
The only difference I can see is the ordering. Does the mouse handler
have to be initialized after the keyboard handler?
Thanks,
Derek
--
+---------------------------------------------------------------+
| Derek Chen-Becker |
| derek@chen-becker.org |
| http://chen-becker.org |
| |
| PGP key available on request or from public key servers |
| ID: 21A7FB53 |
| Fngrprnt: 209A 77CA A4F9 E716 E20C 6348 B657 77EC 21A7 FB53 |
+---------------------------------------------------------------+
next prev parent reply other threads:[~2004-04-27 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 17:53 Troubleshooting PS/2 mouse in 2.6.5 Derek Chen-Becker
2004-04-27 5:49 ` Kim Holviala
2004-04-27 13:49 ` Derek Chen-Becker
2004-04-27 14:06 ` Derek Chen-Becker [this message]
2004-06-02 23:44 ` 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=408E68C9.5010102@chen-becker.org \
--to=derek@chen-becker.org \
--cc=kim@holviala.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox