Changeset 2001b3e for x


Ignore:
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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • x/installing/xorg-config.xml

    r1464543 r2001b3e  
    3333    </sect2>
    3434
     35    <sect2 role="configuration" id='checking-dri' xreflabel="Checking the DRI installation">
     36    <title>Checking the Direct Rendering Infrastructure (DRI) Installation</title>
     37
     38    <para>DRI is a framework for allowing software to access graphics hardware
     39    in a safe and efficient manner. It is installed in <application>X</application>
     40    by default (using <application>MesaLib</application>) if you have a supported
     41    video card.</para>
     42
     43    <para>To check if DRI is installed properly, check the log file
     44    <filename>/var/log/Xorg.0.log</filename> for statements like:</para>
     45
     46<screen><literal>(II) R128(0): Direct rendering enabled</literal></screen>
     47
     48    <note><para>DRI configuration may differ if you are using alternate
     49    drivers, such as those from
     50    <ulink url="http://www.nvidia.com/page/home.html">NVIDIA</ulink> or
     51    <ulink url="http://www.ati.com/">ATI</ulink>.</para>
     52    </note>
     53
     54    <para>Although all users can use software acceleration, any hardware
     55    acceleration (DRI2) is only available to
     56    <systemitem class="username">root</systemitem> and members of the
     57    <systemitem class="groupname">video</systemitem> group.</para>
     58
     59    <para>To see if hardware acceleration is available for your driver, look in
     60    <filename>/var/log/Xorg.0.log</filename> for statements like:</para>
     61
     62<screen><literal> (II) intel(0): direct rendering: DRI2 Enabled</literal></screen>
     63
     64    <para>If your driver is supported, add any users that might use X to that group:</para>
     65
     66<screen role="root"><userinput>usermod -a -G video <replaceable>&lt;username&gt;</replaceable></userinput></screen>
     67
     68    <para>If you elected to install the Mesa-Demos package when installing
     69    <xref linkend="mesalib"/>, from an <command>xterm</command>, run
     70    <command>glxinfo</command> and first look for the phrase:</para>
     71
     72<screen><computeroutput>direct rendering: Yes</computeroutput></screen>
     73
     74    <para>If direct rendering is enabled, you can add verbosity by
     75    running <command>LIBGL_DEBUG=verbose glxinfo</command>.  This will
     76    show the drivers, device nodes and files used by the DRI system.</para>
     77
     78    <para>If DRI is enabled, to confirm that DRI2 hardware acceleration is
     79    working you can (still in the <command>xterm</command>) run the command
     80    <command>glxinfo | grep "OpenGL renderer string"</command> - if that
     81    reports something <emphasis>other than</emphasis>
     82    <literal>Software Rasterizer</literal> then you have working acceleration
     83    for the user who ran the command.</para>
     84
     85    <para>Again, if you have added the Mesa-Demos package, you can also
     86    run the test program <command>glxgears</command>.
     87    This program brings up a window with three gears turning.  The
     88    <command>xterm</command> will display how many frames were drawn every
     89    five seconds, so this is a reasonable benchmark.  The window is scalable,
     90    and the frames drawn per second is highly dependent on the size of
     91    the window.</para>
     92
     93    </sect2>
     94
    3595    <sect2 role="configuration" id='X11R6-compat-symlink'
    3696         xreflabel="Creating an X11R6 Compatibility Symlink">
Note: See TracChangeset for help on using the changeset viewer.