Driver 9625 - TV not detected at startup, but nv-settings does

[wvl0]

Hi,

I read that many people were experiencing trouble with TV-out. Apparently there's a workaround available by adding the ConnectedMonitor option.

My setup is simply a LCD + TV connected via SVIDEO.

I applied the workaround but that didn't work. The funny thing is that in the log I see that the nvidia driver cannot find the tv (it repeatedly says there's only a crt connected) but when I run nvidia-settings and press detect devices, the tv shows up in the screen layout box and can be configured. I wrote an xorg.conf file with the tv in twinview & seperate screen mode, but when I restart X only the LCD works.

Anyway, why is the TV not detected when X startsup, while nvidia-settings' detect devices does find it?

[lxnay]

I have the same problem man...

NVIDIA devs??

[netllama]

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

[Lithorus]

Can verify that I have the same problem here. Will produce a nvidia-bugreport later..

[netllama]

I believe that I've run into this problem, and opened bug 257362. However, I'd still like to see a bug report to verify that those reporting it here are hitting the same issue as I've come across. In my testing, using the ConnectedMonitor option works around the lack of TV encoder detection.

Thanks,
Lonni

[lxnay]

Originally Posted by netllama

I believe that I've run into this problem, and opened bug 257362. However, I'd still like to see a bug report to verify that those reporting it here are hitting the same issue as I've come across. In my testing, using the ConnectedMonitor option works around the lack of TV encoder detection.

Thanks,
Lonni

Sent
ConnectedMonitor does not work for me, I have always used that.

[netllama]

In the future, please post bug reports in the nvnews thread, so that all the information is in the same location.

Thanks,
Lonni

[sams0n]

Originally Posted by netllama

I believe that I've run into this problem, and opened bug 257362. However, I'd still like to see a bug report to verify that those reporting it here are hitting the same issue as I've come across. In my testing, using the ConnectedMonitor option works around the lack of TV encoder detection.

Thanks,
Lonni

You are just damn lucky. ConnectedMonitor does NOT work around this issue. With the current beta driver I can set:

a) Twinview (though I do NOT want it)
b) Separate TV
c) Separate LCD

But NO I CANNOT set them both working together (I will bug report later). If I use ConnectedMonitor option - TV wakes up and runs the second X screen (as should) but the LCD (the first X screen) goes "out of singnal" as nvidia driver sets some crazy refresh rate (for LCD) of around 141hz. Yes, nvidia driver completely ignores the refresh rates I put in the LCD Monitor section.

The funny thing - the nvidia-settings detects my TV, but I cannot use it (ConnectedMonitor does NOT help). Sorry for the long post.

PS: Would you, nvidia guys, consider the following driver options:

**Section Device**
Option "DetectMonitor" "CRT-0" # detects and uses any found CRT

or

**Section Device**
Option "ForceMonitor" "TV-0" # just sends the signal to the videocard's TVout (like damn old vcr do) No bloody buggy detection

PPS: I will post my bugreport later. Thanks

[lxnay]

sams0n,
so a workaround for now is only using TV, without TwinView?
Does Dual X works for you?

Anyway, I had the same setup with the latest 8xxx drivers and everything worked fine.

[netllama]

sams0n,
The problems that you're describing sounds different than the problems that others are reporting here. However, without a bug report, I can't speculate on what is happening on your system.

The ConnectedMonitor option already accomplishes what your suggested new options do.

Thanks,
Lonni

[lxnay]

Lonni,
here you are.

[sams0n]

Originally Posted by lxnay

sams0n,
so a workaround for now is only using TV, without TwinView?
Does Dual X works for you?

Anyway, I had the same setup with the latest 8xxx drivers and everything worked fine.

Quick answer - no, no dualhead for me

PS: With 87** something I had it working too. Alas, there are new xorgs and new kernels.