Re: Troubleshooting PS/2 mouse in 2.6.5

Vojtech Pavlik
2004-06-02T23:45:28Z

On Tue, Apr 27, 2004 at 08:06:01AM -0600, Derek Chen-Becker wrote:
> 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?

No, but on many machines it needs to be initalized after USB.

--