Re: ps/2 mouse problem with KVM switch

From: Vojtech Pavlik (vojtech_at_suse.cz)
Date: 02/13/04

  • Next message: Ville Herva: "2.4: hung spamassassin processes on reiserfs+LVM"
    Date:	Fri, 13 Feb 2004 09:12:31 +0100
    To: Robert White <rwhite@casabyte.com>
    
    

    On Thu, Feb 12, 2004 at 02:29:24PM -0800, Robert White wrote:

    > Less than optimal, yes, but technologically sound. Since there is no "soft
    > reset" behavior provided by the PS/2 standard, let alone any way for the KVM
    > switch to signal the driver that such logic needs to be invoked in software,
    > the real truth of the issue is that this is a limitation inherent in the
    > design of the PS/2 interface and any solution other than
    > greatest-common-denominator will be unstable.
    >
    > It would have been better if the PS/2 (and keyboard) interface were designed
    > with hot-plugability in mind and the KVM switch did nothing but detach the
    > devices so that a "switch to" even caused the software to rediscover the
    > device and reset the parameters. The thing was that part of the core
    > purpose of the KVM today was designed to prevent the old "keyboard not
    > found, press F1 to continue booting" nonsense... Thank You Pane/Webber. 8-)
    >
    > Rob.
    >

    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.

    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.

    -- 
    Vojtech Pavlik
    SuSE Labs, SuSE CR
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Ville Herva: "2.4: hung spamassassin processes on reiserfs+LVM"

    Relevant Pages

    • Re: configure PS2 mouse through KVM Switch to serial port
      ... >and PS2 type mice as the switch is thrown from one PC to another. ... or do you have problems with mice across OS's? ... I tried re-boot of the computer with Linux box chosen on KVM switch. ... The PS/2 mouse has never worked through the KVM ...
      (alt.os.linux)
    • Re: Mac and PC to same monitor
      ... an ADB to VGA adapter) you can use almost any regular KVM. ... The belkin ones work quite well, but with the way that the mac ... power switch set to sleep the machine, and then press it once you'd ... I've been very happy with PS/2 KVM's and PS/2 to ADB and USB converters. ...
      (uk.comp.sys.mac)
    • Re: how do I push a button remotely (second post)
      ... have access to google to post, and google says it's 'unable to retreive the message'. ... The device is a KVM Switch ... The KVM switch is connected to a KVM Extender which boosts 30 meters, ... Should I use 30 meters of shielded cable or just normal wire? ...
      (sci.electronics.basics)
    • Re: how do I push a button remotely (second post)
      ... have access to google to post, and google says it's 'unable to retreive the message'. ... The device is a KVM Switch ... The KVM switch is connected to a KVM Extender which boosts 30 meters, ... Should I use 30 meters of shielded cable or just normal wire? ...
      (sci.electronics.basics)
    • Re: Does SP2 fiddle with keyboard/mouse voltages?
      ... > I have two Windows XP Pro computers that share a monitor, ... > These two computers had been running through the KVM switch for a ... But ever since one of the PCs had SP2 ... > As soon as I switch on PC#2, however, everything works fine. ...
      (microsoft.public.windowsxp.hardware)