From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Qiyct-0001aR-I3 for garchives@archives.gentoo.org; Tue, 19 Jul 2011 00:57:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 804F921C099; Tue, 19 Jul 2011 00:57:18 +0000 (UTC) Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 2B4CE21C023 for ; Tue, 19 Jul 2011 00:56:15 +0000 (UTC) Received: by ewy8 with SMTP id 8so2119914ewy.40 for ; Mon, 18 Jul 2011 17:56:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=/mMR91MrA0lThS0tKbS2lRfA6YsLTuzuustfTL/e2rA=; b=BFgziDrN/XML18Ll+Hw/j/Q16qDR7TCPLpuMjdtiHTM3DrDbAGS6yBVf9batiILeeC 1BtfQpGHxdQNea8EUia7Pq2aGRReSM/0+BwZZVY0zWdvyBY63Q8B7i+5LyqmUCkH932K 5if1XGRVr9GTUwOVtHlp+u8Kv4DqFsEIUzGYo= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.14.96.205 with SMTP id r53mr2534101eef.177.1311036975280; Mon, 18 Jul 2011 17:56:15 -0700 (PDT) Received: by 10.14.50.203 with HTTP; Mon, 18 Jul 2011 17:56:15 -0700 (PDT) In-Reply-To: References: <20110710002013.GB3068@solfire> <20110713022717.GA3026@solfire> <20110713173836.GC3026@solfire> <5763C753-514B-42F8-93D2-3F372137AA5F@stellar.eclipse.co.uk> Date: Mon, 18 Jul 2011 17:56:15 -0700 Message-ID: Subject: Re: [gentoo-user] Problem with xf86-video-ati & nvidia-drivers From: Grant To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 66ec08c5d26c84172cc6c10090a961ea >>> But at some point the 1s and 0s must be converted to some sort of an >>> analog signal if only right behind the diode. =A0A diode must be >>> presented with a signal in some sort of analog form in order to >>> illuminate, right? =A0Digital is just a figment of our imagination afte= r >>> all. >> >> The pixel is either on or off. There's no way to make half of the adjace= nt 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 b= e doing some scaling on the image. >> >> Check for overscan / underscan settings in the TV's menus and on the rem= ote. The button for overscan may not be at all obvious on the remote from t= he icon that labels it - if you can't find a button on the remote that reso= lves this issue, or a overscan setting in the TV's menus then check the man= ual. >> >> 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 T= V and checked it. > > You may be right about this. =A0I 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. =A0I 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. =A0I 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