public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KVM problems - anyone know _why_ it happens?
Date: Sun, 22 Jan 2012 11:30:36 -0800	[thread overview]
Message-ID: <CAK2H+eexsS8Ec5jyv+X3GLEyx0E_LMqoFz4sNXUGQTYu0et0cQ@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiCrj5yjT6atG1QRFMvVxsM8vqK0ZmdZPj-NHAesG6qhCQ@mail.gmail.com>

On Sun, Jan 22, 2012 at 10:58 AM, Michael Mol <mikemol@gmail.com> wrote:
> On Sun, Jan 22, 2012 at 1:07 PM, G.Wolfe Woodbury <redwolfe@gmail.com> wrote:
>> 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.
>
> Concur. It sounds like the EDID block isn't making it back or is
> somehow messed up. x11-misc/read-edid would help in investigating that
> kind of issue.
>

Yeah, I did that sort of stuff already. It didn't tell me anything
specific as best I could tell. However I haven't done it with the KVM
out. Maybe comparing the two responses would give some clues.

Also, thanks for the pointer to xvidtune. Interesting little app.
QUESTION: Do you know how to get the data for each monitor/video card
combo? So far I haven't figured out how to tell it Screen2. Seems to
only give me Screen0 as best I can tell.

I'm a bit nervous to just start trying things.

Cheers,
Mark



  reply	other threads:[~2012-01-22 19:32 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
2012-01-22 18:22       ` Mark Knecht
2012-01-22 18:58       ` Michael Mol
2012-01-22 19:30         ` Mark Knecht [this message]
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=CAK2H+eexsS8Ec5jyv+X3GLEyx0E_LMqoFz4sNXUGQTYu0et0cQ@mail.gmail.com \
    --to=markknecht@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