public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "G.Wolfe Woodbury" <redwolfe@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KVM problems - anyone know _why_ it happens?
Date: Sun, 22 Jan 2012 13:07:09 -0500	[thread overview]
Message-ID: <4F1C504D.6010105@gmail.com> (raw)
In-Reply-To: <CAK2H+efWEd8ti+wv_q5GUZoknQL=1EtVi15Ac09RLGn7dX2j8w@mail.gmail.com>

On 01/22/2012 12:42 PM, Mark Knecht wrote:
> I played a bit with get-edid | parse-edid. Logically that stuff even 
> working says the VGA monitor cable is bidirectional. I started 
> wondering if the KVM messes up the data coming back, or what else 
> might be going on. Thanks for the ideas, Mark 
Many of the cheap KVM models do, indeed, mess up the EDID data coming 
from the monitor.  I suspect that this is from old design specs that 
have too much pull-up/pull-down on the EDID lead since the boxen haven 
been re-engineered for newer, higher resolution and higher speed monitors.

I have had problems specifically with the BELKIN KVMs.

It may also be that the video drivers for Linux are just enough 
different (necessarily) from the MSFT drivers to not reliably sense the 
EDID return signals.

I did as others suggested and tried several until I found one that 
worked.  Sometimes a slightly different model/serial/part no KVM from 
the same manufacturer would/wouldn't work.

-- 
G.Wolfe Woodbury
redwolfe@gmail.com




  reply	other threads:[~2012-01-22 18:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-22 15:54 [gentoo-user] KVM problems - anyone know _why_ it happens? Mark Knecht
2012-01-22 16:06 ` Michael Mol
2012-01-22 17:42   ` Mark Knecht
2012-01-22 18:07     ` G.Wolfe Woodbury [this message]
2012-01-22 18:22       ` Mark Knecht
2012-01-22 18:58       ` Michael Mol
2012-01-22 19:30         ` Mark Knecht
2012-01-22 20:07           ` Michael Mol
2012-01-22 20:18             ` Mark Knecht
2012-01-22 20:52               ` Alan McKinnon
2012-01-22 21:21                 ` Mark Knecht
2012-01-22 17:47 ` Stroller
2012-01-22 18:52   ` Michael Mol

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=4F1C504D.6010105@gmail.com \
    --to=redwolfe@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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