public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marko Macek <Marko.Macek@gmx.net>
To: Robert White <rwhite@casabyte.com>
Cc: vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: ps/2 mouse problem with KVM switch
Date: Fri, 13 Feb 2004 18:55:43 +0100	[thread overview]
Message-ID: <402D0F9F.70302@gmx.net> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA2ZSI4XW+fk25FhAf9BqjtMKAAAAQAAAAIH4lUMJJWUqlFPWIv65Y6gEAAAAA@casabyte.com>

Robert White wrote:
> Note that the KVM Switch (typically) implements an intermediate "device" for
> the mouse so that when you are switched away to the other machine, the first
> machine is still "talking to something".
> 
> This has the less-than-desireable effect of causing the mouse device "inside
> the switch" to act as a largest-common-denominator.  Consequently many of
> the special features and peculiarities of your real device may not be
> accessible to your computer.

Well, under 2.4 they all work, probably because the settings for both 
systems are the same.

> A particular, and bette-documented, example of this can probably be found by
> trying to hook up a "new-fangled" keyboard (with the media control key
> cluster across the top and such) to your windows box.  When the keyboard
> drivers cannot find the special buttons and you call the KVM switch vendor
> they will promptly tell you about how all those hot extra buttons are not
> supported with their product, have a nice day, good-bye... 8-)

I have a Microsoft internet keyboard and the keys all work. I guess MS 
is big enough to be supported. (not that I use any of the keys). I 
haven't tried others.

> The same things go four your mouse, but are not as well documented and
> accessible to the KFM help desk weasels.
> 
> You should find that if you select a "much more generic" mouse configuration
> "everything works fine".

Yes, "bare" works. But I want my wheel to work.

> Some newer windows drivers "look past" the switch and activate the mouse
> features anyway.
> 
> Regardless, if your "other" computer is initializing the mouse through
> voodoo and dark magic to increase the reporting (baud?) rate and such, when
> you toggle to the Linux box you will see all sorts of unhappiness.  The
> inverse is also true, if the windows driver is expecting
> fast-and-feature-full and the side trip to Linux has set things back to
> mundane, the return to Windows will be "exciting"

I can see this would be a problem. I just haven't figured out the right 
rate, ... settings yet.
> 
> (My optimal configuration that saves heartache)
> 
> 2-Port plasma flat panel
>   DVI port connected to my primary use machine
>   VGA port connected to my KVM

I plan to to that when I upgrade my monitor. My current one doesn't have 
2 inputs. I'd still prefer one mouse and keyboard.


Regards,
Mark



      parent reply	other threads:[~2004-02-13 17:54 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
2004-02-13 17:55   ` Marko Macek [this message]

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=402D0F9F.70302@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox