Bug 735770

Summary: [NVa8] External monitor doesn't work after upgrade to F16
Product: [Fedora] Fedora Reporter: Jiri Moskovcak <jmoskovc>
Component: 0xFFFFAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: dfediuck, dwmw2, mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: [cat:modesetting]
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-13 09:03:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 713564    
Attachments:
Description Flags
nouveau xorg log drm.debug=0x04
none
mangled output
none
messages
none
dmesg output none

Description Jiri Moskovcak 2011-09-05 10:32:07 UTC 
Description of problem:
After updating from F15 to F16, my external monitor stopped working.

Version-Release number of selected component (if applicable):

xorg-x11-server-Xorg-1.10.99.902-1.20110818.fc16.x86_64
glibc-2.14.90-4.x86_64

How reproducible:
100%

Steps to Reproduce:
1. try to set up external monitor in F16
  

Actual results:
Tried nv, nouveau even nvidia (the official binaries with IgnoreABI) and none of them works. The monitor sometimes turn on with nouveau, but the image is mangled - seems like wrong refresh rate and after a few secs it turns off.

Expected results:
Working external lcd.

Additional info:
My GPU is:
01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2)
Comment 1 Matěj Cepl 2011-09-05 11:33:20 UTC 
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 2 Jiri Moskovcak 2011-09-05 12:51:32 UTC 
Created attachment 521495 [details]
nouveau xorg log drm.debug=0x04

$ grep Backtrace /var/log/Xorg*
-> gives nothing
Comment 3 Jiri Moskovcak 2011-09-05 12:55:03 UTC 
Created attachment 521497 [details]
mangled output
Comment 4 Jiri Moskovcak 2011-09-05 13:00:26 UTC 
Created attachment 521500 [details]
messages
Comment 5 Jiri Moskovcak 2011-09-05 13:01:03 UTC 
Created attachment 521501 [details]
dmesg output
Comment 6 Jiri Moskovcak 2011-09-13 09:03:40 UTC 
Fixed, it was a HW problem.