Changeset c96921c


Ignore:
Timestamp:
03/08/2013 03:49:03 AM (11 years ago)
Author:
Bruce Dubbs <bdubbs@…>
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:
5fb5a6cd
Parents:
a153d42
Message:

Correct some font links.
Reword DRI description.
Do some general reformatting.

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

Files:
4 edited

Legend:

Unmodified
Added
Removed

  • general.ent

    ra153d42 rc96921c  
    55
    66<!ENTITY day          "04">                   <!-- Always 2 digits -->
    7 <!ENTITY month        "06">                   <!-- Always 2 digits -->
     7<!ENTITY month        "07">                   <!-- Always 2 digits -->
    88<!ENTITY year         "2013">
    99<!ENTITY copyrightdate "2001-&year;">
    1010<!ENTITY copyholder   "The BLFS Development Team">
    1111<!ENTITY version      "&year;-&month;-&day;">
    12 <!ENTITY releasedate  "March 6th, &year;">
     12<!ENTITY releasedate  "March 7th, &year;">
    1313<!ENTITY pubdate      "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
    1414<!ENTITY blfs-version "svn">                  <!-- svn|[release #] -->

  • introduction/welcome/changelog.xml

    ra153d42 rc96921c  
    4545-->
    4646    <listitem>
     47      <para>March 7th, 2013</para>
     48      <itemizedlist>
     49        <listitem>
     50          <para>[bdubbs] - Fix link to Chineese fonts.  Fixes
     51          <ulink url="&blfs-ticket-root;3821">#3821</ulink>.</para>
     52        </listitem>
     53        <listitem>
     54          <para>[bdubbs] - Update wording of DRI detection in Xorg
     55          configuration.</para>
     56        </listitem>
     57      </itemizedlist>
     58    </listitem>
     59
     60    <listitem>
    4761      <para>March 6th, 2013</para>
    4862      <itemizedlist>

  • postlfs/security/openssl.xml

    ra153d42 rc96921c  
    108108
    109109<screen><userinput>patch -Np1 -i ../openssl-&openssl-version;-fix_manpages-1.patch &amp;&amp;
    110 ./config --prefix=/usr --openssldir=/etc/ssl shared zlib-dynamic &amp;&amp;
     110
     111./config --prefix=/usr         \
     112         --openssldir=/etc/ssl \
     113         shared                \
     114         zlib-dynamic &amp;&amp;
    111115make</userinput></screen>
    112116

  • x/installing/xorg-config.xml

    ra153d42 rc96921c  
    4848    <para>
    4949      To check if DRI drivers are installed properly, check the log file
    50       <filename>/var/log/Xorg.0.log</filename> for statements like:
     50      <filename>/var/log/Xorg.0.log</filename> for statements such as:
    5151    </para>
    5252
    5353<screen><literal>(II) intel(0): direct rendering: DRI2 Enabled</literal></screen>
     54
     55    <para>or</para>
     56
     57<screen><literal>(II) NOUVEAU(0): Loaded DRI module</literal></screen>
    5458
    5559    <note>
    … …  
    6771      of the <systemitem class="groupname">video</systemitem> group.
    6872    </para>
    69 
     73<!--
    7074    <para>
    7175      To see if hardware acceleration is available for your driver, look in
    … …  
    7478
    7579<screen><literal>(II) intel(0): direct rendering: DRI2 Enabled</literal></screen>
    76 
     80-->
    7781    <para>
    7882      If your driver is supported, add any users that might use X to that group:
    … …  
    8286
    8387    <para>
    84       If you have installed two OpenGL demo programs when you installed
    85       <xref linkend="mesalib"/>, from an X terminal, run <command>glxinfo</command>
     88      Another way to determine if DRI is working properly is to use one of the
     89      two optionally installed OpenGL demo programs in <xref
     90      linkend="mesalib"/>. From an X terminal, run <command>glxinfo</command>
    8691      and look for the phrase:
    8792    </para>
    … …  
    98103
    99104    <para>
    100       If DRI2 is enabled, to confirm that DRI2 hardware acceleration is working you can
    101       (still in the X terminal) run the command
    102       <command>glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)"</command>
    103       - if that reports something <emphasis>other than</emphasis>
    104       <literal>Software Rasterizer</literal> then you have working acceleration for the
    105       user who ran the command.
    106     </para>
    107 
    108     <para>
    109       If your hardware does not have any DRI2 driver available, it will use Software Rasterizer
    110       for Direct Rendering. In such cases, it is recommended that you use new, LLVM-accelerated,
    111       Software Rasterizer called LLVMPipe. In order to build LLVMPipe just make sure that
    112       <xref linkend="llvm"/> is present at MesaLib build time. Please note that all decoding is
    113       done on CPU instead of GPU, so expect that things run slower. To check if you are using
    114       LLVMpipe, run
    115       <command>glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)"</command>.
    116       An example output is shown below:
     105      To confirm that DRI2 hardware acceleration is working, you can (still in
     106      the X terminal) run the command <command>glxinfo | egrep "(OpenGL
     107      vendor|OpenGL renderer|OpenGL version)"</command>.
     108      If that reports something <emphasis>other than</emphasis>
     109      <literal>Software Rasterizer</literal> then you have working
     110      acceleration for the user who ran the command.
     111    </para>
     112
     113    <para>
     114      If your hardware does not have any DRI2 driver available, it will use a
     115      Software Rasterizer for Direct Rendering. In such cases, you can use a new,
     116      LLVM-accelerated, Software Rasterizer called LLVMPipe. In order to build
     117      LLVMPipe just make sure that <xref linkend="llvm"/> is present at MesaLib
     118      build time. Note that all decoding is done on the CPU instead of the GPU,
     119      so the display will run slower than with hardware acceleration. 
     120      To check if you are using LLVMpipe,
     121      review the output ot the glxinfo command above.  An example of the
     122      output using the Software Rasterizer is shown below:
    117123    </para>
    118124
    … …  
    122128
    123129    <para>
    124       You can always force LLVMPipe by exporting <envar>LIBGL_ALWAYS_SOFTWARE=1</envar>
    125       environment variable.
    126     </para>
    127 
    128     <para>
    129       Again, if you have built Mesa OpenGL demos, you can also run the test program
    130       <command>glxgears</command>. This program brings up a window with three gears
    131       turning. The X terminal will display how many frames were drawn every five
    132       seconds, so this is a reasonable benchmark. The window is scalable, and the
    133       frames drawn per second is highly dependent on the size of the window. On some
    134       hardware, <command>glxgears</command> will run synchronized to vertical refresh
    135       and framerate will be approximately the same as the monitor refresh rate.
     130      You can also force LLVMPipe by exporting the <envar>LIBGL_ALWAYS_SOFTWARE=1</envar>
     131      environment variable when starting Xorg.
     132    </para>
     133
     134    <para>
     135      Again, if you have built the Mesa OpenGL demos, you can also run the test
     136      program <command>glxgears</command>. This program brings up a window with
     137      three gears turning. The X terminal will display how many frames were
     138      drawn every five seconds, so this will give a rough benchmark. The window
     139      is scalable, and the frames drawn per second is highly dependent on the
     140      size of the window. On some hardware, <command>glxgears</command> will
     141      run synchronized with the vertical refresh signal and the frame rate will
     142      be approximately the same as the monitor refresh rate.
    136143    </para>
    137144
    … …  
    151158      In order to use PRIME for GPU switching, make sure that you are using Linux
    152159      Kernel 3.4 or later (recommended). You will need latest DRI and DDX drivers
    153       for your hardware and <application>Xorg Server</application> 1.13 with an
    154       optional patch applied.
     160      for your hardware and <application>Xorg Server</application> 1.13 or later
     161      with an optional patch applied.
    155162    </para>
    156163
    … …  
    158165      <application>Xorg Server</application> should load both GPU drivers automaticaly.
    159166      In order to run a GLX application on a discrete GPU, you will need to export
    160       <envar>DRI_PRIME=1</envar> environment variable. For example,
     167      the <envar>DRI_PRIME=1</envar> environment variable. For example,
    161168
    162169<screen><userinput>DRI_PRIME=1 glxinfo | egrep "(OpenGL vendor|OpenGL renderer|OpenGL version)"</userinput></screen>
    … …  
    166173
    167174    <para>
    168       If the last command reports same OpenGL renderer with and without <envar>DRI_PRIME=1</envar>,
    169       you will need to check your installation.
     175      If the last command reports same OpenGL renderer with and without
     176      <envar>DRI_PRIME=1</envar>, you will need to check your installation.
    170177    </para>
    171178
    172179    </sect2>
    173 
    174 <!--
    175     <sect2 role="configuration" id='X11R6-compat-symlink'
    176          xreflabel="Creating an X11R6 Compatibility Symlink">
    177 
    178     <title>Creating an X11R6 Compatibility Symlink</title>
    179 
    180     <para>Until recently (relatively speaking) almost every
    181     <application>X Window</application> installation you performed or came
    182     across was installed in the
    183     <filename class='directory'>/usr/X11R6</filename> directory. That was the
    184     standard for years. Developers picked up on this and wrote their package
    185     installation scripts looking for <application>X</application> in the
    186     standard location. Things have changed and the trend is to now install
    187     <application>X</application> in
    188     <filename class='directory'>/usr</filename>. Some people want to install
    189     it in a custom location.</para>
    190 
    191     <para>Many package developers have not caught up to the change and their
    192     packages are still trying to find <application>X</application> in
    193     <filename class='directory'>/usr/X11R6</filename> and subsequently fail
    194     when you try to build the package. Though for most packages it is not
    195     difficult to 'hack' the installation script to fix the problem, that is not
    196     the long term solution to the problem. Upstream developers need to modernize
    197     their installation scripts and eliminate the problem altogether.</para>
    198 
    199     <para>Until then, you can create a symbolic link to satisfy the
    200     <filename class='directory'>/usr/X11R6</filename> requirement so that you
    201     won't be inconvenienced with a package build failure due to this known
    202     issue. If you wish to create the symlink, issue the following command as
    203     the <systemitem class="username">root</systemitem>:</para>
    204 
    205 <screen role="root"><userinput>ln -vsf $XORG_PREFIX /usr/X11R6</userinput></screen>
    206 
    207     </sect2>
    208 -->
    209180
    210181    <sect2 role="configuration" id="xft-font-protocol"  xreflabel="Xft Font Protocol">
    … …  
    292263        <listitem>
    293264          <para><ulink
    294           url="http://cle.linux.org.tw/fonts/FireFly">Firefly New Sung font</ulink>
     265          url="http://sourceforge.jp/projects/sfnet_chinesepuppy/downloads/ChineseSupport/Fonts/fireflysung-1.3.0.tar.gz">Firefly New Sung font</ulink>
    295266          - This font provides Chinese coverage. This font is listed in the
    296267          aliases in the
    … …  
    300271        <listitem>
    301272          <para><ulink
    302           url="http://cle.linux.org.tw/fonts/Arphic">Arphic fonts</ulink> -
     273          url="http://packages.debian.org/sid/fonts-arphic-ukai">Arphic fonts</ulink> -
    303274          A similar set of Chinese fonts to the Firefly New Sung font.
    304275          These fonts are listed in the aliases in the
    … …  
    335306      url="http://unifont.org/fontguide/">Unicode Font Guide</ulink>.</para>
    336307
    337       <para>As an example, consider the installation of the DejaVu fonts.  From
    338       the unpacked source directory, run the following commands as the
    339       <systemitem class="username">root</systemitem> user:</para>
     308      <para>Rendered examples of many of the above fonts can be found at this
     309      <ulink url="http://homepage.ntlworld.com/zarniwhoop/ttf-font-analysis/">
     310      font analysis</ulink> site.</para>
     311
     312      <para>As a font installation example, consider the installation of the
     313      DejaVu fonts.  From the unpacked source directory, run the following
     314      commands as the <systemitem class="username">root</systemitem> user:</para>
    340315
    341316<screen role="root"><userinput>install -v -d -m755 /usr/share/fonts/dejavu &amp;&amp;
    … …  
    347322  <sect2 role="configuration" id='xconfig'>
    348323    <title>Setting up Xorg Devices</title>
     324
    349325    <para>For most hardware configurations, modern Xorg will automatically
    350326    get the server configuration correct without any user intervention. There
    … …  
    360336    <para>A sample default XKB setup could look like the following (executed as
    361337    the <systemitem class="username">root</systemitem> user):</para>
     338
    362339<screen><userinput role="username">cat &gt; /etc/X11/xorg.conf.d/xkb-defaults.conf &lt;&lt; "EOF"
    363340Section "InputClass"
    … …  
    371348  <sect3 id="xdisplay">
    372349  <title>Fine Tuning Display Settings</title>
     350 
    373351  <para>Again, with modern Xorg, little or no additional configuration is
    374352  necessary. If you should need extra options passed to your video driver,
Note: See TracChangeset for help on using the changeset viewer.