[mythtv-users] Yet another NVidia 6200 1080i Component Output thread

[Jeff Wormsley]

Jeff Wormsley wrote:

Answering my own post with progress...

>3. Option "ConnectedMonitor" "TV" is called for in the nvidia README, 
>but others have said they had to use "TV-0"...
>  
>
Seems "TV" is correct here.

>4. I have errors in my xorg.0.log, but am not sure what they signify 
>(except the last one, it is a crash, but why, I don't know).
>
>(II) LoadModule: "speedo"
>(WW) Warning, couldn't open module speedo
>(II) UnloadModule: "speedo"
>(EE) Failed to load module "speedo" (module does not exist, 0)
>  
>
This was in someone's xorg.conf I got from the net.  Removed it and that 
goes away.

>(II) Loading extension NV-CONTROL
>(EE) NVIDIA(0): Failed to load GLX
>  
>
Removed GLX from xorg.conf, this goes away.

>   *** If unresolved symbols were reported above, they might not
>   *** be the reason for the server aborting.
>
>Fatal server error:
>Caught signal 11.  Server aborting
>
>Please consult the The X.Org Foundation support
>         at http://wiki.X.Org
> for help.
>Please also check the log file at "/var/log/Xorg.0.log" for additional 
>information.
>
>(EE) NVIDIA(0): unknown reason for exception
>(II) NVIDIA(0): EAX=0x00000003, EBX=0x00000000, ECX=0x00000000, 
>EDX=0x00000000
>(II) NVIDIA(0): ESP=0x00000ffa, EBP=0x00000000, ESI=0x00000000, 
>EDI=0x00000000
>(II) NVIDIA(0): CS=0x0000, SS=0x0100, DS=0x0040, ES=0x0000, FS=0x0000, 
>GS=0x0000
>(II) NVIDIA(0): EIP=0x00010000, EFLAGS=0x00033286
>(II) stack at 0x00001ffa:
> 00 06 00 00 00 32
>(II) NVIDIA(0): code at 0x00000000:
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>(EE) NVIDIA(0): cannot continue
>  
>
Added Option "NvAGP" "1" to xorg.conf, this goes away.

>5. During the boot process, POST and linux loading is "wrapped".  When X 
>loads, the nvidia logo appears breifly perfectly (not "wrapped", right 
>aspect ratio, etc), and then my TV goes crazy (it doesn't like whatever 
>the card is feeding it).  I can supply pictures of all of this if needed.
>  
>
This seems to be related to the NvAGP setting, as after I added that, it 
instead came up.  Only it came up with a 640x480 window inside a 1080i 
screen.  In other words, the actual display was a smallish square in the 
middle of the screen.  So I've added some of the 1080i modelines I've 
found on the net:

        ModeLine "1080i" 74.5 1920 1952 2016 2208 1080 1084 1096 1126 
-hsync -vsync interlace
        ModeLine "a1920x1080"    74.50   1920 1924 1988 2388   1080 1084 
1096 1259 -hsync -vsync interlace
        ModeLine "b1920x1080"    74.25   1920 1976 2010 2200   1080 1084 
1094 1125 +hsync +vsync interlace
        ModeLine "c1920x1080"    74.25   1920 1976 2011 2200   1080 1084 
1094 1125 -hsync -vsync interlace
        Modeline "d1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 
1124 interlace -hsync -vsync

These are all added to the Modes section, and they all "work".  They all 
look the same, and they are all horribly overscanned.  If I try to build 
a derivative ModeLine for a smaller resolution within any of these 
timings, then in my xorg.0.log I get errors saying they are not valid TV 
formats.

Running xvidtune is also interesting.  It will allow adjustments, but 
there is no effect.  I think the nVidia driver is overriding anything it 
doesn't think is a valid 1080i setup.  Clicking "Auto" and adjusting 
anything (wider, narrower, taller, shorted, left, right, up, or down) 
and I can adjust quite a bit without it saying it is outside the 
parameters, but the screen never changes (it sort of flickers and then 
looks just like it did before).

>6. So many of the posts I've read seem to be like "You need to do this 
>one thing and it will work".  However, I think they had done many other 
>things, and that "one thing" was just the last one.  I've tried every 
>suggestion I've found, and many besides, and all I can say is I know a 
>lot of things that don't work. ;-)
>  
>
Now I have a new issue.  I decided to try to live with the horrid 
overscan, and adjusted my GUI size in Myth to accomodate it.  Now, 
however, any time I try to play video, either with the internal player, 
mplayer, or xine, my computer hard locks.  I can't even ssh into it from 
another box.

I think this is being discussed right now on another thread about TVOut, 
so I'm going to go re-read that and see if there is a resolution (no pun 
intended) to this issue.

Jeff.