X Strike Force XFree86 SVN commit: r2197 - in trunk/debian: . local
Author: branden
Date: 2005-02-18 13:42:45 -0500 (Fri, 18 Feb 2005)
New Revision: 2197
Modified:
trunk/debian/CHANGESETS
trunk/debian/changelog
trunk/debian/local/FAQ.xhtml
Log:
Update FAQ entry "How can I help debug 3D acceleration problems?" per
feedback from Michel D?\195?\164nzer.
Modified: trunk/debian/CHANGESETS
===================================================================
--- trunk/debian/CHANGESETS 2005-02-18 17:55:37 UTC (rev 2196)
+++ trunk/debian/CHANGESETS 2005-02-18 18:42:45 UTC (rev 2197)
@@ -24,4 +24,8 @@
Tollef Fog Heen for bringing this to my attention.
2196
+Update FAQ entry "How can I help debug 3D acceleration problems?" per
+feedback from Michel Dänzer.
+ 2197
+
vim:set ai et sts=4 sw=4 tw=80:
Modified: trunk/debian/changelog
===================================================================
--- trunk/debian/changelog 2005-02-18 17:55:37 UTC (rev 2196)
+++ trunk/debian/changelog 2005-02-18 18:42:45 UTC (rev 2197)
@@ -16,8 +16,11 @@
* Fix missing .HP tag in XGetWindowProperty() (et al.) manpage. Thanks to
Tollef Fog Heen for bringing this to my attention.
- -- Branden Robinson <branden@debian.org> Fri, 18 Feb 2005 12:49:00 -0500
+ * Update FAQ entry "How can I help debug 3D acceleration problems?" per
+ feedback from Michel Dänzer.
+ -- Branden Robinson <branden@debian.org> Fri, 18 Feb 2005 13:39:21 -0500
+
xfree86 (4.3.0.dfsg.1-11) unstable; urgency=medium
* Urgency set to medium due to fix for release-critical bug #286181
Modified: trunk/debian/local/FAQ.xhtml
===================================================================
--- trunk/debian/local/FAQ.xhtml 2005-02-18 17:55:37 UTC (rev 2196)
+++ trunk/debian/local/FAQ.xhtml 2005-02-18 18:42:45 UTC (rev 2197)
@@ -3430,15 +3430,24 @@
<ol>
<li>
- <p>Try to reproduce the problem by running the troublesome application from
- a shell prompt in a terminal window with the following environment variables
- set:</p>
- <pre>LIBGL_ALWAYS_INDIRECT=1; export LIBGL_ALWAYS_INDIRECT
-LIBGL_DEBUG=verbose; export LIBGL_DEBUG</pre>
- <p>Setting <code class="other">LIBGL_DEBUG=verbose</code> helps to ensure
- that indirect rendering is actually being used. Note that if it is, there
- will <em>not</em> be any special output, whereas if it's not (that is, if
- DRI is being used), you will see output like:</p>
+ <p>First, try to reproduce the problem by running the troublesome
+ application from a shell prompt in a terminal window with the following
+ environment variable set:</p>
+ <pre>LIBGL_DEBUG=verbose; export LIBGL_DEBUG</pre>
+ <p>If the problem is not reproducible, it is probably too soon to file a bug
+ report. Ask for assistance on the <a
+ href="http://lists.debian.org/debian-user/";><code
+ class="other">debian-user</code> mailing list</a>.</p>
+ </li>
+ <li>
+ <p>Next, to reproduce the problem as above with an additional environment
+ variable set:</p>
+ <pre>LIBGL_ALWAYS_INDIRECT=1; export LIBGL_ALWAYS_INDIRECT</pre>
+ <p>With <code class="other">LIBGL_DEBUG=verbose</code> already set and
+ exported, we can determine whether indirect rendering is actually being
+ used. Note that if it is, there will <em>not</em> be any special output,
+ whereas if it's not (that is, if DRI is being used), you will see output
+ like:</p>
<pre>libGL: XF86DRIGetClientDriverName: 4.0.1 r200 (screen 0)
libGL: OpenDriver:
trying /home/michdaen/src/mesa-cvs/Mesa/lib/r200_dri.so
@@ -3447,37 +3456,38 @@
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0</pre>
- <p>If the problem is reproducible with indirect rendering, then there is
- likely a problem with the GL library itself. Use the command <kbd>dpkg -S
- /usr/lib/libGL.so.1</kbd> to determine which package provides your GL
- library, and file a bug report against it (or skip the middleman and use
- <kbd>reportbug --file /usr/lib/libGL.so.1</kbd>).</p>
+ <p>If the problem <em>is</em> reproducible with indirect rendering, then
+ there is likely a problem with the OpenGL/GLX implementation in the X server
+ — most likely, in the Mesa code shared between the X server and the
+ DRI 3D drivers.</p>
+ <p>The problem could also be in the underlying GL library on the
+ system, however; if you have reason to suspect this is the case, use the
+ command <kbd>dpkg -S /usr/lib/libGL.so.1</kbd> to determine which package
+ provides your GL library, and file a bug report against it (or skip the
+ middleman and use <kbd>reportbug --file /usr/lib/libGL.so.1</kbd>).</p>
<p>On the other hand, if the problem goes away when indirect rendering is
used, then one of the following is at fault:</p>
<ul>
- <li>the hardware-neutral parts of DRI</li>
+ <li>the X server's portions of DRI</li>
<li>the Mesa DRI module for your display adapter</li>
- <li>the Linux DRM module for your display adapter</li>
+ <li>the Linux DRM (Direct Rendering Manager) module for your display
+ adapter</li>
<li>your display adapter (i.e., a hardware bug that either Mesa or Linux
should try to work around, if possible)</li>
</ul>
</li>
<li>
- <p>To rule out problems with the hardware-neutral parts of DRI, remove the
- <code class="package">xlibmesa-dri</code> package if it is installed, and
- disable the <code class="other">Load "dri"</code> line in your <code
+ <p>To rule out problems with the X server's portions of DRI, disable the
+ <code class="other">Load "dri"</code> line in your <code
class="filespec">/etc/X11/XF86Config-4</code> file. There are two ways to
- do the latter; you can run <kbd>dpkg-reconfigure xserver-xfree86</kbd> and
- remove <code class="other">dri</code> from the list of modules to be loaded,
- or you can simply open <code class="filespec">/etc/X11/XF86Config-4</code>
- with your favorite text editor and comment the line out by putting a hash
- mark (<kbd>#</kbd>) at the beginning of it.</p>
- <p>If doing the above resolves the problem but the previous step did not,
- you have found a problem in the hardware-neutral part of DRI; file a bug
- against <code class="package">xserver-xfree86</code> and report your
- findings.</p>
- <p>You can of course reinstall the <code class="package">xlibmesa-dri</code>
- package if you removed it, and if you so desire.</p>
+ do this; you can run <kbd>dpkg-reconfigure xserver-xfree86</kbd> and remove
+ <code class="other">dri</code> from the list of modules to be loaded, or you
+ can simply open <code class="filespec">/etc/X11/XF86Config-4</code> with
+ your favorite text editor and comment the line out by putting a hash mark
+ (<kbd>#</kbd>) at the beginning of it.</p> <p>If doing the above resolves
+ the problem but the previous step did not, you have found a problem in the X
+ server's portions of DRI; file a bug against <code
+ class="package">xserver-xfree86</code> and report your findings.</p>
</li>
<li>
<p>Occassionally people find that problems with 3D acceleration appear and
Reply to: