[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#379323: marked as done (mesa-utils: glxinfo does not report library open problems)

Your message dated Mon, 21 May 2007 20:19:50 +0200
with message-id <4651E2C6.3080004@ens-lyon.org>
and subject line Bug#379323: mesa-utils: glxinfo does not report library open problems
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: mesa-utils
Version: 6.3.2-2.1
Severity: important


I unfortunately just spent hours of debugging trying to find why I wasn't
getting accelerated GL after installing 3D drivers, and having the right
/usr/lib/libGL.so.1 and friends.

I would have killed for having glxinfo tell me what the problem was until
I found out a day later about LIBGL_DEBUG=verbose glxinfo, which then
gave me:
gandalf:~$ LIBGL_DEBUG=verbose glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 8.26.18 fglrx (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/fglrx_dri.so
libGL error: dlopen /usr/X11R6/lib/modules/dri/fglrx_dri.so failed (/usr/X11R6/l
ib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or dir
ectory)
libGL error: unable to find driver: fglrx_dri.so

This was due to a packaging bug, which I fixed with a simple symlink in about
30 seconds, but I would really really have liked for glxinfo to tell me that
it couldn't open the driver and that's why I was still getting Mesa.
Please consider making LIBGL_DEBUG=verbose or equivalent, a default to help
out the countless people on the net like me who have spent too much time
tracking this problem.

I'm adding extra un-needed info so that google indexes it, and that
hopefully other people can find this instead of spending the time I spent.
With fglrx (fglrx-driver), and xorg 7.0.22, the driver was loading, dri was
initializing, but glxinfo would tell me:
gandalf:~$ glxinfo | grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

After ln -s /usr/lib /usr/X11R6/lib/modules, it allowed libGL to find
/usr/X11R6/lib/modules/dri/fglrx_dri.so which really had been installed
in /usr/lib/dri/fglrx_dri.so

Now, I do get:
gandalf:~$ glxinfo | grep -E '(direct|renderer)'
direct rendering: Yes
OpenGL renderer string: MOBILITY FIREGL T2 Pentium 4 (SSE2) (FireGL) (GNU_ICD)

Thanks
Marc


-- System Information:
Debian Release: woody
  APT prefers unstable
  APT policy: (900, 'unstable'), (500, 'oldstable'), (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.6-pmup-desktop-marc1y
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO-8859-15)

Versions of packages mesa-utils depends on:
di  freeglut3                 2.4.0-4        OpenGL Utility Toolkit
ii  libc6                     2.3.6-15       GNU C Library: Shared libraries
pi  libgl1-mesa-glx [libgl1]  6.4.2-1        A free implementation of the OpenG
pi  libglu1-mesa [libglu1]    6.4.2-1        The OpenGL utility library (GLU)
ii  libx11-6                  6.9.0.dfsg.1-1 X Window System protocol client li

mesa-utils recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 6.5.3-1

Mesa 6.5.3 (currently in experimental) reports:
$ glxinfo
name of display: :0.0
libGL error: open DRM failed (Operation not permitted)
libGL error: reverting to (slow) indirect rendering
display: :0  screen: 0
direct rendering: No (If you want to find out why, try setting
LIBGL_DEBUG=verbose)

--- End Message ---
Reply to: