[mythtv-users] Modelines

[PJR]

On 28/01/14 10:37, John Pilkington wrote:
> On 28/01/14 03:42, Robert Dege wrote:
>> Neither Game Mode, nor switching HDMI ports resolved the overscan
>> problem.
>>
>> @Gary - One of the HDMI inputs was already labelled 'PC'.  So this had
>> no effect
>>
>> @Kenni - I own a Samsung HL-S5687W.  It's a DLP system from 2006.  I
>> tried your xorg.conf, but it had no effect.  I checked the log files,
>> and the config was read, along with /usr/share/X11/xorg.conf.d.  There
>> was also this towards the end of the log:
>>
>> [     5.453] (**) NVIDIA(0): Not using HorizSync/VertRefresh ranges from
>> the EDID for
>> [     5.453] (**) NVIDIA(0):     display device SAMSUNG (DFP-1) (Using
>> EDID frequencies has
>> [     5.453] (**) NVIDIA(0):     been disabled on all display devices.)
>> [     5.453] (II) NVIDIA(0): Mode Validation Overrides for SAMSUNG
>> (DFP-1):
>> [     5.453] (II) NVIDIA(0):     NoEdidModes
>> [    10.799] (II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not
>> support NVIDIA 3D Vision
>> [    10.799] (II) NVIDIA(GPU-0):     stereo.
>> [    10.799] (**) NVIDIA(0): Not using HorizSync/VertRefresh ranges from
>> the EDID for
>> [    10.799] (**) NVIDIA(0):     display device SAMSUNG (DFP-1) (Using
>> EDID frequencies has
>> [    10.799] (**) NVIDIA(0):     been disabled on all display devices.)
>> [    10.799] (II) NVIDIA(0): Mode Validation Overrides for SAMSUNG
>> (DFP-1):
>> [    10.799] (II) NVIDIA(0):     NoEdidModes
>> [    10.824] (II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-1)) does not
>> support NVIDIA 3D Vision
>> [    10.824] (II) NVIDIA(GPU-0):     stereo.
>>
>>
>> Any idea what that means?
>>
>> -Robert
>>
>>
>> On Mon, Jan 27, 2014 at 3:46 PM, Kenni Lund <kenni at kelu.dk
>> <mailto:kenni at kelu.dk>> wrote:
>>
>>     2014-01-27 Robert Dege <livemotion at gmail.com
>>     <mailto:livemotion at gmail.com>>:
>>      > @Mike - I have a Samsung TV, which has two HDMI ports, and a Game
>>     Mode.  I
>>      > currently have the TV configured for Movie mode, but will try
>>     enabling Game
>>      > mode to see if it makes a difference.  I will also toggle between
>>     the two
>>      > HDMI ports.  One of the ports doubles as a DVI in, when using a
>>     HDMI to DVI
>>      > adapter.
>>      >
>>      >
>>      > @ Raymond - The overscan affects all programs, including xfce (I
>>     am unable
>>      > to see the panel across the top of the screen).  I did try the
>>     screen setup
>>      > wizard, but it only made minor adjustments... not enough to
>>     resolve the
>>      > issue.
>>      >
>>      >
>>      > @ Kenni - Thank you for the judder free link.  I will check it
>>     out later
>>      > this evening if the above TV suggestions are ineffective.
>>
>>     Robert, which Samsung model do you have? The xorg.conf I posted on
>>     pastebin should work with most - if not all - Samsung full HD TVs
>>     released within the past few years. I've used it for 5 or 6
>> different
>>     Samsung models with success. You should NOT use the screen setup
>>     wizard with a Samsung full HD TV.
>>
>>     Save the file in /etc/X11/xorg.conf and reboot your system and
>> see if
>>     it works. If you have a current generation LED TV ("F"), you should
>>     likely set "Picture Size" on your TV to "Screen Fit" or
>> alternatively
>>     "16:9" to get a 1:1 pixel mapping.
>>
>>     When you get the screen size fixed, you should also set the Picture
>>     Sharpness filter to "0" instead of the default "50", as this will
>>     improve the picture quality dramatically when using a PC as source.
>>
>>     Best regards
>>     Kenni
>
> I have a monitor (CRT:) and a Panasonic TV (DFP:) and my Xorg.0.log,
> too, is anxious to let me know that they don't support 3D Vision.  The
> TV has an 'Overscan Off' setting in its menu, but it /ALSO/ requires
> the Aspect ratio, set from the TV remote, to be 16:9.  Then
> nvidia-auto-select works fine.  nVidia 304.119.   When I want Myth on
> the TV I use
>
> #!/bin/bash
> export DISPLAY=:0.1
> mythfrontend --geometry 1920x1080+0+0
> # mythfrontend --geometry 1860x1046+30+16
>
> This provoked argument in a thread here last March, but in the end it
> was agreed to be justified.
>
> John P
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
Robert, re "what does the log file snip mean?".  The xorg logfile start
with this "

|Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.`|

"

which should help to decode what it means.  Most of it is just for
information (II), ie hasn't been used in the setup.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140128/88e71a36/attachment.html>