Bug 11947

Summary: TFT monitor detected as 1x1 pixels
Product: xorg Reporter: Pierre Ossman <pierre-bugzilla>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log none

Description Pierre Ossman 2007-08-11 04:38:11 UTC
When I hook up my Fujitsu-Siemens Myrica VQ40-1 (a LCD TV) via DVI, the nouveau driver refuses to work, citing "no valid modes". The problem is that it believes that the screen is 1x1 pixels. Screen works fine on a radeon card via DVI.

The problem is also present in the nv driver.
Comment 1 Pierre Ossman 2007-08-11 04:40:41 UTC
Created attachment 11093 [details]
Xorg.0.log
Comment 2 Pierre Ossman 2007-12-22 16:05:08 UTC
Any ideas on this? Problem is still present.
Comment 3 Maarten Maathuis 2007-12-23 01:13:00 UTC
It's unlikely this will work, maybe the randr-1.2 driver (Option "Randr12" "1" in your device section) will have better luck detecting this. This will only help if your card has a dvi with a strange i2c bus.
Comment 4 Maarten Maathuis 2007-12-23 01:34:23 UTC
Please make sure you use an up-to-date driver if you are going to test randr-1.2, as it changes a lot.
Comment 5 Pierre Ossman 2007-12-30 11:04:39 UTC
Thanks. The RandR 1.2 code nicely detects and drives my monitor. Keep up the good work. :)
Comment 6 Pierre Ossman 2007-12-30 11:43:10 UTC
False positive. RandR12 false also gets the panel running with the new driver. So it's something that has been fixed between what Fedora 8 packages and HEAD.
Comment 7 Pierre Ossman 2008-01-03 11:17:12 UTC
False false positive. ;)

Further testing shows that non-RandR mode needs the BIOS to init the DVI output. But the RandR code can init the DVI fine on its own.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.