Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen der Seite angezeigt.

--- content:linux_fedora [2026/04/10 13:00] – obel1x
+++ content:linux_fedora [2026/04/10 14:22] (aktuell) – obel1x
@@ Zeile 7: / Zeile 7: @@
 ===== Graphics =====
-Out of the Box there are not all multimedia codecs installed.
+==== Basic codecs ====
+Out of the Box there are not all multimedia codecs installed which are needed to decode propietary formats.
 To use h264 and vlc, you need to:
@@ Zeile 17: / Zeile 19: @@
 </code>
 ==== Interfaces ====
-There are different interfaces that are important
+There are different Hardware/Software Interfaces that are important for Video acceleration in 2D and 3D.
-=== VA-API ===
+From [[https://wiki.archlinux.org/title/Hardware_video_acceleration|https://wiki.archlinux.org/title/Hardware_video_acceleration]] :
-This is the most used interface for video acceleration and decoding itself. The example here is a very old card still supported by AMDGPU:
+[[https://en.wikipedia.org/wiki/Graphics_processing_unit#GPU_accelerated_video_decoding_and_encoding|Hardware video acceleration]] makes it possible for the video card to decode/encode video, thus offloading the CPU and saving power.
+There are several ways to achieve this on Linux:
+  * [[https://en.wikipedia.org/wiki/Video_Acceleration_API|Video Acceleration API]] (VA-API) is a specification and open source library to provide both hardware accelerated video encoding and decoding, developed by Intel.
+  * [[https://en.wikipedia.org/wiki/VDPAU|Video Decode and Presentation API for Unix]] (VDPAU) is an open source library and API to offload portions of the video decoding process and video post-processing to the GPU video-hardware, developed by NVIDIA.
+  * [[https://gpuopen.com/advanced-media-framework/|Advanced Media Framework SDK]] (AMF) is an open source framework which allows "Optimal" access to AMD GPUs for multimedia processing, developed by AMD.
+  * [[https://en.wikipedia.org/wiki/Nvidia_NVDEC|NVDEC]]/[[https://en.wikipedia.org/wiki/Nvidia_NVENC|NVENC]] - NVIDIA's proprietary APIs for hardware video acceleration, used by NVIDIA GPUs from Fermi onwards.
+  * [[https://www.khronos.org/blog/an-introduction-to-vulkan-video|Vulkan Video]] is an extension of the [[https://wiki.archlinux.org/title/Vulkan|Vulkan]] graphics API designed to support hardware-accelerated video encoding and decoding.
+For comprehensive overview of driver and application support see [[https://wiki.archlinux.org/title/Hardware_video_acceleration#Comparison_tables|#Comparison tables]].
+=== VA-API ===
+This is the most used Interface for video acceleration and decoding itself. The example here is a very old card still supported by AMDGPU:
 <code>
 root@pc-000700080009:~# vainfo
 Trying display: wayland
@@ Zeile 55: / Zeile 72: @@
 === VDPAU ===
-This is a library, that NVIDIA is using for their video acceleration. The NIVDIA packages may still offer them.
+Basically a good way, to put load from the cpu to gpu. But:
-The Mesa-Project, which is the base-project for all desktops and many programs that did support the interfac, now does not any more, which is why that interface will die:
+The Mesa-Project, which is the base-project for all desktops and many programs that did support the interface, now does not any more, which is why that interface from Mesa will die:
 <code>
@@ Zeile 71: / Zeile 88: @@
 </code>
-You may still use it, but don't count on it on LInux in the future.
+To still be able to unload rendering to GPU, you ma y use the LIBVDPAU-VA-GL ( [[https://github.com/i-rinat/libvdpau-va-gl|https://github.com/i-rinat/libvdpau-va-gl]] ). This Library will offer VDPAU by using VA-API and OpenGL.
+See beaneath for setup.
 === Vulkan ===
@@ Zeile 78: / Zeile 97: @@
 To tes, use:
+<code>
-<code>vulkaninfo | grep VK_KHR_video_
+vulkaninfo | grep VK_KHR_video_
 </code>
@@ Zeile 90: / Zeile 110: @@
 dnf install https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
 dnf install mesa-va-drivers-freeworld --allowerasing
+dnf install libvdpau-va-gl
 </code>
-By default, most Linux deliver radeon- driver, which is open source and stable, but lacks some important features.
+By default, most Linux deliver radeon- driver, which is open source and stable, but lacks important features.
-For AMD on should switch to AMDGPU if possible (supported card by that driver).
+For AMD, one should switch to AMDGPU if possible (supported card by that driver).
 To do so:
@@ Zeile 117: / Zeile 138: @@
 </code>
+Blacklist radeon - this is needed for Vulkan ro work properly:
+<code>
+root@pc-000700080009:~# echo "blacklist radeon"> /etc/modprobe.d/blacklist-radeon.conf
+</code>
+Reboot. lsmod should than not show radeon any more.
 Environment: to make the Interfaces using the Driver
@@ Zeile 129: / Zeile 159: @@
 <file>
 LIBVA_DRIVER_NAME=radeonsi
-VDPAU_DRIVER=radeonsi
+# 10.04.2026 No support from mesa for VDPAU any more, use libvdpau-va-gl
+VDPAU_DRIVER=va_gl
 </file>
-Hint: Also the driver is changed to **AMDGPU**, you need to set **radeonsi** as value there!
+Hint: Also the driver is changed to **AMDGPU**, you need to set **radeonsi**  as value for LIBVA there!
-Hint 2: Don't expect VDPAU to work. It will still give:
+VDPAU will work via VA-API:
 <code>
+root@pc-000700080009:~# export VDPAU_DRIVER=va_gl
 root@pc-000700080009:~# vdpauinfo
 display: :0   screen: 0
-Failed to open VDPAU backend libvdpau_radeonsi.so: cannot open shared object file: No such file or directory
+libva info: VA-API version 1.22.0
-Error creating VDPAU device: 1
+libva info: User environment variable requested driver 'radeonsi'
+libva info: Trying to open /usr/lib64/dri-nonfree/radeonsi_drv_video.so
+libva info: Trying to open /usr/lib64/dri-freeworld/radeonsi_drv_video.so
+libva info: Found init function __vaDriverInit_1_22
+libva info: va_openDriver() returns 0
+API version: 1
+Information string: OpenGL/VAAPI backend for VDPAU
 </code>
-Thats because Mesa dropped VDPAU (libvdpau_radeonsi.so was part of Mesa).
+Do not install / use
-Dont use any compatiblity-layer from va api to vdpau or other way round, those are very messy and most applications should use VA-API directly:
-Do not install:
   * **libva-vdpau-driver**
-  * **libvdpau-va-gl**
+**This would be the other way round (use VA-API via VDPAU Driver!)**
 ==== Intel ====