Bug 25876 - Direct Rendering Disabled Due to Undefined Symbols
Summary: Direct Rendering Disabled Due to Undefined Symbols
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/R100 (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-03 15:29 UTC by Tom Stellard
Modified: 2010-01-03 18:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Tom Stellard 2010-01-03 15:29:32 UTC 
I just built the latest version of mesa from git, commit: 	e388d62b4712bcd75cecad53f5ca20a2bb6f89b1

Direct rendering is disabled due to some undefined symbols, here is the debugging output from glxinfo:

libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: undefined symbol: _glthread_GetID)
libGL error: unable to load driver: r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so
libGL error: dlopen /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: undefined symbol: _glapi_check_multithread)
libGL error: unable to load driver: swrast_dri.so
libGL error: reverting to indirect rendering

I am using xorg-server version 1.7.3.901, kernel version 2.6.32, and the latest versions of libdrm and ddx.
Comment 1 Kristian Høgsberg 2010-01-03 18:04:19 UTC 
Should be fixed now, please give git master a try.

thanks,
Kristian
Comment 2 Tom Stellard 2010-01-03 18:46:50 UTC 
I just tried again with mesa master, commit: 	b8326b011d9b16dcc502507a52bd747a4b709399
I can confirm this bug has been fixed.
Comment 3 Kristian Høgsberg 2010-01-03 18:51:19 UTC 
Thanks, closing bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.