Summary: | [Radeon FireGL 9000 RV250] Blank screen when switching to lower resolutions in X | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Bryce Harrington <bryce> | ||||||||||||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||||||||||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||||||
Severity: | normal | ||||||||||||||||||
Priority: | high | CC: | jamesrudee, peter.vd.meer | ||||||||||||||||
Version: | 7.3 (2007.09) | ||||||||||||||||||
Hardware: | Other | ||||||||||||||||||
OS: | Linux (All) | ||||||||||||||||||
Whiteboard: | |||||||||||||||||||
i915 platform: | i915 features: | ||||||||||||||||||
Attachments: |
|
Description
Bryce Harrington
2009-01-30 17:09:11 UTC
Created attachment 22399 [details] [review] xrandr output Created attachment 22400 [details] [review] Xorg.0.log_normalLogin Created attachment 22401 [details]
Xorg.0.log_loginAndSwitchTo800x600
Created attachment 22402 [details]
regdump_broke.txt
radeontool regmatch '*' > regdump_broke.txt
xrandr --output LVDS --mode 1400x1050
Created attachment 22403 [details]
regdump_good.txt
radeontool regmatch '*' > regdump_good.txt
xrandr --output LVDS --mode 800x600
Created attachment 29703 [details]
Logs for the 6.12 branch.
I also tested with the 6.12 branch (that I just compiled and installed today). The problem also appears here. Attached are the XOrg.log-files, the reg-dumps and the test-program that created the logs.
Created attachment 29705 [details]
The Xorg.log in vesa mode
All resolutions seem to work ok in Vesa mode. Attached is the xorg.log for reference when running in Vesa mode.
Is this still an issue with kms or a newer version of the driver? (In reply to comment #8) > Is this still an issue with kms or a newer version of the driver? Unfortunately I can no longer test this. I already sold the affected laptop. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.