Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#17695 - [xorg] radeon driver very slow (and unstable) acceleration for RV250 chipset
Attached to Project:
Arch Linux
Opened by Andre Herbst (moormaster) - Sunday, 03 January 2010, 11:16 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 03 May 2010, 16:47 GMT
Opened by Andre Herbst (moormaster) - Sunday, 03 January 2010, 11:16 GMT
Last edited by Andreas Radke (AndyRTR) - Monday, 03 May 2010, 16:47 GMT
|
DetailsDescription:
* glxgears uses 100% CPU in fullscreen even though glxinfo is showing that the MESA DRI R200 renderer is used. * running nexuiz leads to unplayable slow framerate ( < 0.2 fps ) * hedgewars does not even start... it just opens up a window and closes it again (and this is not a 3d game...) * googleearth has many graphic errors and sometimes causes Xorg to lock up... or even more weird: the mounted filesystems suddenly get unusable... reading files causes I/O Errors and writing fails due to not enough space left (even though there is...) I have also tried to use EXA AccelMethod... this lead glxgears to work fine in fullscreen with ~5% CPU usage hedgewars is able to start games... but with similiar graphic errors like googleearth (but still very slow) googleearth is as unstable as it was using XAA before :D Though it has graphic errors googleearth is the only program which seems to run with a usable framerate (besides glxgears). Additional info: * package version(s) xf86-video-ati 6.12.4-3 mesa 7.7-1 ati-dri 7.7-1 * config and/or log files etc. Steps to reproduce: 
googleearth.png
(931.4 KiB)
|
This task depends upon
Closed by Andreas Radke (AndyRTR)
Monday, 03 May 2010, 16:47 GMT
Reason for closing: Works for me
Additional comments about closing: no response for months and many updates later it seems solved.
Monday, 03 May 2010, 16:47 GMT
Reason for closing: Works for me
Additional comments about closing: no response for months and many updates later it seems solved.
Since Google Earth causes the biggest problems I have tried running it to get the log files when the errors are happening. If I disable DRI google earth works fine ( but slow of course) without any errors shown in dmesg... Having DRI enabled seems to almost always crush critical memory ranges in RAM ( corrupted r/w cache of mounted file systems etc... ). If I should get googleearth to work before the filesystems stop working I get other memory corruption errors in dmesg if I continue to use the application.
I hope the log files are helping :D
https://bugs.freedesktop.org/show_bug.cgi?id=24414
The comments tell that the problems are caused by mesa 7.6.0... a downgrade seems to fix the problems... I need to try that to see if that also works for me...