TV out useless after debian squeeze upgrade

[Barracuda_666]

I've got trouble with the tv out of my 9300GS. As i start to build my system, i spent a lot of hours to make it work cause none of the newer driver versions detect my tv. I've tried several configurations with twinview and only the tv pluged in, btw the tv is connected through a scart adaptor over a svideo cable to the svideo out of the board. Finally i got it working with the older 180.60 driver.
After the latest upgrade of my debian squeeze the driver module won't load anymore and X dies with the message "nvidia_drv.so: undefined symbol: resVgaShared". Unfortunately it's not possible to downgrade X.
All driver versions prior 190.18 i've tested won't load and all versions above doesn't find my tv. Mainly i need the system as VDR and a VDR without tv out is somewhat useless :/
Is there a possible solution in sight or any workaround known?

thanks in advance

[Barracuda_666]

with the legacy driver i got tv out working again. but now none of the main apps (mythtv, mplayer) wanna start, cause the lack of libvdpau.so.1 of course. does anybody know how i can by-pass loading this library (but i assume it's not possible)

thanks in advance

[danix]

Hi Barracuda_666,

Thanks for reporting this issue. I haven't been able to reproduce it here... at first I thought perhaps it might have something to do with NTSC vs. PAL, but another user has reported similar problems with a North American TV...

http://www.nvnews.net/vbulletin/showthread.php?t=149152

As for mplayer and mythtv, you can build these without VDPAU support, but I'm not aware of a better way to work around this off the top of my head...

[Barracuda_666]

Hi danix,

thanks for reply!
I remeber, this was another unsuccessful try. by setting the "ConnectedMonitor" option i got the same strange behavior as Garthecho has. the mouse pointer is invisible, the tv-encoder will be detected but i got no signal at tv. If i set "HWCursor" to false i got the pointer back at least.

greetings

addition:
If i only set "CRT" at the relevant Options, the drive tries to bind the screen to "CRT-0" which fails and the monitor went blank.

PHP Code:

(**) Mar 24 12:40:00 NVIDIA(0): Enabling RENDER acceleration
(**) Mar 24 12:40:00 NVIDIA(0): Forcing SVIDEO output
(**) Mar 24 12:40:00 NVIDIA(0): TV Standard string: "PAL-B"
(**) Mar 24 12:40:00 NVIDIA(0): ConnectedMonitor string: "CRT, TV-0"
(WW) Mar 24 12:40:01 NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
(II) Mar 24 12:40:01 NVIDIA(0): NVIDIA GPU GeForce 9300 GS (G98) at PCI:1:0:0 (GPU-0)
(--) Mar 24 12:40:01 NVIDIA(0): Memory: 524288 kBytes
(--) Mar 24 12:40:01 NVIDIA(0): VideoBIOS: 62.98.29.00.36
(II) Mar 24 12:40:01 NVIDIA(0): Detected PCI Express Link width: 16X
(--) Mar 24 12:40:01 NVIDIA(0): Interlaced video modes are supported on this GPU
(--) Mar 24 12:40:01 NVIDIA(0): Connected display device(s) on GeForce 9300 GS at PCI:1:0:0:
(--) Mar 24 12:40:01 NVIDIA(0):     CRT-0
(--) Mar 24 12:40:01 NVIDIA(0):     NVIDIA TV Encoder (TV-0)
(--) Mar 24 12:40:01 NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
(--) Mar 24 12:40:01 NVIDIA(0): NVIDIA TV Encoder (TV-0): 400.0 MHz maximum pixel clock
(--) Mar 24 12:40:01 NVIDIA(0): TV encoder: NVIDIA
(**) Mar 24 12:40:01 NVIDIA(0): TwinView enabled
(II) Mar 24 12:40:01 NVIDIA(0): Option "UseDisplayDevice" "CRT, TV-0" converted to "CRT-0,
(II) Mar 24 12:40:01 NVIDIA(0):     TV-0".
(II) Mar 24 12:40:01 NVIDIA(0): Assigned Display Devices: CRT-0, TV-0
(II) Mar 24 12:40:01 NVIDIA(0): Validated modes:
(II) Mar 24 12:40:01 NVIDIA(0):     "CRT:1024x768+0+0,TV-0:1024x768+1024+0"
(II) Mar 24 12:40:01 NVIDIA(0): Virtual screen size determined to be 2048 x 768
(WW) Mar 24 12:40:01 NVIDIA(0): Unable to get display device CRT-0's EDID; cannot compute DPI
(WW) Mar 24 12:40:01 NVIDIA(0):     from CRT-0's EDID.
(==) Mar 24 12:40:01 NVIDIA(0): DPI set to (75, 75); computed from built-in default
(==) Mar 24 12:40:01 NVIDIA(0): Disabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) Mar 24 12:40:01 NVIDIA: Using 768.00 MB of virtual memory for indirect framebuffer
(II) Mar 24 12:40:01 NVIDIA:     access.
(II) Mar 24 12:40:01 NVIDIA(0): Initialized GPU GART.
(II) Mar 24 12:40:01 NVIDIA(0): Setting mode "CRT:1024x768+0+0,TV-0:1024x768+1024+0"


I attached the last xorg.0.log with "ConnectedMonitor" option set, if it helps.

[t3hl33td4rg0n]

Well, I guess i should throw it out there as well. I have a 660, running 190.53, and the nvtv package would not recognize the TV out.

Currently I am using DVI to HDMI, but the screen is cutoff quite a bit and figured the TV out would get rid of it. Whenever it boots, it says that it couldnt find the TV out.

[primerib]

Originally Posted by t3hl33td4rg0n

Well, I guess i should throw it out there as well. I have a 660, running 190.53, and the nvtv package would not recognize the TV out.

Currently I am using DVI to HDMI, but the screen is cutoff quite a bit and figured the TV out would get rid of it. Whenever it boots, it says that it couldnt find the TV out.

I used VDR and an dvi->hdmi config for quite some time with no problems what-so-ever. If your screen is cut off then check your xorg.conf (overscan) and tv settings (on the actual tv).

[Garthecho]

Hi Barracuda_666. Looks like we have the same problem. Until this is fixed properly, I just wanted to point you to a somewhat complicated but functional workaround I posted elsewhere on the net to someone else with this issue.

It may get you up and running for now...

http://www.linuxforums.org/forum/ubu...detect-tv.html

[Barracuda_666]

thanks for advice.

this didn't make my tv run. i tried the changes at the current driver, cause the 185.* driver didn't load with in X 1.7, with out success.

[Garthecho]

Sorry to hear that. Looks like I'll be waiting to upgrade to Ubuntu 10.04.

[danix]

Originally Posted by Barracuda_666

the 185.* driver didn't load with in X 1.7, with out success.

The 185 branch doesn't support X.org 1.7, but the legacy branches do. If your card is supported by the legacy 173 branch (9500 GT should work) then you might want to give this a try for the time being.

[Barracuda_666]

Originally Posted by danix

... then you might want to give this a try for the time being.

Can i interpret this as you've found/reproduced this problem and we can face on a solution in a future release? Or do you mean "the plans" to integrate X 1.7 support at the 185 branch?

thanks for help

[danix]

I still haven't reproduced the TV-out problems.

The 185 branch does not support X.org 1.7. I'm not aware of any plans to support X.org 1.7 in the 185 branch, as the 195 branch supports X.org 1.7 and supports all GPUs supported by 185.

The 71, 96, and 173 legacy branches are still maintained to provide support for older GPUs. The 173 branch *should* support GeForce 9 series, but YMMV. Since this appears to be a regression in the driver, the 173 branch should work for now until the problem with the newer drivers and TV-out can be identified.

FWIW, I'm testing with a 9300GS at the moment. It's possible that the issue might be specific to some TVs, so I'll try a few other TVs. (Have you tested any other TVs?)