Mouse movement is erratic under certain conditions (as activity in some windows, network activity, etc.) under XFree86 with a Voodoo Banshee video card (probably with a Voodoo 3 too). This bug did not appear in RedHat 6.0 with XFree86 3.3.5 (taken from RedHat 6.1).
I'm getting the same with an ATI Expert 98 & Voodoo 2 & Logitech MouseMan, normally when lots of IO is happening in the background (e.g. copying a 200 meg file from one partition to another). Under RH5.2 this type of operation didn't affect mouse movement. A look at the gnome cpu graph shows all the time is in 'nice'.
make sure you don't have option sw_cursor turned on in /etc/X11/XF86Config. Alternatively, try out XFree86 3.3.6 from our rawhide tree and see if it fixes your problem. We can't duplicate the problem here.
I am using a Quantum Raven 3D PCI card that runs with the latest Banshee drivers under Windows 98/direct X7.0 (dual boot machine). Redhat recognises it as a Banshee and all the install goes great except that whenever I move the mouse toward a button e.g. the "Add Comment" on this form the mouse pointer dissapears and re-appears at a random location on the screen. This happens during install as well as in both Gnome and KDE (at all res's). I just did a Vanilla install from the RH6.1 CD and have so far applied no patches. My mouse is a Rockwell PS/2 (Ms Wheel Mouse clone). Is this the same problem as outlined by keith.uk??
*** Bug 9667 has been marked as a duplicate of this bug. ***
Hello, This bugged me beyond belief. I tired a bunch of PS/2 mice I had laying around and they all exhibitted the same behavior. I found the following post on usenet. It turned out to be a problem with the bios of my MB. Three people have said this fixed the problem. I also am very happy to say it fixed me. BTW, this affected the shipping BIOS on a ABIT KA7/KA7-100 MB. http://x55.deja.com/viewthread.xp?AN=628679020&search=thread&svcclass=dnserver&ST=PS&CONTEXT=961986966.1466957927&HIT_CONTEXT=961986966.1466957927&HIT_NUM=4&recnum=%3c8gua3t$3fa$1@news.flashnet.it%3e%231/1&group=alt.comp.mainboards.abit&frpage=getdoc.xp&back=clarinet
thank you very much for finding the solution to this problem.