Bug 130990 - mouse loses control through d-link kvm switch
Summary: mouse loses control through d-link kvm switch
Status: RESOLVED WORKSFORME
: 132045 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Vojtech Pavlik
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-27 12:12 UTC by Daniel Secareanu
Modified: 2006-01-11 11:05 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Secareanu 2005-10-27 12:12:44 UTC
I have a 4 port KVM switch that I use with a few servers (1 monitor, 1 keyb & 1 mouse to manage all machines). I installed 10.0 final version (not oss) and whenever I switch the KVM port to another computer connected to it and then return to the suse computer and try to move the mouse slowly, the mouse cursor starts moving erraticaly on the screen as if someone keeps all buttons pressed and moves it around madly (it does right clicks, left clicks, scrolls and so on, whenever the cursor is on a relevat screen part where such actions can be done). Restarting the X server with ctrl+alt+backsp doesn't help. Rebooting and keeping the KVM switch only to the suse computer shows no problems of this issue...

I had something related a while ago while trying to install suse linux on a machine connected through kvm switch, it never detected the video card properly and only wanted to install in text mode...

Daniel
Comment 2 Matthias Hopf 2005-10-27 13:07:46 UTC
If restarting the X server doesn't help, this is a kernel mouse driver issue.

Even if the monitor is not detected, installation should work graphically. In your case it seems that the bios did not have a framebuffer mode (maybe a i815?). For i815 that has been fixed. Video card detection has nothing to do with kvm switches.
Comment 3 Egbert Eich 2005-10-27 13:55:09 UTC
Well, I used to have such problems with my KVM switch, too. I didn't experience them lately, I don't know why. When the problem occurred not even my protocol detection code could do anything useful with the data delivered from the mouse.
Why the problem occured in the first place was impossible to find out.
I'm not sure if there is anything at all we can do. Neither im kernel nor in X.
Comment 4 Stefan Dirsch 2005-10-27 14:39:04 UTC
I agree. I therefore close this one as WONTFIX.
Comment 5 chuck frain 2005-11-09 23:31:32 UTC
I have had this problem with a Belkin switch as well. 

From the research I've done, I've found that it does appear to be a kernel level issue. From posts I've found RH appears to have fixed the issue at some point, though I've not verified that. 

Also, Suse 9.3 (installed and live DVD) both do not have this problem beyond the first mouse movement upon swtiching back. The resync works there. I cannot find any kernel compile options that are different and my programing skills do not allow me to check the code. 
Comment 6 chuck frain 2005-11-09 23:35:14 UTC
Sorry, forgot to click on the reopen last time. 
Comment 7 Martin Lasarsch 2005-11-11 10:53:32 UTC
*** Bug 132045 has been marked as a duplicate of this bug. ***
Comment 9 Michael Gross 2005-11-11 16:29:07 UTC
I'm closing this. If someone is able to fix this, please reopen it.
Comment 11 Egbert Eich 2005-11-11 17:55:36 UTC
There are bzillions of different KVM switch models around and a lot of them are broken in one way or the other. Mine behaves well - so I cannot reproduce these problems. Good for me. Bad for the others who are not so lucky.
Comment 12 Egbert Eich 2005-11-24 12:14:49 UTC
If anyone could send me a KVM that makes trouble I could see if it's fixable.
Comment 13 chuck frain 2005-12-16 16:04:11 UTC
Something that I found that seems to work with the Belkin switches that I've tried this on. Passing the option 'psmouse.resetafter=3' seems to fix the issue for me. The number looks for a particular ammount of errors from the mouse and resets the protocol after that many errors are found. The scrollwheel continues to work as well. 

I don't have a D-Link switchbox to test this on, but I would be interested if it works. Also if anyone knows of a reason not to use this as a solution that would be great to know as well. 
Comment 15 Stefan Dirsch 2006-01-02 06:22:42 UTC
'psmouse.resetafter=3' --> reassiging to Vojtech :-)
Comment 16 Vojtech Pavlik 2006-01-06 16:18:49 UTC
This option was added exactly for working around problematic KVM's. It's harmless
and can even be set to a lower value (even 1 usually works without adverse effects, and synchronizes faster). If it solves your problem, I think we can
close this bug.
Comment 17 Vojtech Pavlik 2006-01-11 11:05:33 UTC
Closing, a workaroun for problematic KVM's exists.