Just recently upgraded to a Radeon HD6450. Upon boot, as soon as fbcon takes over, the screen gets corrupted. (note X is not started on boot). SSHing into the box and starting and restarting X a couple time sometimes fixes the issue, sometimes locks of the machine.
Created attachment 64638 [details] DMESG after booting with screen corruption
Created attachment 64639 [details] DMESG after restarting X a couple time to fix the issue
Created attachment 64640 [details] Xorg log after issue is gone
Created attachment 64641 [details] Picture of screen corruption
I would consider having a look at bug 43655, it might be related. Could you try workaround proposed in comment 8 (bug 43655#c8) or comment 13 (bug 43655#c13)?
I am not using grub2, so I do not believe that the workaround in BUG 43655 are relevant. I do not have these lines in my grub.conf
Possible duplicate of BUG 42373?
Created attachment 64758 [details] [review] Cleanup and fix mc programing This patch should fix your issue
I do not see any improvement after applying the proposed patch
Maybe I have the same problem. Tested on ubuntu 13.04 and 13.10， my new HD6450 just gives me the same corrupted screen as yours. On windows, it works with no problem. (In reply to comment #4) > Created attachment 64641 [details] > Picture of screen corruption
Created attachment 88477 [details] corrupted screen on ubuntu 13.04 corrupted screen on ubuntu 13.04
I believe kernel-3.8 and 3.11 already have these patches, but it looks like doesn't work. (In reply to comment #5) > I would consider having a look at bug 43655, it might be related. Could you > try workaround proposed in comment 8 (bug 43655#c8) or comment 13 (bug > 43655#c13)?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/287.
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.