Bug 82039 – xorg-x11-6.8.2 breaks direct rendering: r128_dri.so: undefined symbol: WRITE_DEPTH

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Zach Keene 2005-02-14 13:30:55 UTC]

I have an ATI All-in-wonder 128 (a Rage 128 card), and had direct rendering working with previous X installations (both Xfree and Xorg). Emerging xorg-x11 6.8.2 seems to have broken dri, however.

My Xorg.0.log shows nothing amiss (even claiming DRI to be enabled), however this is the first few lines of my glxinfo results (with LIBGL_DEBUG=verbose):

name of display: :0.0
libGL: XF86DRIGetClientDriverName: 4.0.1 r128 (screen 0)
libGL: OpenDriver: trying /usr/lib/modules/dri/r128_dri.so
libGL error: dlopen /usr/lib/modules/dri/r128_dri.so failed (/usr/lib/modules/dri/r128_dri.so: undefined symbol: WRITE_DEPTH)
libGL error: unable to find driver: r128_dri.so
display: :0  screen: 0
direct rendering: No

I've included a URL to a FreeBSD mailing list thread where someone was having the same problem (and apparently found a fix in mesa CVS...)

Reproducible: Always
Steps to Reproduce:
1. Emerge x11-base/xorg-x11-6.8.2 with ATI r128 card

Actual Results:  
Direct rendering broke

Expected Results:  
Not broken direct rendering. :)

[Comment 1 Donnie Berkholz (RETIRED) 2005-02-14 15:44:55 UTC]

So if you unpack xorg-x11 and apply the small patch at http://cvs.freedesktop.org/mesa/Mesa/src/mesa/drivers/dri/common/depthtmp.h?r1=1.4&r2=1.5 -- does it work?

You can find mesa in the xorg-x11 source at xc/extras/Mesa/.

[Comment 2 Zach Keene 2005-02-14 20:56:49 UTC]

Yep, applying that patch and recompiling seems to have solved the problem.

[Comment 3 Donnie Berkholz (RETIRED) 2005-02-14 23:56:12 UTC]

By "seems to have solved," do you mean, "I now have direct rendering"?

[Comment 4 Zach Keene 2005-02-15 05:24:57 UTC]

Yes.

[Comment 5 PL Hayes 2005-03-14 05:02:32 UTC]

I have a similar problem having just emerged 6.8.2: Xorg.0.log says direct rendering is enabled, glxinfo says it isn't (and glxgears is so slow I'd guess glxinfo was right) - but I don't get any of the libGL error messages. Could this be the same bug? I have USE +dlloader if that makes a difference. 

[Comment 6 Donnie Berkholz (RETIRED) 2005-03-14 13:01:09 UTC]

If you want to know whether it's the same bug, try the patch. Clearly if it fixes your problem, it's the same.

`LIBGL_DEBUG=verbose glxinfo` will tell you whether you're hitting this bug. If you don't get those messages, it's a different bug (or not a bug at all but rather a configuration problem).

[Comment 7 Enderson Tadeu S. Maia (RETIRED) 2005-03-28 06:31:59 UTC]

I had problems that the machine just didn't respond after I start some
games lioke Quake3, and if I swithing from tty1 (Ctrl+Alt+1) to X (Ctrl+Alt+7).

The patch solved my problem.

[Comment 8 Donnie Berkholz (RETIRED) 2005-04-14 16:41:28 UTC]

Should be fixed in 6.8.2-r2.

[Comment 9 PL Hayes 2005-04-24 20:15:13 UTC]

Yes - manually applying the patch was a bit too much for me at the moment but 6.8.2-r2 has fixed it. Thanks.