Summary: | [R500 X1400] Console fades to green | ||
---|---|---|---|
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: | major | ||
Priority: | high | CC: | lionel |
Version: | 7.4 (2008.09) | Keywords: | regression |
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Description
Bryce Harrington
2010-03-26 09:52:40 UTC
Created attachment 34488 [details]
dmesg.txt
Created attachment 34489 [details]
regdump_nomodeset.txt
Created attachment 34490 [details]
regdump_broke.txt
Created attachment 34491 [details]
"my desktop, invaded by the pink invasion (everything is frozen)"
Created attachment 34492 [details]
"switching to console"
Created attachment 34493 [details]
"note that the black "patch" on the right of the screen is not an artifact of the picture. It is well visible as something part of the corruption."
There's also a couple videos, probably too large to attach in bugzilla, but here's launchpad links: http://launchpadlibrarian.net/42038386/MVI_2260.ogv http://launchpadlibrarian.net/42038452/MVI_2261.ogv Some further comments from the reporter: """ With the latest upgrade (changelog says that DKMS is now enabled by default), the bug happens all the time, even with the nomodeset option or an old kernel. It looks like the nomodeset option is not working. (= The computer is totally unusable on Lucid) Also, it happens in recovery mode in console, as soon as the driver is loaded, without starting X! Finally, it seems to be related to the heat. In the morning, it doesn't happen for hours then it starts and become more and more frequent. Even full shut down are not sufficient. Shutting down the computer for one hour make it bug free for a couple of hours again. """ Original reporter doesn't have hardware anymore to test with. |
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.