Troubleshooting PS/2 mouse in 2.6.5
Hi,
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. I've tried disabling ACPI because I saw it mentioned when I googled, but that didn't help. I've also tried loading the event handler module and I get nothing there either. I have another PC with 2.6.5 working fine with the same mouse. Both are hooked up to the same KVM, would that have anything to do with it? Does anyone know where I could look to get more detail on what's happening?
Thanks,
Derek
Signature · 9 lines
+---------------------------------------------------------------+ | Derek Chen-Becker | | [email protected] | | 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 | +---------------------------------------------------------------+
Quoted 5 lines · Derek Chen-Becker
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/devicesshow 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.
Kim
Quoted 12 lines · Kim Holviala
Quoted 5 lines · Derek Chen-Becker
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/devicesshow 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.
They appeared to indicate that it had loaded. I'll save the contents of dmesg and /proc/bus/input/devices and post it.
Thanks,
Derek
Signature · 9 lines
+---------------------------------------------------------------+ | Derek Chen-Becker | | [email protected] | | 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 | +---------------------------------------------------------------+
Quoted 13 lines · Derek Chen-Becker
Quoted 11 lines · Kim Holviala
Quoted 5 lines · Derek Chen-Becker
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/devicesshow the mouse handler loaded and show the mouse as recognized.
Quoted 2 lines
Quoted 2 lines
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
Signature · 9 lines
+---------------------------------------------------------------+ | Derek Chen-Becker | | [email protected] | | 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 | +---------------------------------------------------------------+
Quoted 39 lines · Derek Chen-Becker
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/devicesfrom 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=103I: 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 3802078f840d001f2ffffdfffefffff ffffffff fffffffe
B: LED=7And 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 3802078f840d001f2ffffdfffefffff ffffffff fffffffe
B: LED=7I: 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
Quoted 2 lines
The only difference I can see is the ordering. Does the mouse handler have to be initialized after the keyboard handler?
No, but on many machines it needs to be initalized after USB.