RE: [suse-amd64] Touchpad Issues in 9.3
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. It's a 3 button, wheel PS/2 optical mouse from Key Tronics hooked up to a Belkin OmniView SoHo series KVM. -Alain. -----Original Message----- From: Barry Premeaux [mailto:bpremeaux@gmail.com] Sent: Thursday, June 09, 2005 10:52 AM To: suse-amd64@suse.com Subject: [suse-amd64] Touchpad Issues in 9.3 I have an Acer Aspire 1522LMi. I have been trying various 32/64 bit installs with 9.2/9.3 as I learn what works and what doesn't. I've settled on a 9.3 32 bit install which will let me set up the internal winmodem and wifi interfaces. One issue has been the Touchpad mouse under 9.3. I get a hesitation that sometimes requires that I wait a moment before trying to move the pointer. The message log file shows the following: linux kernel: psmouse.c: TouchPad at isa0060/serio4/input 0 lost sync at byte 1 linux kernel: psmouxe.c: TouchPad at isa0060/serio4/input 0 lost sync at byte 1 linux kernel: psmouse.c: TouchPad at isa0060/serio4/input 0 lost sync at byte 4 linux kernel: psmouse.c: TouchPad at isa0060/serio4/input 0 - driver resynched Occasionally you will also see: linux kernel: psmouse.c: issuing reconnect request I went into SAX2 and changed from the Synaptics Touchpad setup to Explorer/PS2 and rebooted. Still got the same messages. I also tried turning off the wheelmouse and setting it to 3 button emulation, but this didn't make a difference either. Does anyone have ideas on this one? Barry -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
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.
It's a 3 button, wheel PS/2 optical mouse from Key Tronics hooked up to a Belkin OmniView SoHo series KVM.
The Touchpad worked fine in 9.2, so I found it strange to have this problem with 9.3. My work around was to pick up a Logitech USB mouse. It works fine. So, for extended periods at the keyboard, it looks like it will be the external mouse. Barry
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
On Sat, Jun 11, 2005 at 05:06:36PM -0700, Barry Premeaux wrote:
Boot with psmouse.proto=bare. That fixes all problems, but unfortunately also disables the scrollwheel :/
Would I put that in Boot.local or one of the rc files?
Into /boot/grub/menu.lst at the end of the "kernel" line of the kernel you are booting. [yes it is painful to admit but Linux 2.6 still requires a reboot to change the mouse settings :/] -Andi
On 6/11/05, Andi Kleen
On Sat, Jun 11, 2005 at 05:06:36PM -0700, Barry Premeaux wrote:
Boot with psmouse.proto=bare. That fixes all problems, but unfortunately also disables the scrollwheel :/
Would I put that in Boot.local or one of the rc files?
Into /boot/grub/menu.lst at the end of the "kernel" line of the kernel you are booting.
[yes it is painful to admit but Linux 2.6 still requires a reboot to change the mouse settings :/]
I tried the end of the line and several locations within the line and the boot process stops at the log in prompt with X failing to start. With it out, the boot process is normal with X starting up as it should. That line currently has: kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x317 selinux=0 splash=silent resume=/dev/hda2 showopts Where would you put it? Barry
That line currently has:
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x317 selinux=0 splash=silent resume=/dev/hda2 showopts
Where would you put it?
Exactly there. However, make sure you don't accidentally insert any line breaks or things go to custard. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
Barry Premeaux wrote:
That line currently has:
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x317 selinux=0 splash=silent resume=/dev/hda2 showopts
Where would you put it?
Unless you want to see it at every boot, between resume=/dev/hda2 and showopts. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Where would you put it?
Unless you want to see it at every boot, between resume=/dev/hda2 and showopts.
I gave that another try, making sure I didn't add anything but a space between parameters.. I got the same results. Although I see init 5 started during the boot up, and it drops me to the CLI. Startx fails and I end up deleting it from the line and then am able to complete a full reboot. As I said, I have tried stuffing it in alternate locations within the line and the result is the same. It simply does not like psmouse.proto=bare. Barry
On Sun, Jun 12, 2005 at 05:24:22PM +0200, Laurent GUERBY wrote:
On Sun, 2005-06-12 at 02:20 +0200, Andi Kleen wrote:
[yes it is painful to admit but Linux 2.6 still requires a reboot to change the mouse settings :/]
Out of curiosity, is there a plan to change this state of affair?
Yes. Eventually there should be sysfs variables for it. -Andi
participants (6)
-
Andi Kleen -
Barry Premeaux -
Black, Alain -
Joe Morris (NTM) -
Laurent GUERBY -
Volker Kuhlmann