Hi Vojtech,
I've just bought a new PS/2 mouse, and it works fine with 2.5, but in
2.4 it doesn't work properly if I move the mouse slowly.
I've tried 2.4.20-pre5, 2.4.20, and 2.4.19, and get the same
problems:
In X, the mouse works fine as long as it's moved quickly, but trying
to move it 1 pixel, for example, is almost impossible.
>From the console, cat /dev/psaux displays nothing, if I move the mouse
slowly, no matter how far it's moved. Moving it quicky displays
characters as expected.
It's almost as if individual packets of data are being lost, but only
the first packet of a constant stream of data. Maybe the mouse is
sending an extra syncronisation byte or something, which is confusing
things?
Is there a way to dump the raw data from the port like there is in
2.5?
John.
> I've just bought a new PS/2 mouse, and it works fine with 2.5, but in
> 2.4 it doesn't work properly if I move the mouse slowly.
>
> I've tried 2.4.20-pre5, 2.4.20, and 2.4.19, and get the same
> problems:
>
> In X, the mouse works fine as long as it's moved quickly, but trying
> to move it 1 pixel, for example, is almost impossible.
>
> From the console, cat /dev/psaux displays nothing, if I move the mouse
> slowly, no matter how far it's moved. Moving it quicky displays
> characters as expected.
OK, this was my fault :-)
In 2.5.X, psmouse_initialize is actually setting the resolution, etc,
whereas 2.4.X is just using the mouse's power on default. Adding:
Option "Resolution" "200"
to my X config file, seems to initialise the mouse in a similar way,
and it works fine.
Never noticed this with any other PS/2 mouse, though. Maybe this one
just has an unusual power-on default setting?
John.