5244 – glxinfo reports no Direct Rendering although X logs say the opposite

Bug 5244 - glxinfo reports no Direct Rendering although X logs say the opposite

Summary: glxinfo reports no Direct Rendering although X logs say the opposite

Status:	RESOLVED FIXED

Alias:	None

Product:	Mesa
Classification:	Unclassified
Component:	Drivers/DRI/r300 (show other bugs)
Version:	unspecified
Hardware:	x86 (IA32) Linux (All)

Importance:	high normal
Assignee:	Default DRI bug account
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-12-05 04:12 UTC by Diego
Modified:	2005-12-04 11:46 UTC (History)
CC List:	0 users

See Also:
i915 platform:
i915 features:

Attachments
X Server log (19.64 KB, text/plain) 2005-12-05 04:13 UTC, Diego	Details
glxinfo output (4.47 KB, text/plain) 2005-12-05 04:14 UTC, Diego	Details
Part of the kernel logs that makes any reference to DRM (403 bytes, text/plain) 2005-12-05 04:16 UTC, Diego	Details
View All

Description Diego 2005-12-05 04:12:24 UTC

I have libdrm, drm kernel driver, Mesa and Mesa r300 driver compiled from CVS as
of 3rd of december. I'm using an X.org modular build from today (4th).

I'm running on a Dell610 with ATI radeon M300. The logs of the Xserver, the
kernel and the glxinfo output are attached

Comment 1 Diego 2005-12-05 04:13:41 UTC

Created attachment 3992 [details]
X Server log

Comment 2 Diego 2005-12-05 04:14:16 UTC

Created attachment 3993 [details]
glxinfo output

Comment 3 Diego 2005-12-05 04:16:25 UTC

Created attachment 3994 [details]
Part of the kernel logs that makes any reference to DRM

Comment 4 Diego 2005-12-05 04:21:13 UTC

I almost forget, it is an PCI Express card, i'm running kernel 2.6.15-rc4

Comment 5 Michel Dänzer 2005-12-05 04:22:30 UTC

Please attach the output of

LIBGL_DEBUG=verbose glxinfo

Comment 6 Diego 2005-12-05 06:46:23 UTC

ok, fixed, the problem was that libGL was not finding the r300_dri module. 

BTW what performance should i expect when running glxgears for example?

Thank you very much.

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.