public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Video card with two ports.
Date: Fri, 08 Nov 2013 12:55:43 -0600	[thread overview]
Message-ID: <527D33AF.80801@gmail.com> (raw)
In-Reply-To: <CA+ZgY1GCZ4YaXXVbfpzj1_7aaSJgcgN30k3tPM1E7sj8TENa_g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]

Daniel Frey wrote:
>
>
> On Nov 7, 2013 9:47 PM, "Dale" <rdalek1967@gmail.com
> <mailto:rdalek1967@gmail.com>> wrote:
>
> > Mine isn't skewed to one side, it's just a fraction to large.  It
> seems to be cut off by a few pixels all the way around.  Watching a
> movie tho, no problem.  Using it for a puter monitor tho, slight
> issue.  To give a bit of a idea, about 1/3 of the clock on the little
> panel thing at the bottom is cut off.  The little K menu thing is
> missing about the same on both bottom and left side.  You can see it
> but it just isn't all there like on my puter monitor.
> >
> > Since I don't really plan to use it for a monitor, it's no biggie. 
> I figure it could be that they just put to much plastic around the
> display itself.  Sort of covered up to much of the screen.
> >
>
> Dale,
>
> I am assuming this is a TV? All TVs apply overscan to inputs and that
> is what you are seeing.
>
> Most TVs made in the last five years have a way to turn that off, but
> it varies. On my Samsung, I have to use the dvi/HDMI input and set the
> input label to dvi/PC and overscan is then turned off for that input.
> It is buried in the menu options but it doesn't explain what it does.
>
> I have several mythtv frontends and found this solution about four
> years ago when I replaced my living room TV.
>
> Dan
>


And a quick google tells how to do this on my TV.  I'll have to test
later tho.  I unhooked the cable the other day.  I need to run it under
the floor so I don't trip over that monster. 

Thanks for the info tho.  That helped. 

Dale

:-)  :-)  

-- 
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!


[-- Attachment #2: Type: text/html, Size: 2617 bytes --]

  reply	other threads:[~2013-11-08 18:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  2:32 [gentoo-user] Video card with two ports Dale
2013-10-30  3:20 ` Walter Dnes
2013-10-30  3:49   ` Dale
2013-10-30 16:03   ` [gentoo-user] " Grant Edwards
2013-10-30 16:20     ` Neil Bothwick
2013-10-30 17:52       ` Dale
2013-10-31  1:14         ` Walter Dnes
2013-10-31  2:07           ` Bruce Hill
2013-10-31  7:13             ` Walter Dnes
2013-10-31 12:31               ` Bruce Hill
2013-10-31 21:35                 ` Walter Dnes
2013-10-31  2:12           ` Dale
2013-11-02  0:43             ` Dale
2013-11-02  7:52               ` J. Roeleveld
2013-11-02 10:33                 ` Dale
2013-11-02 11:45                   ` Neil Bothwick
2013-11-03 22:39                   ` Frank Steinmetzger
2013-11-08  5:47                     ` Dale
2013-11-08 16:27                       ` Daniel Frey
2013-11-08 18:55                         ` Dale [this message]
2013-11-08 19:25                         ` Grant Edwards
2013-11-02  8:55               ` Yohan Pereira
2013-11-02 11:55               ` Frank Steinmetzger
2013-10-31 12:40 ` [gentoo-user] " Alan McKinnon
2013-10-30 13:28   ` Frank Steinmetzger

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=527D33AF.80801@gmail.com \
    --to=rdalek1967@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