The Xorg Drivers page contains the instructions for building Xorg drivers that are necessary in order for Xorg Server to take advantage of the hardware that it is running on. At least one input and one video driver are required for Xorg Server to start.
On machines using KMS, the modesetting driver is provided by xorg-server and can be used instead of the video driver for the specific hardware, but with reduced performance. It can also be used (without hardware acceleration) in virtual machines running under qemu.
If you are unsure which video hardware you have, you can use lspci from pciutils-3.6.2 to find out which video hardware you have and then look at the descriptions of the packages in order to find out which driver you need.
In addition to the drivers listed below, there are several other drivers for very old hardware that may still be relevant. The latest versions of these drivers may be downloaded from https://www.x.org/archive/individual/driver. Instructions for building these now intermittently maintained drivers may be found in a prior version of BLFS: http://www.linuxfromscratch.org/blfs/view/7.6/x/x7driver.html
The libevdev package contains common functions for Xorg input drivers.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.freedesktop.org/software/libevdev/libevdev-1.5.9.tar.xz
Download MD5 sum: a1ca11e961c1efed720fac4130881904
Download size: 400 KB
Estimated disk space required: 7.0 MB (with tests)
Estimated build time: 0.3 SBU (with tests)
Doxygen-1.8.14, Python-2.7.15, and Valgrind-3.13.0 (optional for tests)
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libevdev
Enable the following options in the kernel configuration and recompile the kernel if necessary:
Device Drivers --->
Input device support --->
<*> Generic input layer (needed for...) [CONFIG_INPUT]
<*> Event interface [CONFIG_INPUT_EVDEV]
[*] Miscellaneous devices ---> [CONFIG_INPUT_MISC]
<*> User level driver support [CONFIG_INPUT_UINPUT]
Install libevdev by running the following commands:
./configure $XORG_CONFIG && make
The regression tests can be run as the root
user with make check, in a graphical
session. Note that on some systems, the tests may cause a hard
lockup and require a reboot.
Now, as the root
user:
make install
is a tool to change some kernel device properties. |
|
is a tool to estimate the resolution of a mouse. |
|
touchpad-edge-detector is a tool that reads the touchpad events from the kernel and calculates the minimum and maximum for the x and y coordinates, respectively. |
|
is a library of Xorg driver input functions. |
The Xorg Evdev Driver package contains a Generic Linux input driver for the Xorg X server. It handles keyboard, mouse, touchpads and wacom devices, though for touchpad and wacom advanced handling, additional drivers are required.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-input-evdev-2.10.6.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-input-evdev-2.10.6.tar.bz2
Download MD5 sum: e8bd1edc6751f92e425cae7eba3c61eb
Download size: 400 KB
Estimated disk space required: 3.9 MB
Estimated build time: less than 0.1 SBU
libevdev-1.5.9, mtdev-1.1.5, and Xorg-Server-1.20.1
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-evdev-driver
Install Xorg Evdev Driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
libinput is a library that handles input devices for display servers and other applications that need to directly deal with input devices.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.freedesktop.org/software/libinput/libinput-1.11.3.tar.xz
Download MD5 sum: df6e877f11de4a9793511e9abfe7ef01
Download size: 476 KB
Estimated disk space required: 8.3 MB
Estimated build time: less than 0.1 SBU
libevdev-1.5.9 and mtdev-1.1.5
Valgrind-3.13.0 (to run the tests), Doxygen-1.8.14 and Graphviz-2.40.1 (to build the documentation) GTK+-3.22.30 (to build the GUI event viewer), libunwind (required for tests), libwacom , and PyParsing (for one non-root test)
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libinput
Although libinput works with the same kernel configuration used
by libevdev-1.5.9, its extensive testsuite
requires the presence of /dev/uinput
(as well as both Valgrind-3.13.0 and libunwind).
If you wish to run the full tests, enable the following option in the kernel configuration and recompile the kernel if necessary:
Device Drivers --->
Input device support --->
Miscellaneous Devices --->
<*/M> User level driver support [CONFIG_INPUT_UINPUT]
If you build this as a module, it needs to be inserted before the testsuite runs.
On an Xorg system you will also need to prevent the events
generated during the testsuite from interfering with your
desktop. Copy the file test/50-litest.conf
into ${XORG_PREFIX}/share/X11/xorg.conf.d
and
restart X. For further information see
libinput test suite.
Install libinput by running the following commands:
mkdir build && cd build && meson --prefix=$XORG_PREFIX \ -Dudev-dir=/lib/udev \ -Ddebug-gui=false \ -Dtests=false \ -Ddocumentation=false \ -Dlibwacom=false \ .. && ninja
If you want to run the full tests, remove -Dtests from the meson command above. Please read "kernel configuration for running the libinput testsuite" (above).
If you have enabled the full tests, you can run the main tests as the root user by executing: ninja test. A very large number of tests will be run, about 20 fail (at least on an Xorg system).
Now, as the root
user:
ninja install
If Doxygen-1.8.14 and Graphviz-2.40.1 were present during the
build, you can install the generated documentation by running the
following commands as the root
user:
install -v -dm755 /usr/share/doc/libinput-1.11.3 && cp -rv html/* /usr/share/doc/libinput-1.11.3
-Dudev-dir=/lib/udev
: This switch
specifies where UDev rules and hwdb files will be installed.
-Ddebug-gui=false
: This switch
disables creation of a visual debug helper for libinput. Remove
if you want it, and you have GTK+-3.22.30 installed.
-Dtests=false
: This switch disables
compilation of the main tests. Even with the tests defined as
false, you can still run the first four minor tests, as a regular
user, but one will be skipped if https://pypi.org/project/pyparsing
is not installed.
-Ddocumentation=false
: This switch
disables generation of the documentation. Remove if you want to
generate it, and you have Doxygen-1.8.14 and Graphviz-2.40.1 installed.
-Dlibwacom=false
: Remove this option
if you have the external library libwacom installed.
is a set of tools to interface with the libinput library. |
|
is a debug helper for libinput. |
|
lists local devices as recognized by libinput. |
|
is the entry to a set of debugging programs to measure the properties of one or more devices. |
|
records kernel events from a device in a form that can later be replayed by libinput-replay. |
|
replays kernel events from a recording made by libinput-record. |
|
contains API functions for handling input devices. |
The X.Org Libinput Driver is a thin wrapper around libinput and allows for libinput to be used for input devices in X. This driver can be used as as drop-in replacement for evdev and synaptics.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-input-libinput-0.28.0.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-input-libinput-0.28.0.tar.bz2
Download MD5 sum: 2d7519ac0e39d4c88f3be32e81a637aa
Download size: 448 KB
Estimated disk space required: 3.6 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)
libinput-1.11.3 and Xorg-Server-1.20.1
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-libinput-driver
Install Xorg Libinput Driver by running the following commands:
./configure $XORG_CONFIG && make
To test the results, issue make check.
Now, as the root
user:
make install
The Xorg Synaptics Driver package contains the X.Org Input Driver, support programs and SDK for Synaptics touchpads. Even though the evdev driver can handle touchpads very well, this driver is required if you want to use advanced features like multi tapping, scrolling with touchpad, turning the touchpad off while typing, etc.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-input-synaptics-1.9.1.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-input-synaptics-1.9.1.tar.bz2
Download MD5 sum: cfb79d3c975151f9bbf30b727c260cb9
Download size: 492 KB
Estimated disk space required: 4.8 MB
Estimated build time: less than 0.1 SBU
libevdev-1.5.9 and Xorg-Server-1.20.1
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-synaptics-driver
Install Xorg Synaptics Driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The Xorg VMMouse Driver package contains the VMMouse input driver for the Xorg X server. The VMMouse driver enables support for the special VMMouse protocol that is provided by VMware virtual machines to give absolute pointer positioning. It can be used with Qemu, too.
Starting with version 4.1, the linux kernel supports the VMMouse protocol so that this driver is not needed anymore. Furthermore, kernel support conflicts with earlier versions of this driver (before 13.1), so it is advisable to either remove this driver if you plan to always use kernels with versions greater or equal to 4.1, or update this driver to 13.1 or above if you want to be able to use both old and recent kernels.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-input-vmmouse-13.1.0.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-input-vmmouse-13.1.0.tar.bz2
Download MD5 sum: 85e2e464b7219c495ad3a16465c226ed
Download size: 312 KB
Estimated disk space required: 2.9 MB
Estimated build time: less than 0.1 SBU
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-vmmouse-driver
To get kernel support for the VMMouse, enable the following options in the kernel configuration and recompile the kernel if necessary:
Processor type and features --->
[*] Symmetric multi-processing support [CONFIG_SMP]
[*] Support for extended (non-PC) x86 platforms [CONFIG_X86_EXTENDED_PLATFORM]
[*] ScaleMP vSMP [CONFIG_X86_VSMP]
Device Drivers --->
Input device support --->
[*] Mice ---> [CONFIG_INPUT_MOUSE]
<*/M> PS/2 mouse [CONFIG_MOUSE_PS2]
[*] Virtual mouse (vmmouse) [CONFIG_MOUSE_PS2_VMMOUSE]
Install Xorg VMMouse Driver by running the following commands:
./configure $XORG_CONFIG \ --without-hal-fdi-dir \ --without-hal-callouts-dir \ --with-udev-rules-dir=/lib/udev/rules.d && make
This package does not come with a test suite.
Now, as the root
user:
make install
--with-udev-rules-dir=/lib/udev/rules.d
:
This switch specifies where udev rules should be installed.
--without-hal-*-dir
:
These switches disable installation of the HAL components which are not needed on
Linux.
The Xorg Wacom Driver package contains the X.Org X11 driver and SDK for Wacom and Wacom-like tablets. It is not required to use a Wacom tablet, the xf86-input-evdev driver can handle these devices without problems.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://downloads.sourceforge.net/linuxwacom/xf86-input-wacom-0.36.0.tar.bz2
Download MD5 sum: d1d45f05cf1877b181dc324ce1deb7e9
Download size: 600 KB
Estimated disk space required: 10 MB (with tests)
Estimated build time: 0.1 SBU (with tests)
Doxygen-1.8.14 and Graphviz-2.40.1
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-wacom-driver
To use a Wacom tablet with USB interface, enable the following options in your kernel configuration and recompile. Note that other configuration options could be required for tablet with a serial or bluetooth interface:
Device Drivers --->
HID support --->
<*/M> HID bus support [CONFIG_HID]
Special HID drivers --->
<*/M> Wacom Intuos/Graphire tablet support (USB) [CONFIG_HID_WACOM]
Install Xorg Wacom Driver by running the following commands:
./configure $XORG_CONFIG --with-systemd-unit-dir=no && make
To test the results, issue: make check.
Now, as the root
user:
make install
The Xorg AMDGPU Driver package contains the X.Org Video Driver for newer AMD Radeon video cards starting from Volcanic Islands. It can also be used for Southern and Sea Islands if the experimental support was enabled in the kernel.
This package is known to build and work properly using an LFS-8.3 platform.
For Direct Rendering to work, you need to enable the radeonsi Gallium driver at Mesa-18.1.6 build time. Also, all cards require Firmware to be available when the kernel driver is loaded. Firmware can be obtained from http://anduin.linuxfromscratch.org/BLFS/linux-firmware/. See the section called “Kernel Configuration for additional firmware” below for additional firmware.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-video-amdgpu-18.0.1.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-amdgpu-18.0.1.tar.bz2
Download MD5 sum: d8368d204cb98d4387c8890562db1143
Download size: 408 KB
Estimated disk space required: 6.4 MB
Estimated build time: less than 0.1 SBU
Xorg-Server-1.20.1 (must be built with glamor enabled)
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-amdgpu-driver
Enable the following options in the kernel configuration and recompile the kernel if necessary:
Device Drivers --->
Graphics support --->
<*> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
<*/M> AMD GPU [CONFIG_DRM_AMDGPU]
[ /*] Enable amdgpu support for SI parts [CONFIG_DRM_AMDGPU_SI]
[ /*] Enable amdgpu support for CIK parts [CONFIG_DRM_AMDGPU_CIK]
The last two options enable experimental support for Southern and Sea Islands AMD GPUs so they can be used with this driver. Note that the support is marked experimental and disabled by default. Xorg ATI Driver-18.0.1 should be used for those GPUs.
If you need to add firmware, install the file(s) and then point
to them in the kernel configuration and recompile the kernel if
necessary. To find out which firmware you need, consult the
Decoder ring for engineering vs marketing names. Download any
firmware for your card which is named like:
,
etc. Below is an example for Radeon R7 M340 GPU, which is
codenamed Iceland/Topaz, along with a network card that also
requires the firmware:
<ENGINEERING_NAME>
_rlc.bin
CONFIG_EXTRA_FIRMWARE="amdgpu/topaz_ce.bin amdgpu/topaz_k_smc.bin amdgpu/topaz_mc.bin
amdgpu/topaz_me.bin amdgpu/topaz_mec2.bin amdgpu/topaz_mec.bin
amdgpu/topaz_pfp.bin amdgpu/topaz_rlc.bin amdgpu/topaz_sdma1.bin
amdgpu/topaz_sdma.bin amdgpu/topaz_smc.bin rtl_nic/rtl8168e-3.fw"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
CONFIG_EXTRA_FIRMWARE should all be on one line. It is shown above as multiple lines for presentation only.
You can check dmesg output after boot to see which firmware is missing.
Alternatively, if you change CONFIG_DRM_AMDGPU to '=m' in your linux kernel .config the firmware can be loaded automatically from /lib/firmware/amdgpu/ when it installs the module. This offers a tiny space saving, but also means that the screen will be blank for a longer time before the framebuffer appears. Distros take this approach because it is not practical to specify every possible firmware and the kernel would be excessively big.
Install Xorg AMDGPU Driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The Xorg ATI Driver package contains the X.Org Video Driver for ATI Radeon video cards including all chipsets ranging from R100 to the "Volcanic Islands" chipsets.
This package is known to build and work properly using an LFS-8.3 platform.
For Direct Rendering to work with newer Radeon Cards (R300 and later chipsets), you need to enable the r300, r600 and radeonsi Gallium drivers at Mesa-18.1.6 build time. Also, some cards require Firmware to be available when the kernel driver is loaded. Firmware can be obtained from http://anduin.linuxfromscratch.org/BLFS/linux-firmware/. See the section called “Kernel Configuration for additional firmware” below for additional firmware.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-video-ati-18.0.1.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-ati-18.0.1.tar.bz2
Download MD5 sum: 40e7c0a5a69aba3d84e0958f58705ea7
Download size: 861 KB
Estimated disk space required: 19 MB
Estimated build time: 0.2 SBU
Xorg-Server-1.20.1 (recommended to be built with glamor enabled)
Glamor is required for Southern, Sea or Volcanic Islands GPUs, and used by default in all other R600 or later radeon GPUs. To see which GPUs are in these categories, read the Decoder ring for engineering vs marketing names.
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-ati-driver
Enable the following options in the kernel configuration and recompile the kernel if necessary:
Device Drivers --->
Graphics support --->
<*> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
<*> ATI Radeon [CONFIG_DRM_RADEON]
If you need to add firmware, install the file(s) and then point
to them in the kernel configuration and recompile the kernel if
necessary. To find out which firmware you need, consult the
Decoder ring for engineering vs marketing names. Download any
firmware for your card which is named like:
,
etc. Note that for R600 and R700 family, generic <ENGINEERING_NAME>
_rlc.binR600_rlc.bin
and R700_rlc.bin
are necessary in addition to the
model specific firmware, while for later generations you need the
BTC_rlc.bin
in addition to the
model specific firmware. Below is an example for a Radeon HD6470
which is a "Northern Islands" GPU, plus an RTL network chip that
also requests extra firmware:
CONFIG_EXTRA_FIRMWARE="radeon/BTC_rlc.bin radeon/CAICOS_mc.bin radeon/CAICOS_me.bin
radeon/CAICOS_pfp.bin radeon/CAICOS_smc.bin rtl_nic/rtl8168e-3.fw"
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
CONFIG_EXTRA_FIRMWARE should all be on one line. It is shown above as two lines for presentation only.
You can check dmesg output after boot to see which firmware is missing.
Alternatively, if you change CONFIG_DRM_RADEON to '=m' in your .config the firmware can be loaded automatically from /lib/firmware/radeon when it installs the module. This offers a tiny space saving, but also means that the screen will be blank for a longer time before the framebuffer appears. Distros take this approach because it is not practical to specify every possible firmware and the kernel would be excessively big.
Install Xorg ATI Driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The Xorg Fbdev Driver package contains the X.Org Video Driver for framebuffer devices. This driver is often used as fallback driver if the hardware specific and VESA drivers fail to load or are not present. If this driver is not installed, Xorg Server will print a warning on startup, but it can be safely ignored if hardware specific driver works well.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-video-fbdev-0.5.0.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-fbdev-0.5.0.tar.bz2
Download MD5 sum: f07475655376be5a124d8187aacd87b6
Download size: 292 KB
Estimated disk space required: 2.5 MB
Estimated build time: less than 0.1 SBU
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-fbdev-driver
Install Xorg Fbdev Driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The Xorg Intel Driver package contains the X.Org Video Driver for Intel integrated video chips including 8xx, 9xx, Gxx, Qxx, HD, Iris, and Iris Pro graphics processors.
This package is known to build and work properly using an LFS-8.3 platform.
This is a development version of the Intel driver which is needed to work properly with the latest hardware.
Download (HTTP): http://anduin.linuxfromscratch.org/BLFS/xf86-video-intel/xf86-video-intel-20180223.tar.xz
Download (FTP): ftp://anduin.linuxfromscratch.org/BLFS/xf86-video-intel/xf86-video-intel-20180223.tar.xz
Download MD5 sum: bca9c6bbada7dc5a19252e930c1bc587
Download size: 940 KB
Estimated disk space required: 64 MB
Estimated build time: 0.6 SBU
xcb-util-0.4.0 and Xorg-Server-1.20.1
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-intel-driver
Enable the following options in the kernel configuration. Only one of the lines “Intel I810” or “Intel 8xx/9xx...” needs to be selected. If you select the latter, “Enable modesetting...” is needed too. Recompile the kernel if necessary:
Device Drivers --->
Graphics support --->
<*> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
<*> Intel 8xx/9xx/G3x/G4x/HD Graphics [CONFIG_DRM_I915]
Install Xorg Intel Driver by running the following commands:
./autogen.sh $XORG_CONFIG \ --enable-kms-only \ --enable-uxa \ --mandir=/usr/share/man && make
This package does not come with a test suite.
Now, as the root
user:
make install && mv -v /usr/share/man/man4/intel-virtual-output.4 \ /usr/share/man/man1/intel-virtual-output.1 && sed -i '/\.TH/s/4/1/' /usr/share/man/man1/intel-virtual-output.1
The SandyBridge New Acceleration (SNA) code is intended to replace the old UXA (UMA Acceleration Architecture), but it is a large body of code and may cause problems. However, the version of the code in the version control system listed above has been tested successfully with both SNA and UXA capabilities.
To work around this problem, as well as enabling support for UXA,
it is necessary to force UXA to be used by creating a
configuration file. If this problem applies to you, create the
following file as the root
user
and modify it as needed:
cat >> /etc/X11/xorg.conf.d/20-intel.conf << "EOF"
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
#Option "DRI" "2" # DRI3 is default
#Option "AccelMethod" "sna" # default
#Option "AccelMethod" "uxa" # fallback
EndSection
EOF
--enable-kms-only
: This
switch omits the UMS (User Mode Setting) code.
--enable-uxa
: This switch
allows the old UXA code to be compiled in addition to the default
SNA.
The Xorg Nouveau Driver package contains the X.Org Video Driver for NVidia Cards including RIVA TNT, RIVA TNT2, GeForce 256, QUADRO, GeForce2, QUADRO2, GeForce3, QUADRO DDC, nForce, nForce2, GeForce4, QUADRO4, GeForce FX, QUADRO FX, GeForce 6XXX and GeForce 7xxx chipsets.
This is a development version of the Nouveau driver which is needed to build properly with the latest xorg-server.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-video-nouveau-1.0.15.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-nouveau-1.0.15.tar.bz2
Download MD5 sum: 717203cb87029cddcbccf7398f9ad8c3
Download size: 572 KB
Estimated disk space required: 14 MB
Estimated build time: 0.1 SBU
Xorg-Server-1.20.1 (recommended to be built with glamor enabled)
The new “Maxwell” and “Pascal” GPUs require Glamor to be built with the Xorg server.
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-nouveau-driver
Enable the following options in the kernel configuration and recompile the kernel if necessary:
Device Drivers --->
Graphics support --->
<*> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
<*> Nouveau (NVIDIA) cards [CONFIG_DRM_NOUVEAU]
[*] Support for backlight control [CONFIG_DRM_NOUVEAU_BACKLIGHT]
Install Xorg Nouveau Driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
Glamor is an acceleration library which uses cards' 3D capabilities to accelerate 2D rendering. Glamor acceleration is enabled by default for the new “Maxwell” GPU's. According to the documentation, Glamor acceleration can be used with other chips as well, but that does not seem functional yet.
If you want anyway to try to enable Glamor for GPU's other than
the new “Maxwell” ones,
create the following file as the root
user:
cat >> /etc/X11/xorg.conf.d/nvidia.conf << "EOF"
Section "Device"
Identifier "nvidia"
Driver "nouveau"
Option "AccelMethod" "glamor"
EndSection
EOF
The Xorg VMware Driver package contains the X.Org Video Driver for VMware SVGA virtual video cards.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://www.x.org/pub/individual/driver/xf86-video-vmware-13.3.0.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-vmware-13.3.0.tar.bz2
Download MD5 sum: 08d66d062055080ff699ab4869726ea2
Download size: 464 KB
Estimated disk space required: 12 MB
Estimated build time: 0.1 SBU
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/xorg-vmware-driver
Enable the following options in the kernel configuration and recompile the kernel if necessary:
Device Drivers --->
Graphics support --->
<*> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
<*> DRM driver for VMware Virtual GPU [CONFIG_DRM_VMWGFX]
[*] Enable framebuffer console under vmwgfx by default [CONFIG_DRM_VMWGFX_FBCON]
Install Xorg VMware Driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The libva package contains a library which provides access to hardware accelerated video processing, using hardware to accelerate video processing in order to offload the central processing unit (CPU) to decode and encode compressed digital video. The VA API video decode/encode interface is platform and window system independent targeted at Direct Rendering Infrastructure (DRI) in the X Window System however it can potentially also be used with direct framebuffer and graphics sub-systems for video output. Accelerated processing includes support for video decoding, video encoding, subpicture blending, and rendering.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://github.com/intel/libva/releases/download/2.2.0/libva-2.2.0.tar.bz2
Download MD5 sum: 92d04ad1700136dc75b1e5f47516e704
Download size: 476 KB
Estimated disk space required: 10 MB
Estimated build time: 0.1 SBU
Intel Driver Download (HTTP): https://github.com/intel/intel-vaapi-driver/releases/download/2.2.0/intel-vaapi-driver-2.2.0.tar.bz2
Intel Driver Download MD5 sum: e296c52fa1cb5c3d53a6cc994ce0a66c
Intel Driver Download size: 2.8 MB
Estimated disk space required: 99 MB
Estimated build time: 0.3 SBU
Doxygen-1.8.14 and Wayland-1.15.0
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libva
If you are reinstalling this package, you will need to remove the older versions of the libraries. These are in the form of libva*.so.1 and any symbolic links pointing to them. In addition, any packages that use these files need to be rebuilt.
Install libva by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The intel-vaapi-driver is designed specifically for video cards based on an Intel GPU. Unpack the intel-vaapi tarball using the normal procedures and install the driver by running the following commands:
./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The libvdpau package contains a library which implements the VDPAU library.
VDPAU (Video Decode and Presentation API for Unix) is an open source library (libvdpau) and API originally designed by Nvidia for its GeForce 8 series and later GPU hardware targeted at the X Window System This VDPAU API allows video programs to offload portions of the video decoding process and video post-processing to the GPU video-hardware.
Currently, the portions capable of being offloaded by VDPAU onto the GPU are motion compensation (mo comp), inverse discrete cosine transform (iDCT), VLD (variable-length decoding) and deblocking for MPEG-1, MPEG-2, MPEG-4 ASP (MPEG-4 Part 2), H.264/MPEG-4 AVC and VC-1, WMV3/WMV9 encoded videos. Which specific codecs of these that can be offloaded to the GPU depends on the version of the GPU hardware; specifically, to also decode MPEG-4 ASP (MPEG-4 Part 2), Xvid/OpenDivX (DivX 4), and DivX 5 formats, a GeForce 200M (2xxM) Series (the eleventh generation of Nvidia's GeForce graphics processing units) or newer GPU hardware is required.
This package is known to build and work properly using an LFS-8.3 platform.
Download (HTTP): https://people.freedesktop.org/~aplattner/vdpau/libvdpau-1.1.1.tar.bz2
Download MD5 sum: 2fa0b05a4f4d06791eec83bc9c854d14
Download size: 420 KB
Estimated disk space required: 9.3 MB (with tests)
Estimated build time: less than 0.1 SBU (with tests)
Doxygen-1.8.14, Graphviz-2.40.1, and texlive-20180414 or install-tl-unx
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libvdpau
Install libvdpau by running the following commands:
./configure $XORG_CONFIG \ --docdir=/usr/share/doc/libvdpau-1.1.1 && make
To test the results, issue: make check.
Now, as the root
user:
make install
The libvdpau-va-gl package contains a library which implements the VDPAU library. Libvdpau_va_gl uses OpenGL under the hood to accelerate drawing and scaling and the VA-API (if available) to accelerate video decoding. For now VA-API is available on some Intel chips, and on some AMD video adapters with the help of the libvdpau driver.
This package is known to build and work properly using an LFS-8.3 platform.
Libvdpau-va-gl Driver Download (HTTP): https://github.com/i-rinat/libvdpau-va-gl/archive/v0.4.0/libvdpau-va-gl-0.4.0.tar.gz
Libvdpau-va-gl Driver Download MD5 sum: 638244652a702d0262039890904f37ce
Libvdpau-va-gl Driver Download size: 120 KB
Estimated disk space required: 3.4 MB
Estimated build time: less than 0.1 SBU
CMake-3.12.1, FFmpeg-4.0.2, libvdpau-1.1.1, and libva-2.2.0
Doxygen-1.8.14, Graphviz-2.40.1, and texlive-20180414 or install-tl-unx
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libvdpau
Install libvdpau-va-gl by running the following commands:
mkdir build && cd build && cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=$XORG_PREFIX .. && make
To test the results, issue: make check. The tests must be run from an Xorg environment.
Now, as the root
user:
make install
To allow libvdpau to find libvdpau-va-gl, set an environment
variable. As the root
user:
echo "export VDPAU_DRIVER=va_gl" >> /etc/profile.d/xorg.sh
Last updated on 2017-05-19 11:30:22 -0700