Bug 7108 - libGL error message is only printed with LIBGL_DEBUG=verbose
Summary: libGL error message is only printed with LIBGL_DEBUG=verbose
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 6.5
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-03 14:48 UTC by Andrei Slavoiu
Modified: 2006-06-06 09:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Andrei Slavoiu 2006-06-03 14:48:35 UTC 
Output of `glxinfo`:
name of display: :0.0
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
display: :0  screen: 0
direct rendering: No

Output of `LIBGL_DEBUG=verbose glxinfo`:
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 4.0.3 r300 (screen 0)
libGL: OpenDriver: trying /usr/lib64/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/r300_dri.so
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
libGL error:
R300 DRI driver expected DRM version 1.24.x but got version 1.22.0
libGL warning: 3D driver returned no fbconfigs.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
display: :0  screen: 0
direct rendering: No

The message I'm talking about is:
libGL error:
R300 DRI driver expected DRM version 1.24.x but got version 1.22.0
Comment 1 Roland Scheidegger 2006-06-06 09:14:02 UTC 
You're right it should be printed always. It is however already fixed in CVS
since some weeks.

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.