Changeset 2001b3e

Timestamp:

04/08/2012 09:22:47 PM (12 years ago)

Author:

Ken Moffat <ken@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

7114aa56

Parents:

1464543

Message:

Reinstate some of the DRI explanation, expanded to mention DRI2 hardware video acceleration.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@9881 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:

• general/graphlib/clutter.xml (modified) (1 diff)
• gnome/add/totem.xml (modified) (1 diff)
• gnome/core/metacity.xml (modified) (1 diff)
• gnome/core/mutter.xml (modified) (1 diff)
• introduction/welcome/changelog.xml (modified) (1 diff)
• x/installing/xorg-config.xml (modified) (1 diff)

general/graphlib/clutter.xml

@@ -35 +35 @@
 
   <note>
-    <para>Anything built with this toolkit needs accelerated 3D support from the
-    graphics driver at runtime.  If you use <application>GNOME-3</application> and
-    it selects the <emphasis>fallback</emphasis> window manager
+    <para>Anything built with this toolkit needs hardware 3D acceleration from the
+    graphics driver at runtime.  This is provided by <application>MesaLib</application>
+    (or by proprietary graphics drivers), but is not available for every graphics card,
+    nor for all virtual machines). You may wish to review <xref linkend="checking-dri"/>.
+    </para>
+
+    <para>If you use <application>GNOME-3</application> and it selects the
+    <emphasis>fallback</emphasis> window manager
     (<application>metacity</application>) you should treat this package as a build
     dependency and expect unsatisfactory runtime performance from other
-    <application>clutter</application> packages, particularly
+    <application>clutter</application> packages such as
     <application>totem</application>.</para>
   </note>
 
-    &lfs70_built;
+    &lfs70_checked;
 
     <bridgehead renderas="sect3">Package Information</bridgehead>

gnome/add/totem.xml

@@ -38 +38 @@
 
     <para>Now that this package uses the <application>clutter</application> toolkit,
-    it is only useful if you have accelerated video.</para>
+    it is only useful if you have hardware accelerated video.</para>
 
     &lfs70_checked;

gnome/core/metacity.xml

@@ -33 +33 @@
     <para><application>Metacity</application> is the fallback window manager for
     <application>GNOME</application>, used if the video driver does not provide
-    acceleration. It is conventionally run from <command>gnome-session</command>,
+    hardware acceleration. It is conventionally run from <command>gnome-session</command>,
     which will start the necessary <application>GNOME</application> daemons.</para>
 

gnome/core/mutter.xml

@@ -32 +32 @@
     <para><application>Mutter</application> is the window manager for
     <application>GNOME</application>. It is not invoked directly, but from
-    <application>gnome-session</application> (on a machine with an accelerated
-    video driver).</para>
+    <application>gnome-session</application> (on a machine with a hardware
+    accelerated video driver).</para>
 
     &lfs70_checked;

introduction/welcome/changelog.xml

@@ -48 +48 @@
           <para>[rthomsen] - Corrected Qt configuration. Thanks to Pierre Labastie for the report.</para>
         </listitem>
+        <listitem>
+          <para>[ken] - reinstate some of the notes on DRI, particularly re the
+          'video' group, and expand to cover DRI2 hardware video acceleration.  Tweak
+          certain gnome comments to show that it is hardware acceleration which is
+          required.</para>
+        </listitem>
       </itemizedlist>
     </listitem>

x/installing/xorg-config.xml

@@ -33 +33 @@
     </sect2>
 
+    <sect2 role="configuration" id='checking-dri' xreflabel="Checking the DRI installation">
+    <title>Checking the Direct Rendering Infrastructure (DRI) Installation</title>
+
+    <para>DRI is a framework for allowing software to access graphics hardware
+    in a safe and efficient manner. It is installed in <application>X</application>
+    by default (using <application>MesaLib</application>) if you have a supported
+    video card.</para>
+
+    <para>To check if DRI is installed properly, check the log file
+    <filename>/var/log/Xorg.0.log</filename> for statements like:</para>
+
+<screen><literal>(II) R128(0): Direct rendering enabled</literal></screen>
+
+    <note><para>DRI configuration may differ if you are using alternate
+    drivers, such as those from
+    <ulink url="http://www.nvidia.com/page/home.html">NVIDIA</ulink> or
+    <ulink url="http://www.ati.com/">ATI</ulink>.</para>
+    </note>
+
+    <para>Although all users can use software acceleration, any hardware
+    acceleration (DRI2) is only available to
+    <systemitem class="username">root</systemitem> and members of the
+    <systemitem class="groupname">video</systemitem> group.</para>
+
+    <para>To see if hardware acceleration is available for your driver, look in
+    <filename>/var/log/Xorg.0.log</filename> for statements like:</para>
+
+<screen><literal> (II) intel(0): direct rendering: DRI2 Enabled</literal></screen>
+
+    <para>If your driver is supported, add any users that might use X to that group:</para>
+
+<screen role="root"><userinput>usermod -a -G video <replaceable>&lt;username&gt;</replaceable></userinput></screen>
+
+    <para>If you elected to install the Mesa-Demos package when installing
+    <xref linkend="mesalib"/>, from an <command>xterm</command>, run
+    <command>glxinfo</command> and first look for the phrase:</para>
+
+<screen><computeroutput>direct rendering: Yes</computeroutput></screen>
+
+    <para>If direct rendering is enabled, you can add verbosity by
+    running <command>LIBGL_DEBUG=verbose glxinfo</command>.  This will
+    show the drivers, device nodes and files used by the DRI system.</para>
+
+    <para>If DRI is enabled, to confirm that DRI2 hardware acceleration is
+    working you can (still in the <command>xterm</command>) run the command
+    <command>glxinfo | grep "OpenGL renderer string"</command> - if that
+    reports something <emphasis>other than</emphasis>
+    <literal>Software Rasterizer</literal> then you have working acceleration
+    for the user who ran the command.</para>
+
+    <para>Again, if you have added the Mesa-Demos package, you can also
+    run the test program <command>glxgears</command>.
+    This program brings up a window with three gears turning.  The
+    <command>xterm</command> will display how many frames were drawn every
+    five seconds, so this is a reasonable benchmark.  The window is scalable,
+    and the frames drawn per second is highly dependent on the size of
+    the window.</para>
+
+    </sect2>
+
     <sect2 role="configuration" id='X11R6-compat-symlink'
          xreflabel="Creating an X11R6 Compatibility Symlink">