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.5.1 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. Instructions for building these now unmaintained 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-7.10 platform.
Download (HTTP): http://www.freedesktop.org/software/libevdev/libevdev-1.5.4.tar.xz
Download MD5 sum: 8f22027bd7a7ba19e6f2695f78e672b6
Download size: 392 KB
Estimated disk space required: 8.2 MB (with tests)
Estimated build time: 0.3 SBU (with tests)
Check-0.10.0 (required for tests), Doxygen-1.8.11, and Valgrind-3.11.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
If you have the optional Check-0.10.0
package installed, the regression tests can be run as the
root
user with make check, in a graphical
session.
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. |
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-7.10 platform.
Download (HTTP): http://www.freedesktop.org/software/libinput/libinput-1.4.1.tar.xz
Download MD5 sum: 2e7ba577ed74d8d1baeb07dbd4fb912a
Download size: 880 KB
Estimated disk space required: 34 MB (add 10 MB for tests)
Estimated build time: 0.3 SBU (add 37 minutes for tests, not CPU dependent)
libevdev-1.5.4 and mtdev-1.1.5
Check-0.10.0 and Valgrind-3.11.0 (to run the tests), Doxygen-1.8.11 and Graphviz-2.38.0 (to build the documentation) GTK+-3.20.9 (to build the GUI event viewer), libunwind, and libwacom-0.22
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libinput
Install libinput by running the following commands:
./configure $XORG_CONFIG \ --disable-libwacom \ --with-udev-dir=/lib/udev && make
To run the tests for this package, valgrind requires a version of the /lib/ld-2.23.so (or later) library with debugging symbols present. Normally in LFS these debugging symbols are stripped at the end of Chapter 6. To get this library, glibc must be rebuilt with the current glibc version using the same compiler that was used to build LFS. The ld-2.23.so can then be renamed to ld-2.23.so.dbg and copied to /lib. Then a symlink needs to be changed:
ln -sfv ld-2.23.so.dbg /lib/ld-linux-x86-64.so.2
Adjust the above instruction as needed for a 32-bit system or for a different version of glibc
Running the testsuite for this package can cause problems. It
creates a number of dummy input devices on the currently running
system that can lead to crashing a local X server or a desktop
environment. If you understand the risks and have the optional
Check-0.10.0 and Valgrind-3.11.0 packages installed, the
regression tests can be run as the root
user with make check
. Note that depending
on the system configuration and hardware, some tests may fail.
Now, as the root
user:
make install
If Doxygen-1.8.11 and Graphviz-2.38.0 were present during the
build, you can install the generated documentation by running the
following commands as the root
user:
install -v -dm755 $XORG_PREFIX/share/doc/libinput-1.4.1 && cp -rv doc/html/* $XORG_PREFIX/share/doc/libinput-1.4.1
--disable-libwacom
:
Remove this option if you have the external library libwacom
installed.
--with-udev-dir=/lib/udev
: This
switch specifies where UDev rules and hwdb files will be
installed.
The Xorg Evdev Driver package contains 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-7.10 platform.
Download (HTTP): http://ftp.x.org/pub/individual/driver/xf86-input-evdev-2.10.3.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-input-evdev-2.10.3.tar.bz2
Download MD5 sum: aa3363ce5061d0c4d1e7f7019b99716d
Download size: 396 KB
Estimated disk space required: 5.0 MB
Estimated build time: less than 0.1 SBU
libevdev-1.5.4, mtdev-1.1.5, and Xorg-Server-1.18.4
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
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-7.10 platform.
Download (HTTP): http://ftp.x.org/pub/individual/driver/xf86-input-synaptics-1.8.3.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-input-synaptics-1.8.3.tar.bz2
Download MD5 sum: 4e3c8bed1ab4a67db2160c2c3d7e2a34
Download size: 476 KB
Estimated disk space required: 5.2 MB
Estimated build time: less than 0.1 SBU
libevdev-1.5.4 and Xorg-Server-1.18.4
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-7.10 platform.
Download (HTTP): http://ftp.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 using an LFS 7.10 platform but has not been tested.
Download (HTTP): http://downloads.sourceforge.net/linuxwacom/xf86-input-wacom-0.33.0.tar.bz2
Download MD5 sum: 4faa1d4bf6eb74f40dba8c5cb3c9c3e4
Download size: 584 KB
Estimated disk space required: 12 MB (with tests)
Estimated build time: 0.1 SBU (with tests)
Doxygen-1.8.11 and Graphviz-2.38.0
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 ATI Driver package contains the X.Org Video Driver for ATI Radeon video cards including all chipsets ranging from R100 to R900 and the newer RAxx chipsets.
This package is known to build and work properly using an LFS-7.10 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-12.0.1 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): http://ftp.x.org/pub/individual/driver/xf86-video-ati-7.7.0.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-ati-7.7.0.tar.bz2
Download MD5 sum: 59bfe0feba875c5cd28b03766aaa3b98
Download size: 810 KB
Estimated disk space required: 20 MB
Estimated build time: 0.2 SBU
Xorg-Server-1.18.4 (recommended to be built with glamor enabled)
Glamor is required for "Southern Islands" and later GPUs but optional for R300 to R700, Evergreen and "Northern Islands" GPUs - see the link in the section called “Glamor Acceleration” below.
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 --->
<*> 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 adition to the
model specific firmware, while for later generations (Evergreen,
"Northern Islands" and probably "Southern Islands") you need the
BTC_rlc.bin
in adition to the model
specific firmware. Below is an example for Radeon HD6470, which
is "Northern Islands" GPU with a network card that also requires
the 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
Glamor is an acceleration library which uses cards' 3D capabilities to accelerate 2D rendering. Glamor acceleration is required for Radeon "Southern Islands" GPUs which use "radeonsi" Gallium3D driver from Mesa-12.0.1. To see which cards fall under "Southern Islands" category, read the Decoder ring for engineering vs marketing names. Please note that Glamor acceleration can be used with other chips as well, from the R300 onwards. On at least some Northern Islands chips it is beneficial.
Glamor acceleration is not enabled by default for chipsets that
don't use "radeonsi" Gallium3D driver. You have to use an
xorg.conf
file to enable it. To
enable Glamor for cards other than "Southern Islands" and later,
create the following file in ${XORG_PREFIX}/share/X11/xorg.conf.d/
as the
root
user:
cat >> ${XORG_PREFIX}/share/X11/xorg.conf.d/20-glamor.conf << "EOF"
Section "Device"
Identifier "radeon"
Driver "ati"
Option "AccelMethod" "glamor"
EndSection
EOF
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-7.10 platform.
Download (HTTP): http://ftp.x.org/pub/individual/driver/xf86-video-fbdev-0.4.4.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-fbdev-0.4.4.tar.bz2
Download MD5 sum: 3931c0e19d441cc576dc088f9eb9fd73
Download size: 287 KB
Estimated disk space required: 2.5 MB
Estimated build time: 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 cards including 8xx, 9xx, Gxx, Qxx and HD graphics processors (SandyBridge, IvyBridge and Haswell).
This package is known to build and work properly using an LFS-7.10 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-20160902.tar.bz2
Download (FTP): ftp://anduin.linuxfromscratch.org/BLFS/xf86-video-intel/xf86-video-intel-20160902.tar.bz2
Download MD5 sum: aff145a655f96761d2ad1935c0d10ab4
Download size: 13 MB
Estimated disk space required: 88 MB
Estimated build time: 0.6 SBU
xcb-util-0.4.0 and Xorg-Server-1.18.4
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 --->
<*> Direct Rendering Manager (XFree86 ... support) ---> [CONFIG_DRM]
<*> Intel I810 [CONFIG_DRM_I810]
<*> Intel 8xx/9xx/G3x/G4x/HD Graphics [CONFIG_DRM_I915]
[*] Enable modesetting on intel by default [CONFIG_DRM_I915_KMS]
Install Xorg Intel Driver by running the following commands:
./configure $XORG_CONFIG --enable-kms-only --enable-uxa && make
This package does not come with a test suite.
Now, as the root
user:
make install
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 sometimes causes problems. In particular, when a system is built with gcc-5 and kernel headers from linux-4.0, trying to run this driver using SNA has been known to segfault on some of the supported chips. 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:
cat >> /etc/X11/xorg.conf.d/20-intel.conf << "EOF"
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
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-7.10 platform.
Download (HTTP): http://ftp.x.org/pub/individual/driver/xf86-video-nouveau-1.0.12.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-nouveau-1.0.12.tar.bz2
Download MD5 sum: dc79910c7b9e32321cefc7af250c7765
Download size: 588 KB
Estimated disk space required: 14 MB
Estimated build time: 0.1 SBU
Xorg-Server-1.18.4 (recommended to be built with glamor enabled)
The new “Maxwell” GPU requires Glamor to be built with the Xorg server. Note that the BLFS editors have not tested that hardware.
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 --->
<*> 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-7.10 platform.
Download (HTTP): http://ftp.x.org/pub/individual/driver/xf86-video-vmware-13.1.0.tar.bz2
Download (FTP): ftp://ftp.x.org/pub/individual/driver/xf86-video-vmware-13.1.0.tar.bz2
Download MD5 sum: 0cba22fed4cb639d5c4276f7892c543d
Download size: 452 KB
Estimated disk space required: 7.9 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 --->
<*> 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. 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-7.10 platform.
Download (HTTP): http://www.freedesktop.org/software/vaapi/releases/libva/libva-1.7.1.tar.bz2
Download MD5 sum: 79f98dd94daa78a026ded79fbcc137c5
Download size: 784 KB
Estimated disk space required: 20 MB
Estimated build time: 0.2 SBU
Intel Driver Download (HTTP): http://www.freedesktop.org/software/vaapi/releases/libva-intel-driver/libva-intel-driver-1.7.1.tar.bz2
Intel Driver Download MD5 sum: 91368b4647a628e8b1fe24438dd51598
Intel Driver Download size: 1.2 MB
Estimated disk space required: 37 MB
Estimated build time: 0.2 SBU
Doxygen-1.8.11 and Wayland-1.11.0
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/libva
Install libva by running the following commands:
sed -i "/seems to be moved/s/^/#/" ltmain.sh && ./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
The libva-intel-driver is designed specifically for video cards based on an Intel GPU. Unpack the libva-intel tarball using the normal procedures and install the driver by running the following commands:
autoreconf -fi && ./configure $XORG_CONFIG && make
This package does not come with a test suite.
Now, as the root
user:
make install
autoreconf -fi: This command regenerates the configure script to prevent a mandatory test for wayland-scanner when configuring. It can be omitted if Wayland-1.11.0 has been built.
sed -i ... ltmain.sh: This sed silences many annoying and useless warnings from libtool.
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-7.10 platform.
Download (HTTP): http://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.11, Graphviz-2.38.0, and texlive-20160523b 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-7.10 platform.
Download this file via wget as:
wget https://github.com/i-rinat/libvdpau-va-gl/archive/v0.4.0.tar.gz \ -O libvdpau-va-gl-0.4.0.tar.gz
Libvdpau-va-gl Driver Download (HTTP): https://github.com/i-rinat/libvdpau-va-gl/archive/v0.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.6.1, FFmpeg-3.1.3, libvdpau-1.1.1, and libva-1.7.1
Doxygen-1.8.11, Graphviz-2.38.0, and texlive-20160523b 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 2016-08-31 14:55:52 -0700