Re: [OFFTOPIC] Busmice: MouseSystems Ps/2 Mouse Skips

Mark Orr (markorr@intersurf.com)
Sat, 21 Feb 1998 03:46:51 -0600 (CST)


On 02-Feb-98 nuke@bayside.net wrote:
> On Tue, 17 Feb 1998, Alessandro Rubini wrote:
>
>>
>> > movement is skippy and erratic. The mouse likes to jump to the lower left
>> > corner of the screen (it does this in both GPM and X).
>>
>> This is is usually due to incorrect decoding of the mouse data stream
>>
>> Please try to run mouse-test, from the gpm distribution (I bet it's
>> already installed in your system). If you can't find your way
>> through protocols please run "od -t x1 /dev/mouse" and send me
>> the output while you move the mouse and/or press buttons.

I know this response is kind of belated (I just noticed the message), and
you may have already found the solution by now...but I thought I might
chime in with what I've found out.

In early January, I bought a Mouse System 3-button PC Point Pro mouse
to replace my broken Microsoft 2-button PS/2 mouse.

This mouse was described on the box as BOTH a serial and PS/2 compatible
mouse -- the cable terminates as a 9-pin D-type serial connector, but it
has an adapter which turns it into a PS/2 mouse.

I tried it as a PS/2 mouse (using the same psaux.o/misc.o driver that
the MS mouse used). I got the exact same reaction as treisk was
describing -- in X11, it alwayed jumped to the lower left corner.

I got it working using gpm as a repeater, and the /dev/gpmdata trick,
BUT I WASNT CONTENT WITH THAT SOLUTION.

I tried it as a serial mouse, and it worked okay -- except that it only
recognized 2 of the 3 buttons, and was WAAAY to sensitive.

Then, I looked at a large # of messages on Dejanews looking for others
who had a similar problem -- one pointed me to a Tech Support web page
at Mouse Systems -- it related directly to Linux (imagine that). I
don't have the URL handy, but the gist of it was that Mouse Systems
ps2 mice need initialization.

if you look in /usr/src/linux/drivers/char/psaux.c, after the big
comment at the top of the file, there's a #define INITIALIZE_DEVICE
that's commented out. Get rid of the /* and */ and it should work.

It DID for me -- *BUT* it's still way too sensitive.

I looked down at the section that's enabled by that #define .. and
fiddled with the commands it's sending to the mouse. The relevant
one seems to contain the string "SCALE21" .. change that to "SCALE11"
(it's surrounded by other text) and that fixes it right up. It's
still a tiny bit more sensitive than my old MS PS/2 mouse -- but I
can live with it.

(Info: I'm running the latest 2.1 kernels -- not 100% sure how the
2.0's psaux.c code looks)

Also, for anyone thinking of getting a mouse like this -- it has a
really short cable...like 4 feet long. Luckily I had a PS/2 mouse
cord extender. Now it's like 9 feet long - oh boy!

Otherwise, I'm pretty happy with the performance of the mouse. Well,
initally, I found that button 1 double-clicked too easily -- but it
seems to have calmed down.

It would be nice if psaux.o had module/kernel command line parameters
that allowed you to select initialization/samples/resolution/sensitivity/
scaling at load time (i.e. put them in /etc/conf.modules, just like
the new modular sound drivers' parameters). Then I wouldn't have to
edit the kernel source every time just to get my mouse working.

--
Mark Orr
markorr@intersurf.com

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu