[Bug 42373] New: Radeon HD 6450 (NI CAICOS) screen corruption on boot

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Oct 29 09:03:58 PDT 2011


             Bug #: 42373
           Summary: Radeon HD 6450 (NI CAICOS) screen corruption on boot
    Classification: Unclassified
           Product: DRI
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel at lists.freedesktop.org
        ReportedBy: kunal.gangakhedkar at gmail.com
        Depends on: 40935

Created attachment 52891
  --> https://bugs.freedesktop.org/attachment.cgi?id=52891
dmesg log

Bought a new Radeon HD 6450 for the new desktop I was building using PhenomII
X6 1075T.

Installed Kubuntu Oneiric (11.10) amd64.
As soon as any FB client (e.g. plymouth splash screen) starts accessing the
card after switching to KMS, the screen image gets totally corrupted.

Even Xorg/KDM fail to show anything useful.
I can only reset the machine using the power button soft-off.
Three-finger-salute also doesn't work.

However, it does work in about 1 out of 10 times - if somehow the apps trying
to use FB device can be killed while the radeon driver is trying to work on the

If KMS is disabled, the machine boots up, but Xorg fails to start saying "KMS
is needed for CAICOS".

The screenshots are available at:
a. KMS with plymouth splash:
b. KMS without plymouth splash (shows init msgs with bluish tinge in the
background): http://img1.UploadScreenshot.com/images/main/10/30100182712.jpg
c. KMS + Xorg lockup:
d. KMS + Xorg successful start:

I believe this is the same as bug #40935 - however, I haven't been able to boot
into the system to test suspend/resume yet.

Finally, I used an old nVidia GeForce 7100 GS  on the same system that I had
lying around as a workaround.

Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the dri-devel mailing list