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 (sracth(0x15E4)=0xCAFEDEAD) [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 2.6.33.4, 2.6.35.7 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 http://www.linuxquestions.org/questions/slackware-14/3d-applications-compete-to-stay-on-top-with-the-radeon-driver-840392/ )
Is this still and issue with current kernel ?
(In reply to comment #0) > 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 > (sracth(0x15E4)=0xCAFEDEAD) > [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). Max: ping? How do current kernels behave? In suspense, Jonathan
-- 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/162.
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.