Changeset e77c478 for x/installing


Ignore:
Timestamp:
07/18/2023 04:51:51 PM (11 months ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
12.0, 12.1, ken/TL2024, ken/tuningfonts, lazarus, plabs/newcss, python3.11, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18
Children:
6dfe4ab
Parents:
4048bc73 (diff), 5af5876 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Merge branch 'trunk' into lxqt

Location:
x/installing
Files:
6 edited

Legend:

Unmodified
Added
Removed

  • x/installing/installing.xml

    r4048bc73 re77c478  
    5959    model which allows writing applications completely independent of
    6060    the graphical hardware. This has the drawback that accessing modern
    61     hardware acceleration is difficult, so that other approaches are developed.
    62     Two new systems are available: <emphasis>Wayland</emphasis> and
    63     <emphasis>Vulkan</emphasis>. The former is a simpler replacement for
    64     X, easier to develop and maintain, using the OpenGL framework. The main
    65     desktop environments GNOME and KDE have been ported to it. The later allows
    66     direct access to graphical hardware through a portable interface. It is
    67     newer and not yet included in BLFS.
     61    hardware acceleration is difficult, so another approach named
     62    <emphasis>Wayland</emphasis> is developed.
     63    It is a simpler replacement for X, easier to develop and maintain, using
     64    the OpenGL framework. The main desktop environments GNOME and KDE have
     65    been ported to it.
    6866  </para>
    6967

  • x/installing/mesa.xml

    r4048bc73 re77c478  
    134134      <ulink url="https://github.com/tizonia/tizonia-openmax-il/wiki/Tizonia-OpenMAX-IL/">
    135135      libtizonia</ulink>,  and
    136       <ulink url="https://www.vulkan.org/">libvulkan</ulink>
     136      <ulink url="https://github.com/KhronosGroup/Vulkan-Loader">Vulkan-Loader</ulink>
    137137    </para>
    138138<!--
    … …  
    148148    </note>
    149149-->
     150  </sect2>
     151
     152  <sect2 role="kernel" id="mesa-kernel"
     153         xreflabel='Mesa Kernel Configuration'>
     154    <title>Kernel Configuration</title>
     155
     156    <para>
     157      Enable the following options in the kernel configuration and
     158      recompile the kernel if necessary:
     159    </para>
     160
     161<screen><literal>Device Drivers  ---&gt;
     162  Graphics support ---&gt;
     163    &lt;*/M&gt;   Direct Rendering Manager (XFree86 ... support) ---&gt; [CONFIG_DRM]
     164    &lt; /M&gt;   ATI Radeon                         [CONFIG_DRM_RADEON]  # For r300 or r600
     165    &lt; /M&gt;   AMD GPU                            [CONFIG_DRM_AMDGPU]  # For radeonsi
     166      [*] Enable AMDGPU support for SI parts   [CONFIG_DRM_AMDGPU_SI]
     167      [*] Enable AMDGPU support for CIK parts  [CONFIG_DRM_AMDGPU_CIK]
     168      Display Engine Configuration
     169        [*] AMD DC - Enable new display engine [CONFIG_DRM_AMD_DC]
     170    &lt; /*/M&gt; Nouveau (NVIDIA) cards             [CONFIG_DRM_NOUVEAU] # For nouveau
     171    &lt; /*/M&gt; Intel 8xx/9xx/G3x/G4x/HD Graphics  [CONFIG_DRM_I915]    # For i915, crocus, or iris
     172    &lt; /*/M&gt; DRM driver for VMware Virtual GPU  [CONFIG_DRM_VMWGFX]  # For svga
     173    &lt; /*/M&gt; Virtual GEM provider               [CONFIG_DRM_VGEM]    # For swrast</literal></screen>
     174
     175    <note>
     176      <para>
     177        The corresponding Mesa Gallium3D driver name is provided as the
     178        comment for the configuration entries.  If you don't know the name
     179        of the Mesa Gallium3D driver for your GPU, see <xref
     180        linkend="mesa-gallium-drivers"/> below.
     181      </para>
     182
     183      <para>
     184        <option>CONFIG_DRM_RADEON</option>,
     185        <option>CONFIG_DRM_AMDGPU</option>,
     186        <option>CONFIG_DRM_NOUVEAU</option>, and
     187        <option>CONFIG_DRM_I915</option> may require firmware.
     188        See <xref linkend='postlfs-firmware'/> for details.
     189      </para>
     190
     191      <para>
     192        Selecting <option>CONFIG_DRM_RADEON</option> or
     193        <option>CONFIG_DRM_AMDGPU</option> as
     194        <quote><literal>y</literal></quote> is not recommended. If it is, any
     195        required firmware must be built as a part of the kernel image or the
     196        initramfs for the driver to function correctly.
     197      </para>
     198
     199      <para>
     200        The sub-entries under <option>CONFIG_DRM_AMDGPU</option> are used
     201        to ensure the AMDGPU kernel driver supports all GPUs using the
     202        <literal>radeonsi</literal> driver.  They are not needed if you
     203        won't need <option>CONFIG_DRM_AMDGPU</option> itself. They
     204        may be unneeded for some GPU models.
     205      </para>
     206
     207      <para>
     208        For <literal>swrast</literal>, <option>CONFIG_DRM_VGEM</option>
     209        is not strictly needed but recommended as an optimization.
     210      </para>
     211    </note>
     212    <indexterm zone="mesa mesa-kernel">
     213      <primary sortas="d-mesa">mesa</primary>
     214    </indexterm>
    150215  </sect2>
    151216
    … …  
    177242    </note>
    178243
    179     <para>
    180       Now, select the drivers you wish to install. For the X86 architecture, the
    181       available gallium drivers are auto (<emphasis>in 21.2.1 this does not select
    182       crocus </emphasis>), <emphasis>or alternatively a choice from</emphasis>
    183       crocus, i915, iris, nouveau, r300, r600, radeonsi, svga, swrast, and virgl.
    184       The latter can provide acceleration in <xref linkend="qemu"/> if that has
    185       been linked against
    186       <ulink url="https://gitlab.freedesktop.org/virgl/virglrenderer/~/releases/">virglrenderer</ulink>
    187       (you will need a freedesktop.org account to get to that page, you can
    188       download the 0.9.1 release without an account from
    189      <ulink url="https://gitlab.freedesktop.org/virgl/virglrenderer/-/archive/0.9.1/virglrenderer-0.9.1.tar.bz2">virglrenderer-0.9.1</ulink>).-->
    190 
    191 <!-- If you wish to build all available gallium drivers,
    192       use 'auto'. FIXME : does not build crocus in 21.2.1 -->
    193 
    194       <!-- crocus was added to the default x86/x86_64 drivers for meson in the
    195       master branch on 2021-08-31, at some point it will appear in a stable release
    196     </para>
    197244-->
    198245<!--
    … …  
    290337
    291338    <para>
    292       <parameter>-Dgallium-drivers="..."</parameter>: This parameter
     339      <anchor id='mesa-gallium-drivers' xreflabel='Mesa Gallium3D Drivers'/>
     340      <parameter>-Dgallium-drivers=auto</parameter>: This parameter
    293341      controls which Gallium3D drivers should be built.
     342      <literal>auto</literal> selects all Gallium3D drivers available
     343      for x86: <literal>r300</literal> (for ATI Radeon 9000 or Radeon X
     344      series), <literal>r600</literal> (for AMD/ATI Radeon HD 2000-6000
     345      series), <literal>radeonsi</literal> (for AMD Radeon HD 7000 or newer
     346      AMD GPU models), <literal>nouveau</literal>
     347      (for Supported NVIDIA GPUs, they are listed as all
     348      <quote>3D features</quote> either <quote>DONE</quote> or
     349      <quote>N/A</quote> in <ulink
     350      url='https://nouveau.freedesktop.org/FeatureMatrix.html'>the Nouveau
     351      status page</ulink>), <literal>virgl</literal> (for QEMU virtual GPU
     352      with <application>virglrender</application> support; note that BLFS
     353      <xref linkend='qemu'/> is not built with
     354      <application>virglrender</application>), <literal>svga</literal>
     355      (for VMWare virtual GPU), <literal>swrast</literal> (using CPU for 3D
     356      rasterisation; note that it's much slower than using a modern
     357      3D-capable GPU, so it should be only used if the GPU is not supported
     358      by other drivers), <literal>iris</literal> (for Intel GPUs shipped
     359      with Broadwell or newer CPUs), <literal>crocus</literal> (for Intel
     360      GMA 3000, X3000 series, 4000 series, or X4000 series GPUs shipped with
     361      chipsets, or Intel HD GPUs shipped with pre-Broadwell CPUs),
     362      <literal>i915</literal> (for Intel GMA 900, 950, 3100, or 3150 GPUs
     363      shipped with chipsets or Atom D/N 4xx/5xx CPUs).  You may replace
     364      <literal>auto</literal> with a comma-separated list to build only
     365      a subset of these drivers if you precisely know which drivers you
     366      need, for example
     367      <option>-Dgallium-drivers=radeonsi,iris,swrast</option>.
    294368    </para>
    295369<!--
    … …  
    310384      <parameter>-Dvulkan-drivers=""</parameter>: This switch allows choosing
    311385      which Vulkan drivers are built. The default is auto, but this requires
    312       the optional dependency <filename>glslang</filename>. So it is better
    313       to pass an empty list, in order to remove the need for that
    314       dependency.  Nothing in BLFS uses Vulkan anyway.
     386      the optional dependencies <application>glslang</application> and
     387      <application>Vulkan-Loader</application>.  Vulkan is a newer API
     388      designed for utilizing the GPUs with a performance better than OpenGL,
     389      but nothing in BLFS benefits from it for now.  So we pass an empty
     390      list in order to remove the need for these dependencies.
    315391    </para>
    316392
    … …  
    365441        </seg>
    366442        <seg>
    367           <!-- Begin gallium DRI drivers : this is the full set -->
    368 <!--          d3dadapter9.so (optional),   For Windows games. This is DirectX's
    369                                           Direct3D -->
     443          <!-- d3dadapter9.so (optional)
     444               I guess this is useless today, Wine applications use Vulkan
     445               through libvkd3d, and new games with native Linux support
     446               likely uses Vulkan directly.  -->
     447          <!-- Begin gallium DRI drivers (*_dri.so) and VA-API drivers
     448               (*_drv_video.so): this is the full set -->
    370449          crocus_dri.so,
    371450          i915_dri.so,

  • x/installing/x7driver.xml

    r4048bc73 re77c478  
    44  <!ENTITY % general-entities SYSTEM "../../general.ent">
    55  %general-entities;
    6   <!ENTITY BLFS76 "https://www.linuxfromscratch.org/blfs/view/7.6/x/x7driver.html">
    7 
    86]>
    97
    10 <sect1 id="xorg7-driver" xreflabel="Xorg Drivers">
     8<sect1 id="xorg7-input-driver" xreflabel="Xorg Input Drivers">
    119  <?dbhtml filename="x7driver.html"?>
    1210
    1311
    14   <title>Xorg Drivers</title>
     12  <title>Xorg Input Drivers</title>
    1513
    16   <indexterm zone="xorg7-driver">
    17     <primary sortas="a-xorg7-driver">xorg7-driver</primary>
     14  <indexterm zone="xorg7-input-driver">
     15    <primary sortas="a-xorg7-input-driver">xorg7-input-driver</primary>
    1816  </indexterm>
    1917
    2018  <sect2 role="package">
    21     <title>Introduction to Xorg Drivers</title>
     19    <title>Introduction to Xorg Input Drivers</title>
    2220
    2321    <para>
    24       The <application>Xorg Drivers</application> page contains the
    25       instructions for building Xorg drivers that are necessary in order
    26       for Xorg Server to take advantage of the hardware that it is
    27       running on. At least one input and one video driver are required
    28       for Xorg Server to start.
     22      The <application>Xorg Input Drivers</application> page contains the
     23      instructions for building Xorg input drivers that are necessary in
     24      order for Xorg Server to respond user inputs.
    2925    </para>
    30 
    31     <para>
    32       On machines using KMS, the modesetting driver is provided by
    33       <application>xorg-server</application> and can be used instead of the
    34       video driver for the specific hardware, but with reduced performance.
    35       It can also be used (without hardware acceleration) in virtual machines
    36       running under <application>qemu</application>.
    37     </para>
    38 
    39     <note>
    40       <para>
    41         If you are unsure which video hardware you have, you can use
    42         <command>lspci</command> from <xref linkend="pciutils"/>
    43         to find out which video hardware you have and then look at
    44         the descriptions of the packages in order to find out
    45         which driver you need.
    46       </para>
    47     </note>
    48 
    49     <note>
    50       <para>
    51         In addition to the drivers listed below, there are several other
    52         drivers for very old hardware that may still be relevant.
    53         The latest versions of these drivers may be downloaded from
    54         <ulink url='https://www.x.org/archive/individual/driver'>
    55         https://www.x.org/archive/individual/driver</ulink>.
    56         Instructions for building these now intermittently maintained drivers
    57         may be found in a
    58         prior version of BLFS: <ulink url="&BLFS76;">&BLFS76;</ulink>
    59       </para>
    60     </note>
    6126
    6227    <sect3 id="xorg-input-drivers">
    … …  
    10974    </sect3>
    11075
    111     <sect3 id="xorg-video-drivers">
    112       <title>Xorg Video Drivers</title>
    113 
    114       <itemizedlist spacing="compact">
    115         <listitem>
    116           <para>
    117             <xref linkend="xorg-amdgpu-driver"/>
    118           </para>
    119         </listitem>
    120         <listitem>
    121           <para>
    122             <xref linkend="xorg-ati-driver"/>
    123           </para>
    124         </listitem>
    125         <listitem>
    126           <para>
    127             <xref linkend="xorg-fbdev-driver"/>
    128           </para>
    129         </listitem>
    130         <listitem>
    131           <para>
    132             <xref linkend="xorg-intel-driver"/>
    133           </para>
    134         </listitem>
    135         <listitem>
    136           <para>
    137             <xref linkend="xorg-nouveau-driver"/>
    138           </para>
    139         </listitem>
    140         <listitem>
    141           <para>
    142             <xref linkend="xorg-vmware-driver"/>
    143           </para>
    144         </listitem>
    145       </itemizedlist>
    146 
    147     </sect3>
    148 
    149     <sect3 id="hw-video-acceleration">
    150       <title>Hardware Video Acceleration</title>
    151 
    152       <itemizedlist spacing="compact">
    153         <listitem>
    154           <para>
    155             <xref linkend="intel-media-driver"/>
    156           </para>
    157         </listitem>
    158         <listitem>
    159           <para>
    160             <xref linkend="intel-vaapi-driver"/>
    161           </para>
    162         </listitem>
    163         <listitem>
    164           <para>
    165             <xref linkend="libva"/>
    166           </para>
    167         </listitem>
    168         <listitem>
    169           <para>
    170             <xref linkend="libvdpau"/>
    171           </para>
    172         </listitem>
    173         <listitem>
    174           <para>
    175             <xref linkend="libvdpau-va-gl"/>
    176           </para>
    177         </listitem>
    178       </itemizedlist>
    179 
    180     </sect3>
    181 
    18276  </sect2>
    18377
    … …  
    20397    href="x7driver-wacom.xml"/>
    20498
    205   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    206     href="x7driver-amdgpu.xml"/>
    207 
    208   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    209     href="x7driver-ati.xml"/>
    210 
    211   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    212     href="x7driver-fbdev.xml"/>
    213 
    214   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    215     href="x7driver-intel.xml"/>
    216 
    217   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    218     href="x7driver-nouveau.xml"/>
    219 
    220   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    221     href="x7driver-vmware.xml"/>
    222 
    223   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    224     href="intel-media-driver.xml"/>
    225 
    226   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    227     href="intel-vaapi-driver.xml"/>
    228 
    229   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    230     href="libva.xml"/>
    231 
    232   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    233     href="libvdpau.xml"/>
    234 
    235   <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
    236     href="libvdpau-va-gl.xml"/>
    237 
    23899</sect1>

  • x/installing/xorg-config.xml

    r4048bc73 re77c478  
    399399
    400400      <para>
    401         Again, with modern Xorg, little or no additional configuration is
    402         necessary. If you should need extra options passed to your video driver,
    403         for instance, you could use something like the following (again,
    404         executed as the <systemitem class="username">root</systemitem> user):
    405       </para>
    406 
    407 <screen role="root"><userinput>cat &gt; /etc/X11/xorg.conf.d/videocard-0.conf &lt;&lt; "EOF"
    408 <literal>Section "Device"
    409     Identifier  "Videocard0"
    410     Driver      "radeon"
    411     VendorName  "Videocard vendor"
    412     BoardName   "ATI Radeon 7500"
    413     Option      "NoAccel" "true"
     401        If you want to set the monitor resolution for Xorg, first run
     402        <command>xrandr</command> in a X terminal to list the supported
     403        resolutions and the corresponding refresh rates.  For example, it
     404        outputs the following for one monitor:
     405      </para>
     406
     407<screen><computeroutput>Screen 0: minimum 16 x 16, current 5760 x 2160, maximum 32767 x 32767
     408DP-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 600mm x 340mm
     409   3840x2160     59.98*+
     410   2048x1536     59.95 
     411   1920x1440     59.90 
     412   1600x1200     59.87 
     413   1440x1080     59.99 
     414   1400x1050     59.98 
     415   1280x1024     59.89 
     416   1280x960      59.94 
     417   1152x864      59.96 
     418   1024x768      59.92 
     419   800x600       59.86 
     420   640x480       59.38  </computeroutput></screen>
     421
     422      <para>
     423        From the output we can see the monitor is identified
     424        <literal>DP-1</literal>.  Select a suitable resolution from the
     425        outputed list, for example <literal>1920x1440</literal>.  Then
     426        as the &root; user, create a configuration file for the Xorg server:
     427      </para>
     428
     429<screen role="root"><userinput>cat &gt; /etc/X11/xorg.conf.d/monitor-DP-1.conf &lt;&lt; "EOF"
     430<literal>Section "Monitor"
     431    Identifier  "DP-1"
     432    Option      "PerferredMode" "1920x1440"
    414433EndSection</literal>
    415434EOF</userinput></screen>
     435
     436      <para>
     437        Sometimes <command>xrandr</command> may fail to detect some
     438        resolution settings supported by the monitor.  It usually happens
     439        with virtual monitors of virtual machine managers like
     440        <xref linkend='qemu'/> or VMWare: a virtual monitor actually
     441        supports all pairs of integers in a range as the resolution, but
     442        <command>xrandr</command> will only list a few.  To use a
     443        resolution not listed by <command>xrandr</command>, first run
     444        <command>cvt</command> to get the mode line for the resolution.
     445        For example:
     446      </para>
     447
     448      <screen><userinput>cvt 1600 900</userinput>
     449<computeroutput><literal># 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz
     450Modeline "1600x900_60.00"  118.25  1600 1696 1856 2112  900 903 908 934 -hsync +vsync</literal></computeroutput></screen>
     451
     452      <para>
     453        As the &root; user, create a Xorg server configuration file
     454        containing this mode line, and specify the mode as preferred mode:
     455      </para>
     456
     457<screen role="root"><userinput>cat &gt; /etc/X11/xorg.conf.d/monitor-DP-1.conf &lt;&lt; "EOF"
     458<literal>Section "Monitor"
     459    Identifier  "DP-1"
     460    Modeline    "1600x900_60.00"  118.25  1600 1696 1856 2112  900 903 908 934 -hsync +vsync
     461    Option      "PerferredMode"   "1600x900_60.00"
     462EndSection</literal>
     463EOF</userinput></screen>
     464
     465      <para>
     466        Some high-end LCD monitors support a refresh rate higher than 100 Hz
     467        but <command>xrandr</command> may fail to recognize the supported
     468        refresh rate and use 60 Hz instead.  This issue would prevent you
     469        from utilizing the full capability of the monitor, and may cause
     470        the screen to flicker or show <quote>artifacts</quote> like meshes
     471        or grids.  To resolve the issue, again use <command>cvt</command>
     472        to get the mode line with a custom refresh rate:
     473      </para>
     474
     475      <screen><userinput>cvt 3840 2160 144</userinput>
     476<computeroutput><literal># 3840x2160 143.94 Hz (CVT) hsync: 338.25 kHz; pclk: 1829.25 MHz
     477Modeline "3840x2160_144.00"  1829.25  3840 4200 4624 5408  2160 2163 2168 2350 -hsync +vsync</literal></computeroutput></screen>
     478
     479      <para>
     480        Then paste it into the Xorg server configuration file and set it
     481        as the preferred mode.
     482      </para>
    416483
    417484      <para>
    … …  
    430497EOF</userinput></screen>
    431498
     499      <para>
     500        With modern Xorg, little or no additional graphic card configuration
     501        is necessary. If you should need extra options passed to your video
     502        driver, for instance, you could use something like the following
     503        (again, executed as the &root; user):
     504      </para>
     505
     506<screen role="root"><userinput>cat &gt; /etc/X11/xorg.conf.d/videocard-0.conf &lt;&lt; "EOF"
     507<literal>Section "Device"
     508    Identifier  "Videocard0"
     509    Driver      "modesetting"
     510    VendorName  "Videocard vendor"
     511    BoardName   "ATI Radeon 7500"
     512    Option      "AccelMethod" "none"
     513EndSection</literal>
     514EOF</userinput></screen>
     515
    432516    </sect3>
    433517  </sect2>

  • x/installing/xorg-server.xml

    r4048bc73 re77c478  
    1111  <!ENTITY xorg-server-buildsize     "188 MB (with tests)">
    1212  <!ENTITY xorg-server-time          "0.6 SBU (using parallelism=4; with tests)">
     13  <!ENTITY modesetting_drv
     14           "<filename class='libraryfile'>modesetting_drv</filename>">
     15  <!ENTITY BLFS113 "https://www.linuxfromscratch.org/blfs/view/11.3/x/x7driver.html">
     16  <!ENTITY BLFS76 "https://www.linuxfromscratch.org/blfs/view/7.6/x/x7driver.html">
    1317]>
    1418
    … …  
    105109      <ulink url="https://www.x.org/archive/individual/doc/">xorg-sgml-doctools</ulink> (to build documentation)
    106110    </para>
    107 
     111  </sect2>
     112
     113  <sect2 role="kernel" id="xorg-server-kernel">
     114    <title>Kernel Configuration</title>
     115
     116    <para>
     117      The traditional Device Dependant X (DDX) drivers have been removed
     118      from BLFS in favor of the &modesetting_drv; driver which will be
     119      built as a part of this package.  To use the &modesetting_drv; driver,
     120      the kernel must provide a Direct Rendering Manager (DRM) driver for
     121      your GPU.
     122    </para>
     123
     124    <para>
     125      If your GPU supports 3D acceleration and <xref linkend='mesa'/>
     126      provides a Gallium3D driver for utilizing its 3D capability, you
     127      should have already enabled the necessary kernel configuration options
     128      in <xref linkend='mesa-kernel'/>.  Otherwise, you need to find the
     129      kernel configuration option of the DRM driver for the GPU and enable
     130      it.  Notably, the virtual GPUs provided by some virtual machine
     131      managers:
     132    </para>
     133
     134<screen><literal>Device Drivers  ---&gt;
     135  Graphics support ---&gt;
     136    &lt;*/M&gt;   Direct Rendering Manager (XFree86 ... support) ---&gt;     [CONFIG_DRM]
     137    &lt; /*/M&gt; DRM driver for VMware Virtual GPU                       [CONFIG_DRM_VMWGFX]
     138    &lt; /*/M&gt; DRM Support for bochs dispi vga interface (qemu stdvga) [CONFIG_DRM_BOCHS]
     139    &lt; /*/M&gt; Virtual Box Graphics Card                               [CONFIG_DRM_VBOXVIDEO]</literal></screen>
     140
     141    <para>
     142      If the kernel does not provide a DRM driver for your GPU, on most x86
     143      systems the <quote>simple frame buffer</quote> DRM driver running on
     144      VESA or UEFI frame buffer can be used as a fallback.  Enable the
     145      following options in the kernel configurations if you don't have a
     146      dedicated DRM driver for the GPU, or you want to keep the simple
     147      frame buffer driver as a fallback in case the dedicated driver fails:
     148    </para>
     149
     150<screen><literal>Device Drivers  ---&gt;
     151  Firmware Drivers ---&gt;
     152    [*] Mark VGA/VBE/EFI FB as generic system framebuffer       [CONFIG_SYSFB_SIMPLEFB]
     153  Graphics support ---&gt;
     154    &lt;*&gt; Direct Rendering Manager (XFree86 ... support)          [CONFIG_DRM]
     155    &lt;*&gt; Simple framebuffer driver                               [CONFIG_DRM_SIMPLEDRM]</literal></screen>
     156
     157    <para>
     158      To allow the kernel to print debug messages at an early boot stage,
     159      <option>CONFIG_DRM</option> and <option>CONFIG_DRM_SIMPLEDRM</option>
     160      should not be built as kernel modules unless an initramfs will be
     161      used.
     162    </para>
     163
     164    <para>
     165      If you want to use the simple frame buffer driver on a system booted
     166      via BIOS (instead of UEFI), add the following line before the first
     167      <literal>menuentry</literal> block in the
     168      <filename>/boot/grub/grub.cfg</filename> file to initialize the VESA
     169      frame buffer:
     170    </para>
     171
     172<screen><literal>set gfxpayload=<replaceable>1024x768x32</replaceable></literal></screen>
     173
     174    <para>
     175      You may replace <literal>1024</literal>, <literal>768</literal>, and
     176      <literal>32</literal> with a resolution and color depth setting
     177      suitable for your monitor.
     178    </para>
     179
     180    <para>
     181      If all of these DRM drivers do not work for you and you need to use
     182      a DDX driver with a non-DRM kernel GPU driver (usually named
     183      <option>CONFIG_FB_*</option> in the kernel configuration, or existing
     184      as out-tree kernel modules), or you need an device specific
     185      functionality requiring a DDX driver, consult
     186      <ulink url="&BLFS113;">a prior version of BLFS</ulink>, or
     187      <ulink url="&BLFS76;">a even prior version</ulink> for more DDX
     188      drivers.
     189    </para>
     190
     191    <indexterm zone="xorg-server xorg-server-kernel">
     192      <primary sortas="d-xorg-server">xorg-server</primary>
     193    </indexterm>
    108194  </sect2>
    109195
    … …  
    121207      --prefix=$XORG_PREFIX \
    122208      --localstatedir=/var  \
    123       -Dsuid_wrapper=true   \
     209      -Dglamor=true         \
    124210      -Dxkb_output_dir=/var/lib/xkb &amp;&amp;
    125211ninja</userinput></screen>
    … …  
    138224<screen role="root" revision="sysv"><userinput>ninja install &amp;&amp;
    139225mkdir -pv /etc/X11/xorg.conf.d &amp;&amp;
     226install -v -d -m1777 /tmp/.{ICE,X11}-unix &amp;&amp;
    140227cat &gt;&gt; /etc/sysconfig/createfiles &lt;&lt; "EOF"
    141228<literal>/tmp/.ICE-unix dir 1777 root root
    … …  
    152239
    153240    <para>
    154       <parameter>-Dsuid_wrapper=true</parameter>: Builds the suid-root
    155       wrapper for legacy driver support on rootless xserver systems.
     241      <parameter>-Dglamor=true</parameter>: Ensure building the Glamor
     242      module.  It's needed to build the &modesetting_drv; driver
     243      which replaces the traditional Device Dependant X (DDX) drivers.
     244    </para>
     245
     246    <para>
     247      <option>-Dsuid_wrapper=true</option>: Builds the suid-root
     248      wrapper for legacy DDX driver support on rootless xserver systems.
    156249    </para>
    157250
    … …  
    193286        <seg>
    194287          several under $XORG_PREFIX/lib/xorg/modules/ including the
    195           <filename class="libraryfile">modesetting_drv.so</filename>
    196           driver
     288          &modesetting_drv; driver
    197289        </seg>
    198290        <seg>

  • x/installing/xterm.xml

    r4048bc73 re77c478  
    88  <!--<!ENTITY xterm-download-ftp  "ftp://invisible-island.net/xterm/xterm-&xterm-version;.tgz">-->
    99  <!ENTITY xterm-download-ftp  " ">
    10   <!ENTITY xterm-md5sum        "a8a6db76a763d4c1e35d1d8daf57701f">
    11   <!ENTITY xterm-size          "1.5 MB">
     10  <!ENTITY xterm-md5sum        "27a701e73076e42a265e34f8fe558ff6">
     11  <!ENTITY xterm-size          "1.4 MB">
    1212  <!ENTITY xterm-buildsize     "14 MB">
    1313  <!ENTITY xterm-time          "0.1 SBU (with parallelism=4)">
Note: See TracChangeset for help on using the changeset viewer.