DRI (direct rendering) is still not working with the latest release of xf86-video-savage driver. The error returned when I run glxgears is now ... belgix@edinburgh ~ $ glxgears libGL error: drmMap of framebuffer failed (Invalid argument) libGL error: reverting to (slow) indirect rendering 770 frames in 5.5 seconds = 140.512 FPS 798 frames in 5.7 seconds = 141.141 FPS which seems an incompatibility between the new updated Savage driver and the current libGL library (from package mesa-6.5.1-r1) in the tree. To fix the DRI locking bug, we just need to apply the submitted patch to version 2.1.1 of the driver. belgix@edinburgh ~ $ glxgears 2388 frames in 5.0 seconds = 477.512 FPS 2628 frames in 5.0 seconds = 525.527 FPS
Created attachment 98407 [details] emerge --info
More likely an issue with the kernel module, the DRM. Could you try something newer?
Created attachment 98409 [details] Xorg log file with DRI enabled and working (with version 2.1.1) Video card is a SuperSavage/IXC 64.
Created attachment 98411 [details, diff] Patch to fix DRI locking problem for xf86-version-savage-2.1.1 Patch coming from upstream.
(In reply to comment #2) > More likely an issue with the kernel module, the DRM. Could you try something > newer? > Nice try but I am running Linux kernel 2.6.18 !!!
DRM source isn't the kernel, it just gets merged into there later ... I have a live git x11-drm ebuild in my overlay at http://dev.gentoo.org/~dberkholz/overlay/ that you could try. Be sure to delete the older kernel modules for radeon.ko and drm.ko in /lib/modules/..../char/drm/ before installing it to avoid weird issues.
(In reply to comment #6) > DRM source isn't the kernel, it just gets merged into there later ... I have a > live git x11-drm ebuild in my overlay at > http://dev.gentoo.org/~dberkholz/overlay/ that you could try. Be sure to delete > the older kernel modules for radeon.ko and drm.ko in > /lib/modules/..../char/drm/ before installing it to avoid weird issues. > Finally, I will stay with my patched version of xf86-video-savage-2.1.1 which DRI is working fine and manually mask =v.2.1.2 to avoid further update. Personnally I think too version 2.1.2 should be hard-masked in the Portage tree because it is not compatible with the current and available software for ~x86.
We need to determine what the actual problem is.
(In reply to comment #8) > We need to determine what the actual problem is. > I will do it. Time to learn which package I must install to access your git overlay.
Install layman, layman -a dberkholz That's perhaps the easiest way.
(In reply to comment #10) Damn, should I ebuild the package x11-base/x11-drm-99999999 in your overlay ? If yes, I must recompile my kernel with CONFIG_DRM=m first.
(In reply to comment #11) After emerging subversion, layman, rcs & git, ... reconfiguring & recompiling my kernel, ... rebooting, ... testing if DRI is still working with my patched xf86-video-savage-2.1.1, ... ebuilding and installing x11-base/x11-drm-99999999, ... rebooting again, ... testing again if DRI is working with my patched xf86-video-savage-2.1.1, ... emerging xf86-video-savage-2.1.2, ... and finally restarting X, IT'S WORKS! So, current vanilla-sources (and possibly others flavors in the Portage tree) should be upgraded to support xf86-video-savage-2.1.2. Thanks!
Thanks for testing, Francois. I really appreciate it. What we can do is provide a newer x11-drm snapshot and add a note to the savage ebuild that people must use it instead of kernels .18 and older to get direct rendering. Bryan, could you add a new x11-drm?
(In reply to comment #13) > > Bryan, could you add a new x11-drm? > Donnie, DRI + Savage cards works fine with x11-base/x11-drm-20060608 presently in the Portage tree. Kernel mates upstream are just sleeping ;-)
Oh, ok. Great, then. Upstream should be merging in for .19, I saw it was on the queue. I've just added a note to the ebuild.
