From: Michel <mic...@ii...> - 2001-11-19 00:05:21
|
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 ha= s=20 > been working very well for quite some time now. I have recently updated m= y=20 > debian woody (weekly apt-get upgrade), though, and from then on, things=20 > suddenly stopped working. I'm not sure which libs were upgraded, though, = as it=20 > 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 >=20 > To try and correct the problem, I upgraded first to a sid (debian unstabl= e) to=20 > get newer packages. This got my Xfree version to 4.1.0-9. Since this did = no=20 > good, I also upgraded the kernel to vanilla 2.4.14. Still no good. >=20 > Direct rendering is enabled : >=20 > $ glxinfo > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes >=20 > But if I try to run a 3D app : >=20 > $ /usr/lib/xscreensaver/gears > drmR128Clear: return =3D -22 >=20 > Strace'ing the stuff indicates the culprit might be an ioctl not recogniz= ed by=20 > the driver : >=20 > ioctl(4, 0x40146449, 0xbffff638) =3D -1 EINVAL (Invalid argument= ) > write(2, "drmR128Clear: return =3D -22\n", 27) =3D 27 >=20 > And, lastly, the system logs the following error : >=20 > [drm:r128_cce_vertex] *ERROR* process 16181 using buffer owned by 0 >=20 > I would appreciate any kind of input on the subject, as this is very frus= trating! 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. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |