Just as a last followup to my issue, this seems to be a know issue for nvidia. From them:
Hi Ken. Thanks for the bug report. We're aware of the problem
and hope to have this resolved in a future release.
I apologize for the inconvenience,
- Andy Ritger
On 9 Jan 2003, dominate wrote:
> I'm having a problem w/ the connectedmonitor option. I started messing
> around w/ connectedMonitor after getting a 2nd display and trying to set
> up twinview. After much trial and error, i noticed that i cannot
> specify CRT as my connectedMonitor for my CRT.
> If i do, the CRT display goes blank (looses input) and never comes back,
> even after blindly closing X and returning to text mode, or
> ctrl-alt-f1'ing back to the console.
> This problem occurs even if i ONLY configure 1 monitor, that being my
> CRT, and specify: Option "ConnectedMonitor" "CTR". Removing that
> setting fixes the problem. For my twinview setup, this results in a
> line like: Option "ConnectedMonitor" "DFP,"
> Setting up twinview took me quite a while, due only to this 1 bug.
> Some details:
> Leadtek winfast geforce 4 ti 4400
> kds avitron 17" crt
> my x config file is attach. It contains my current twinview setup,
> although other variations i have used are commented out and in there....