[Bug 31213] New: [drm] *ERROR* with KMS (any kernels 2.6.3x.x) and ati mobility radeon X300

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Oct 29 06:16:12 PDT 2010


           Summary: [drm] *ERROR* with KMS (any kernels 2.6.3x.x) and ati
                    mobility radeon X300
           Product: DRI
           Version: XOrg CVS
          Platform: x86 (IA32)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel at lists.freedesktop.org
        ReportedBy: djnass_18 at hotmail.com

when loading the 'radeon' driver with modeset=1 (KMS enabled) 
the following error appears in dmesg | grep drm

[drm:r100_ring_test] *ERROR* radeon: ring test failed
[drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22).

the result is that OpenGL renderer with be the 'software rasterizer'. and
performance is obviously crippled.

glxinfo returns:

OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.8.1

The error occurs with kernels, and even the latest at the
time 2.6.36. The pc is a toshiba satellite m40-185 laptop with ati mobility
radeon X300 (rv370) gpu.

Additionally, I have tried installing the git versions of libdrm, mesa, and
xf86-video-ati to this date (29/10/2010) with Gallium support (enabled in turn
--enable-gallium, --enable-gallium-radeon and even both, using llvm (version
2.8) compiler. The problem persists.

The only way to get 3d accelaration is to disable KMS. then dmesg | grep drm
seems to load up fine (see here: http://pastebin.com/vNfyeq7P). But then I have
problems with 3d applications 'competing' to stay on top - they don't seem to
be able to work well with KDE4 compositing effects. To avoid that I have to
disable the compositing effects ( see here for in depth explanation and some
Xorg.0.log and dmesg outputs

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