RE: [suse-amd64] Touchpad Issues in 9.3
-----Original Message----- From: Andi Kleen [mailto:ak@suse.de] Sent: Saturday, June 11, 2005 6:28 AM To: Black, Alain Cc: Barry Premeaux; suse-amd64@suse.com Subject: Re: [suse-amd64] Touchpad Issues in 9.3 On Fri, Jun 10, 2005 at 09:03:35AM -0700, Black, Alain wrote:
I have a similar issue with my desktop machine running SuSE 9.3 32bit that's hooked up to a KVM. When I switch back to the SuSE desktop the mouse goes haywire (large movements across the screen and random mouse clicks when I do not click the mouse buttons). The PC is a Dell Optiplex GX270.
Then I get "lost synchronization, throwing 3 bytes away", sometimes it's 2 bytes and other times 1 byte. I never see the driver resynched message though.
My workaround (part of which will not work for a touch pad) is to move the mouse about a quarter of an inch, which throws the cursor all over the screen, and then let it sit for a couple of seconds. When that doesn't work, I pick the mouse up until it can't read a surface below it and put it back down.
Boot with psmouse.proto=bare. That fixes all problems, but unfortunately also disables the scrollwheel :/ -Andi -- Andi, Thanks, that option works for me. Just a note: I do not have this problem when attached to KVM's from Avocent, only with the less robust SoHo model from Belkin that I'm using at my desk. -Alain
Just a note: I do not have this problem when attached to KVM's from Avocent, only with the less robust SoHo model from Belkin that I'm using at my desk.
Yes. The problem is that there are different extended protocols for the scrollwheels and other extensions and the older KVMs don't deal with it properly The strange effects you see is because the driver becomes desynchronized with the packets from the mouse. The psmouse.proto=bare forces the mouse to use the simplest two byte protocol. -Andi
participants (2)
-
Andi Kleen
-
Black, Alain