From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051018 Epiphany/1.8.2
Description of problem:
After installing from the current rawhide tree, modular
X ist installed. There is no 3D acceleration although
the Savage chips seem to be supported now. According to
the X log file, everything should be fine:
"(II) SAVAGE(0): Direct rendering enabled".
However, even after rebuilding GL screensavers and "ppracer",
3D acceleration is clearly not available.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch some Open GL application.
Actual Results: 3D graphics is awfully slow.
Expected Results: 3D graphics should be accelerated.
Before reinstalling my system, I had used my hoembrewn,
monolithic Xorg 6.9RC1 RPMs. Here, 3D acceleration was
excellent even for the latest rawhide tree before the
move to modular X. It seems, that the Mesa tree is not
the right one. enabling verbose output, one obtains for
"ppracer" the following output:
[test]$ env LIBGL_DEBUG=verbose /usr/bin/ppracer
PPRacer 0.3.1 -- http://racer.planetpenguin.de
(c) 2004-2005 The PPRacer team
(c) 1999-2001 Jasmin F. Patry<email@example.com>
PPRacer comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to redistribute it under certain conditions.
See http://www.gnu.org/copyleft/gpl.html for details.
libGL: XF86DRIGetClientDriverName: 2.0.2 savage (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/savage_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/savage_dri.so failed (/usr/X11R6/lib/modules/dri/savage_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to find driver: savage_dri.so
Why does it still look for "/usr/X11R6/lib/modules/dri/savage_dri.so"?
Running "strings /usr/lib/libGL.so.1.2 | grep X11R6"
yields "/usr/X11R6/lib/modules/dri" which seems to confirm
my earlier conjecture.
A symlink from "/usr/lib/dri" to "/usr/X11R6/lib/modules/dri" for
testing purposes allows to recover hardware acceleration. This
confirms my previous guess of an internal "Mesa" build problem.
Fixed in -5