PS2 Mouse Going Crazy!

[curious101]

I just installed a new ps2 mouse because my old one wasn't functioning properly anymore. The old one was a wheel mouse and it was the one detected by Fedora Core during installation. The new one I replaced wasn't a wheel mouse. And now I can't get my mouse to work. Whenever I am in the logon screen, my mouse doesn't function properly anymore. Whenever I moved the mouse pointer, it suddenly disappears and for some reason it just keeps on clicking even though I did not press the mouse clicks. The same is true when I am in GNOME.

Please help me how to go about this problem. :confused:

[Harryc]

Are you running FC1 or FC2 and what is the exact model of mouse?

[Algernon]

I just installed a new ps2 mouse because my old one wasn't functioning properly anymore. The old one was a wheel mouse and it was the one detected by Fedora Core during installation. The new one I replaced wasn't a wheel mouse. And now I can't get my mouse to work. Whenever I am in the logon screen, my mouse doesn't function properly anymore. Whenever I moved the mouse pointer, it suddenly disappears and for some reason it just keeps on clicking even though I did not press the mouse clicks. The same is true when I am in GNOME.

Please help me how to go about this problem. :confused:

I have the same problem.
SW = FC2 with ANY kernel after the default installation.
HW = Compaq EN-6350 SFF, 160GB, 256MB, embedded everything (video, sound which sort of works, net...) & 4to1 KVM. Logitech wireless mouse with PS/2 or USB attachment options.

What I have found is that if I boot without monitor, mouse or keyboard (remeber the KVM) somehow the system works but if I switch the KVM to show the boot (even for a little while) mouse will not work. No amount of "mouseconfig" or "system-config-mouse" will help.

X.conf (or xorg.conf) has "imps/2" but I have tried "ps/2" also, didn't help.
Also the wheel in mouse acted funny with earlier kernels. Now it works ok if I remember to boot in the correct KVM position.

-M

[Harryc]

Now it works ok if I remember to boot in the correct KVM position. What happens if you boot up with the mouse connected directly to the computer? (no KVM)

[Algernon]

What happens if you boot up with the mouse connected directly to the computer? (no KVM)

I had a power outage this morning so decided to make a trial.

And as was to be expected mouse works OK if plugged directly to PC.

So the trouble seems to be related to my KVM, which has never had any problems.
KVM is a Linksys ProConnect model SVIEW04.

I tried to boot again with KVM "tuned" to show the boot and mouse goes nuts again...I'm now using the PC after a another reboot.

Now the question is, what changed right after kernel#2.6.5-1.358 that would explain this?
All kernels after the initial have similar problems. Either the wheel would act funny or now in the later ones the movements are uncontrollable.

-M

[Harryc]

Don't see any workarounds in a quick search...this guy replaced his KVM.

http://www.redhat.com/archives/fedora-list/2004-June/msg00251.html


and a few more ideas...

"I have had this happen before.

Power down both machines. Then power down the switch
-- if possible. Unplug both computers and switch so
that no juice whatsoever is going to the switch. Plug
everything back in and power on.

Your mileage may vary, but this worked for me."

"I have this problem every once in a while, and I've found that switching
to a text console (CTRL-ALT-F1) and back (ALT-F7) does the trick."

[Algernon]

Don't see any workarounds in a quick search...this guy replaced his KVM.
http://www.redhat.com/archives/fedora-list/2004-June/msg00251.html

And that why I have the Linksys. There has been no problems so far.



and a few more ideas...

"I have had this happen before.

Power down both machines. Then power down the switch
-- if possible. Unplug both computers and switch so
that no juice whatsoever is going to the switch. Plug
everything back in and power on.

Your mileage may vary, but this worked for me."

"I have this problem every once in a while, and I've found that switching
to a text console (CTRL-ALT-F1) and back (ALT-F7) does the trick."

I will try the last trick but since I have tried to config the mouse from F1 (with root access) and booted the X with init 3, init 5 without luck I assume that will not solve anything.

Still there is the issue of using the default kernel. This will solve the problem every time, it is still installed, I would just like to use the newer kernels and have those fully functional.

-M

[tim@npagroup.co]

Moving my mouse (Microsoft optiocal wheel mouse USB via a PS/2 adapter) during boot up of a clean FC2 install on my toshiba laptop causes the mouse to go haywire - not moving the mouse until I get a login screen causes the mouse to work fine - if you want to look at the detailed startup text, using the keyboard shortcut leaves the mouse unaffected.

Hope this helps

--Tim

[Bob K]

I have been having the same problem with my KVM, and was over at the Gentoo site and did a search on KVM and somebody has a patch for the psmouse driver that is supposed to fix this problem. I read the patch code for the problem and what is happing is the driver loses sync with the mouse and starts getting error packets. the solution that was used was after 3 error packets the driver would reset and re sync. I didn't load the driver due to the fact I am running an older version but when I get the time I will modify my psmouse driver.

[bitsofme]

I followed the link to the gentoo site and got a patch file.

http://bugzilla.kernel.org/attachment.cgi?id=3244&action=view

But what do I do with that? It looks like a c program.
Am I being completely Blonde ???

PS life would not be so entertaining without Blondes !!

[Bob K]

I just figured I would modify my psmouse and add the error checking and re sync code and recompile and rebuild my core.

I have noticed that there has been alot of work in psmouse in 2.4 and this patch was for 2.6.

I am planning to upgrade hardware this year and don't plan going to 2.6 until then so by then this will be incorperated in the core release by then.