Bug 756194

Summary: No display when starting Fedora with only external display
Product: [Fedora] Fedora Reporter: Chris Bredesen <cbredesen>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: ajax, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 08:03:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Xorg log showing the error
none
dmesg output on failing boot none

Description Chris Bredesen 2011-11-22 22:13:55 UTC
Description of problem:

Lenovo T520 (Sandy Bridge) docked with DVI display connected and laptop lid closed.  Fedora enables the display but nothing shows on it.  X error as listed in attached Xorg log.

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

xorg-x11-drv-intel-2.17.0-1.fc16.i686

How reproducible:

Always.

Steps to Reproduce:
1. Start Fedora with laptop closed and display connected and powered up
2. Wait for GDM login screen
  
Actual results:

Blank display (but power is on, i.e. it's not in power save mode)

Expected results:

Actual working Fedora display.

Additional info:

I can coax the system into working by toggling the display using Fn-F7 to get to mirror mode and then shutting off the laptop display with the Displays applet.

Comment 1 Chris Bredesen 2011-11-22 22:14:35 UTC
Created attachment 535208 [details]
Xorg log showing the error

Comment 2 Adam Jackson 2011-11-28 17:06:04 UTC
Please boot with drm.debug=4 on the kernel command line, and attach dmesg from a boot in the failing configuration.

Comment 3 Chris Bredesen 2011-11-28 21:59:22 UTC
Created attachment 537692 [details]
dmesg output on failing boot

Adam - I captured a dmesg after a failed X session at boot.  First time I've mucked with grub2 so let me know if this file does not contain what you need.  

Thanks for looking!

Comment 4 Fedora End Of Life 2013-01-16 09:59:05 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 08:03:35 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.