From: Marko Macek <Marko.Macek@gmx.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Robert White <rwhite@casabyte.com>, linux-kernel@vger.kernel.org
Subject: Re: ps/2 mouse problem with KVM switch
Date: Fri, 13 Feb 2004 18:41:14 +0100 [thread overview]
Message-ID: <402D0C3A.6070909@gmx.net> (raw)
In-Reply-To: <20040213081231.GA247@ucw.cz>
Vojtech Pavlik wrote:
> Sadly enough, there is a soft reset command in the PS/2 protocol, and
> the PS/2 interface is designed for hotplug, and because of that Linux
> 2.6 can easily handle hotplugging of both PS/2 keyboards and mice,
> including type detection, etc, BUT the KVM switches don't use that,
> because Windows historically doesn't support unplugging a PS/2 mouse.
If the mouse gets into confusing state, I can "replug" it into the KVM
switch (while in Windows) and it works fine after that. I have also
noticed that when Windows is doing "resume" I must not switch away
before it is if I want my mouse to work (otherwise I will need to replug).
For Linux, I also need to switch from X to console and back when the
mouse is "confused".
With 2.4 I repeat the the 2 steps described above my mouse works (incl
wheel) on both machines after that.
> The most ugly part of the KVM switch in this play is that while the KVM
> switch usually implements a virtual mouse for each of the machines, it
> lets them all talk to the real one, and if they have different ideas
> about what mode the mouse should be set to, well, then there goes the
> road to madness.
I guess I need to figure out how to force both machines to initialize
the mouse in the same way then...
Regards,
Mark
next prev parent reply other threads:[~2004-02-13 17:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 9:34 ps/2 mouse problem with KVM switch Marko Macek
2004-02-12 22:29 ` Robert White
2004-02-13 8:12 ` Vojtech Pavlik
2004-02-13 17:41 ` Marko Macek [this message]
2004-02-13 17:55 ` Marko Macek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=402D0C3A.6070909@gmx.net \
--to=marko.macek@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhite@casabyte.com \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.