public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with xf86-video-ati & nvidia-drivers
Date: Mon, 18 Jul 2011 17:56:15 -0700	[thread overview]
Message-ID: <CAN0CFw1DsTC95uFUtrJ+1jDdDQ+1s9bjO-POC25wxR9026D4-A@mail.gmail.com> (raw)
In-Reply-To: <CAN0CFw1cMRKYLC97L7xHs_ZaEWHvLURa1R4yaRCU4EX-bri17Q@mail.gmail.com>

>>> But at some point the 1s and 0s must be converted to some sort of an
>>> analog signal if only right behind the diode.  A diode must be
>>> presented with a signal in some sort of analog form in order to
>>> illuminate, right?  Digital is just a figment of our imagination after
>>> all.
>>
>> The pixel is either on or off. There's no way to make half of the adjacent pixel on (and the other half of that pixel off).
>
> Well, couldn't the digital information for a particular pixel mean
> blue, and the D/A mechanism attempts to create an analog signal that
> the diode would interpret as blue, but the D/A converter or the analog
> signal or the analog diode is affected by electric interference (which
> traveled from the computer to the TV along the HDMI cable) and the
> diode illuminates light blue instead of blue?
>
>> Having said that, you may be on the right track. I hadn't looked at your photo before, so sorry for that, but it indeed looks like your telly may be doing some scaling on the image.
>>
>> Check for overscan / underscan settings in the TV's menus and on the remote. The button for overscan may not be at all obvious on the remote from the icon that labels it - if you can't find a button on the remote that resolves this issue, or a overscan setting in the TV's menus then check the manual.
>>
>> Overscan would cause this symptom, and it is such a common feature, that IMO you shouldn't pst back here again until you've identified it on your TV and checked it.
>
> You may be right about this.  I can select the following aspect ratios
> on my TV's menu:
>
> 16:9 (this causes all 4 edges of the screen to be cut off)
> Just Scan (this is what I use and it fits perfectly on the screen)
> Set By Program (same as 16:9)
> 4:3 (same as 16:9 except with black boxes on the left and right)
> Zoom (same as 16:9 except more of the image is cut off)
> Cinema Zoom 1 (same as Zoom except nothing is cut off from the top of the image)
>
> I set 1920x1080 in xorg.conf but I just tried defining no resolution
> at all and it seems to have been set anyway:
>
> (II) RADEON(0): Output HDMI-0 using initial mode 1920x1080
>
> The TV is an LG 47LH90 and and it is said to do 1080p.  I looked for
> ghosting in 16:9 mode instead of Just Scan mode and strangely the
> shadows are there, but they're oriented top and bottom instead of left
> and right.  I can take another photo if anyone would like to see.
>
> Why do I need to select Just Scan in order to prevent all 4 edges of
> the screen from being cut off?
>
> - Grant

BTW I think you're on to something Stroller because the overall
picture is definitely improved in 16:9 mode compared to Just Scan
mode.  I just need to figure out how to prevent the edges of the
screen from being cut off.

- Grant



  reply	other threads:[~2011-07-19  0:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 23:21 [gentoo-user] Problem with xf86-video-ati & nvidia-drivers Grant
2011-07-10  0:20 ` meino.cramer
2011-07-11 23:48   ` Grant
2011-07-12 22:33     ` Grant
2011-07-13  2:27       ` meino.cramer
2011-07-13 15:55         ` Roger Mason
2011-07-13 16:17           ` meino.cramer
2011-07-13 17:13         ` Grant
2011-07-13 17:38           ` meino.cramer
2011-07-14 19:44             ` Grant
2011-07-14 20:07               ` Michael Mol
2011-07-14 23:29                 ` Grant
2011-07-14 20:23               ` [gentoo-user] " Nikos Chantziaras
2011-07-14 23:30                 ` Grant
2011-07-17 16:22                 ` Grant
2011-07-17 16:47                   ` Nikos Chantziaras
2011-07-17 16:54                     ` Grant
2011-07-17 21:53                       ` Michael Mol
2011-07-17 23:28                         ` Grant
2011-07-18 13:18                       ` [gentoo-user] " Stroller
2011-07-18 22:52                         ` Grant
2011-07-19  0:56                           ` Grant [this message]
2011-07-19 16:03                             ` Daniel Frey
2011-07-19 19:41                               ` Grant
2011-07-19 21:00                                 ` Mick
2011-07-20 18:38                                   ` Grant
2011-07-20 14:29                                 ` Stroller
2011-07-20 15:29                                   ` Michael Mol
2011-07-19  2:01                       ` [gentoo-user] " Volker Armin Hemmann
2011-07-19 20:35                         ` Grant
2011-07-19 20:54                           ` Michael Mol
2011-07-20 21:22                             ` Grant
2011-07-13  7:19       ` Nikos Chantziaras
2011-07-13 17:27         ` Grant
2011-07-13  7:13 ` Nikos Chantziaras
2011-07-13 12:25   ` Mick
2011-07-13 14:42     ` Nikos Chantziaras
2011-07-13 16:36       ` Mick
2011-07-16 16:22       ` Mick
2011-07-13 17:23   ` Grant
2011-07-14  6:13     ` Nikos Chantziaras

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=CAN0CFw1DsTC95uFUtrJ+1jDdDQ+1s9bjO-POC25wxR9026D4-A@mail.gmail.com \
    --to=emailgrant@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