public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KVM problems - anyone know _why_ it happens?
Date: Sun, 22 Jan 2012 17:47:51 +0000	[thread overview]
Message-ID: <B2159F2D-D7BE-40B3-80AB-7121A31FCC3A@stellar.eclipse.co.uk> (raw)
In-Reply-To: <CAK2H+eceBcE=v_KHuBp1vfGdRXn98_B1q8fZ+FtZE6dxc5MqkQ@mail.gmail.com>


On 22 January 2012, at 15:54, Mark Knecht wrote:
> ...
> Basically, I looked around in Google for anyone that had real info
> about why this problem occurs, couldn't find any that made sense, and
> am wondering how to choose a KVM that's going to work out of the box
> short of asking for model numbers, etc.

For all you've written, I'm afraid the best answer you're likely to get it "buy a KVM you can return" (or buy secondhand at a price you can resell without loss). 

Video resolutions / refresh rates / timing / &c is a bit of a black art. What the heck is a modeline? 

The manufacturer of a KVM isn't going to be able to test it with all the 10,000 monitors available on the market today - not even 1% of them. They're happy if it works 99% of the time, and if you complain to them they'll say "oh, it must be a bug with that monitor" and maybe, eventually, give you a refund for the sake of a peaceful life. 

There are probably a handful of different KVM chips that are made by big manufacturers in Taiwan, and then sold by the 10,000 to other manufacturers, this time manufacturers of actual KVM units. These second tier manufacturers probably all wrap the KVM integrated circuits up in slightly different ways, using slightly different resistors and capacitors to interface with input and output. 

So in terms of your specific questions, I'm not able to answer very helpfully. I think you could waste a lot of time trying to get these answers, whereas you could swap in a specific model and try it in a matter of minutes - and that way you'd know for sure.

Stroller.




  parent reply	other threads:[~2012-01-22 17:48 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
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 [this message]
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=B2159F2D-D7BE-40B3-80AB-7121A31FCC3A@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --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