Bug 25786

Summary: KMS turns off monitor on Asus A7N266-VM motherboard with onboard NVCrush11 [GeForce2 MX Integrated Graphics]
Product: xorg Reporter: Rajeev V. Pillai <rajeevvp>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: medium CC: rajeevvp
Version: 7.5 (2009.10)   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg output with KMS
none
X log without KMS
none
lsmod module list
none
lspci device listing
none
/proc/mtrr details none

Description Rajeev V. Pillai 2009-12-23 18:35:57 UTC
Created attachment 32268 [details]
dmesg output with KMS

All the nouveau kernel modules after the big merge on 2009-12-08 (id=69d47626b81fc1abf0e0e06ad623ead9be011341) turn off the LCD monitor because it fails to detect connector connected with modes: "No connectors reported connected with modes"

The X server, of course, does not start. Without KMS, X works ok (there are some issues, but, nothing that makes X unusable), but the VGA fonts are totally trashed during X init and not properly restored on exit.

$ uname -a
Linux athlon.localdomain 2.6.32.2 #1 PREEMPT Sat Dec 19 09:20:29 IST 2009 i686 GNU/Linux

X org: xorg-server-1.7.3.901

nouveau DDX: from git.
Comment 1 Rajeev V. Pillai 2009-12-23 18:36:58 UTC
Created attachment 32269 [details]
X log without KMS

X log file without KMS.
Comment 2 Rajeev V. Pillai 2009-12-23 18:37:43 UTC
Created attachment 32270 [details]
lsmod module list

lsmod module listing.
Comment 3 Rajeev V. Pillai 2009-12-23 18:38:13 UTC
Created attachment 32271 [details]
lspci device listing

lspci device listing
Comment 4 Rajeev V. Pillai 2009-12-23 18:38:55 UTC
Created attachment 32272 [details]
/proc/mtrr details

MTRR details
Comment 5 Rajeev V. Pillai 2009-12-23 23:26:24 UTC

*** This bug has been marked as a duplicate of bug 25619 ***

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.