Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 589907 - Display blanks when modesetting on Intel chipsets
Summary: Display blanks when modesetting on Intel chipsets
Keywords:
Status: CLOSED DUPLICATE of bug 587171
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-07 09:20 UTC by Jonathan Dieter
Modified: 2010-05-07 12:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-07 12:24:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Xorg log (deleted)
2010-05-07 09:20 UTC, Jonathan Dieter 		no flags Details
lspci -n output (deleted)
2010-05-07 09:21 UTC, Jonathan Dieter 		no flags Details
dmesg output (deleted)
2010-05-07 09:23 UTC, Jonathan Dieter 		no flags Details
lspci -n output from second type of intel motherboard (deleted)
2010-05-07 09:54 UTC, Jonathan Dieter 		no flags Details
lspci -n output from third type of intel motherboard (deleted)
2010-05-07 09:56 UTC, Jonathan Dieter 		no flags Details
Xorg log from working motherboard type (deleted)
2010-05-07 10:00 UTC, Jonathan Dieter 		no flags Details
lspci -n output from working motherboard type (deleted)
2010-05-07 10:00 UTC, Jonathan Dieter 		no flags Details
dmesg output from working motherboard type (deleted)
2010-05-07 10:03 UTC, Jonathan Dieter 		no flags Details
View All

Description Jonathan Dieter 2010-05-07 09:20:41 UTC 
Created attachment 412273 [details]
Xorg log

Description of problem:
When I try to install Fedora 13 (over PXE, local mirror updated today) onto a desktop with an Intel chipset, the display goes blank with a "Input out of range" error coming from the monitor.  I can SSH into the computer, but the only way to continue the install is using VNC.

As I can see the first second or so of the kernel loading, I believe the problem occurs when the modesetting happens.  Changing the monitor didn't fix the problem.

Version-Release number of selected component (if applicable):
2.6.33.3-79.fc13.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start PXE install
  
Actual results:
Blank monitor with "Input out of range" message

Expected results:
Fedora install screen
Comment 1 Jonathan Dieter 2010-05-07 09:21:46 UTC 
Created attachment 412275 [details]
lspci -n output
Comment 2 Jonathan Dieter 2010-05-07 09:23:27 UTC 
Created attachment 412276 [details]
dmesg output
Comment 3 Jonathan Dieter 2010-05-07 09:53:53 UTC 
I've just finished installing the system over VNC, and the bug persists when the system is booted normally, so it's not just an installation problem.  I've swapped in another monitor that's the same resolution as the previous one (1280x1024), but the display stays blank, even if I kill and restart X.

We have several other motherboards with similar hardware, and two out of three have the blank screen.
Comment 4 Jonathan Dieter 2010-05-07 09:54:43 UTC 
Created attachment 412282 [details]
lspci -n output from second type of intel motherboard
Comment 5 Jonathan Dieter 2010-05-07 09:56:39 UTC 
Created attachment 412283 [details]
lspci -n output from third type of intel motherboard
Comment 6 Jonathan Dieter 2010-05-07 10:00:03 UTC 
Created attachment 412286 [details]
Xorg log from working motherboard type
Comment 7 Jonathan Dieter 2010-05-07 10:00:53 UTC 
Created attachment 412287 [details]
lspci -n output from working motherboard type
Comment 8 Jonathan Dieter 2010-05-07 10:03:08 UTC 
Created attachment 412288 [details]
dmesg output from working motherboard type
Comment 9 Jonathan Dieter 2010-05-07 12:24:43 UTC 

*** This bug has been marked as a duplicate of bug 587171 ***
Note You need to log in before you can comment on or make changes to this bug.