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 586235 - [KMS] Out of Scan Range
Summary: [KMS] Out of Scan Range
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-27 06:33 UTC by Marko Myllynen
Modified: 2010-05-18 08:09 UTC (History)
7 users (show)

Fixed In Version: kernel-2.6.33.3-85.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-18 08:09:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
dmesg output, screen normal (deleted)
2010-04-27 06:34 UTC, Marko Myllynen 		no flags Details
dmesg output, screen blank (deleted)
2010-04-27 06:34 UTC, Marko Myllynen 		no flags Details
diff of good vs. bad drm messages (deleted)
2010-04-28 13:41 UTC, Chuck Ebbert 		no flags Details
View All

Description Marko Myllynen 2010-04-27 06:33:03 UTC 
Description of problem:
After installing Fedora 13 Beta on a system with Intel display adapter and an old Sun monitor everything worked ok. However, after upgrading to kernel 2.6.33.2-57.fc13.i686.PAE and booting, then while KMS is being enabled the screen goes blank and the monitor displays information "Out of Scan Range".

I'll attach dmesg outputs with both kernels using drm.debug=0x06.

Version-Release number of selected component (if applicable):
2.6.33.2-57.fc13.i686.PAE

How reproducible:
Always
Comment 1 Marko Myllynen 2010-04-27 06:34:19 UTC 
Created attachment 409365 [details]
dmesg output, screen normal
Comment 2 Marko Myllynen 2010-04-27 06:34:45 UTC 
Created attachment 409366 [details]
dmesg output, screen blank
Comment 3 Chuck Ebbert 2010-04-28 13:41:47 UTC 
Created attachment 409833 [details]
diff of good vs. bad drm messages
Note You need to log in before you can comment on or make changes to this bug.