Bug 586235 - [KMS] Out of Scan Range
[KMS] Out of Scan Range
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-27 02:33 EDT by Marko Myllynen
Modified: 2010-05-18 04:09 EDT (History)
7 users (show)

See Also:
Fixed In Version: kernel-
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-18 04:09:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
dmesg output, screen normal (55.65 KB, text/plain)
2010-04-27 02:34 EDT, Marko Myllynen
no flags Details
dmesg output, screen blank (55.36 KB, text/plain)
2010-04-27 02:34 EDT, Marko Myllynen
no flags Details
diff of good vs. bad drm messages (20.36 KB, text/plain)
2010-04-28 09:41 EDT, Chuck Ebbert
no flags Details

  None (edit)
Description Marko Myllynen 2010-04-27 02:33:03 EDT
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 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):

How reproducible:
Comment 1 Marko Myllynen 2010-04-27 02:34:19 EDT
Created attachment 409365 [details]
dmesg output, screen normal
Comment 2 Marko Myllynen 2010-04-27 02:34:45 EDT
Created attachment 409366 [details]
dmesg output, screen blank
Comment 3 Chuck Ebbert 2010-04-28 09:41:47 EDT
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.