On Wed, 2001-11-14 at 13:41, Daniel Polombo wrote: > I am using the DRI on my Dell Latitude C800 with a Rage 128, and it has > been working very well for quite some time now. I have recently updated my > debian woody (weekly apt-get upgrade), though, and from then on, things > suddenly stopped working. I'm not sure which libs were upgraded, though, as it > was a rather heavy upgrade.
First make sure that both xserver-xfree86 and xlibmesa3 are the same versions, namely 4.1.0-x. > Initial (working) configuration : > - kernel 2.4.9-ac11 > - using the kernel's r128.o as a module > - debian woody (testing) > - XFree 4.1.0-7 > > To try and correct the problem, I upgraded first to a sid (debian unstable) to > get newer packages. This got my Xfree version to 4.1.0-9. Since this did no > good, I also upgraded the kernel to vanilla 2.4.14. Still no good. > > Direct rendering is enabled : > > $ glxinfo > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > > But if I try to run a 3D app : > > $ /usr/lib/xscreensaver/gears > drmR128Clear: return = -22 > > Strace'ing the stuff indicates the culprit might be an ioctl not recognized by > the driver : > > ioctl(4, 0x40146449, 0xbffff638) = -1 EINVAL (Invalid argument) > write(2, "drmR128Clear: return = -22\n", 27) = 27 > > And, lastly, the system logs the following error : > > [drm:r128_cce_vertex] *ERROR* process 16181 using buffer owned by 0 > > I would appreciate any kind of input on the subject, as this is very frustrating! My first guess would have been a wrong version of the kernel module, but the one from the 2.4.14 kernel should work. Could there be a stray libGL, e.g. in /usr/local, that gets picked up? You can check with ldd. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
