From wikipedia:Vulkan (API):
- Vulkan is a low-overhead, cross-platform 3D graphics and compute API. First released in 2016, it is a successor to OpenGL.
Learn more at Khronos.
To run a Vulkan application, you will need to install the vulkan-icd-loader package (and lib32-vulkan-icd-loader if you also want to run 32-bit applications), as well as Vulkan drivers for your graphics card(s). There are several packages providing a vulkan-driver:
- Intel: vulkan-intel (or lib32-vulkan-intel)
- NVIDIA: nvidia-utils (or lib32-nvidia-utils)
- AMD: there are three implementations, which could be installed simultaneously:
- vulkan-radeon (or lib32-vulkan-radeon) - RADV (part of Mesa project)
- amdvlk (or lib32-amdvlk) - AMDVLK Open (maintained by AMD)
- vulkan-amdgpu-proAUR (or lib32-vulkan-amdgpu-proAUR) - AMDVLK Closed (maintained by AMD)
- Software: vulkan-swrast - Lavapipe (software rasteriser, only recommended for devices without Vulkan support)
For Vulkan application development, install vulkan-headers, and optionally vulkan-validation-layers and vulkan-tools (you can find the vulkaninfo tool in here).
To see which Vulkan implementations are currently installed on your system, use the following command:
$ ls /usr/share/vulkan/icd.d/
To ensure that Vulkan is working with your hardware, install vulkan-tools and use the
vulkaninfo command to pull up relevant information about your system. If you get info about your graphics card, you will know that Vulkan is working.
You can see https://linuxconfig.org/install-and-test-vulkan-on-linux for more information.
Switching between AMD drivers
On AMD systems, it is valid to have multiple Vulkan drivers installed at once, and it may be desirable to switch between them.
Selecting via environment variable
As of amdvlk 2021.Q3.4, a new switching logic was implemented which enforces AMDVLK as the default and mandates you either
AMD_VULKAN_ICD=RADVto switch from the AMDVLK default,
- or globally set
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1to re-enable the ICD loader method below.
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1, you can choose your preferred driver by setting the environment variable
VK_ICD_FILENAMES. For example, running Steam with the RADV driver is done by
$ VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json steam
To avoid crashes with 32-bit games, it is possible to assign the 32-bit variant and the 64-bit variant to the environment variable.
Selecting via AMD Vulkan Prefixes
AMD Vulkan Prefixes is a script for switching between all three Vulkan implementations. Install amd-vulkan-prefixesAUR, and prepend your application with the prefix you want. The executables provided are
vk_pro. For example, to use the AMDVLK Closed drivers:
$ vk_pro command
Software Vulkan: lavapipe
You can also install the software Vulkan rasterizer known as lavapipe: vulkan-swrast. There is no 32-bit vulkan-swrast package for now (even in AUR).
$ LIBGL_ALWAYS_SOFTWARE=1 __GLX_VENDOR_LIBRARY_NAME=mesa VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/lvp_icd.i686.json:/usr/share/vulkan/icd.d/lvp_icd.x86_64.json vulkaninfo
Vulkan hardware database
The Vulkan Hardware Database provides user reported GPU/driver combinations. Supplying own information is possible by using vulkan-caps-viewer-waylandAUR or vulkan-caps-viewer-x11AUR.
NVIDIA - vulkan is not working and can not initialize
Check if you have any other vulkan driver installed, it may prevent NVIDIA's vulkan driver from being detected.
Alternatively set the environment variable
If you have a dual-graphics system, like NVIDIA Optimus, ensure that your system is using the graphics card that you installed Vulkan drivers for.
Optimus Manager (Client) version 1.4 Current GPU mode : nvidia GPU mode requested for next login : no change GPU at startup : integrated Temporary config path: no
No device for the display GPU found. Are the intel-mesa drivers installed?
Try to list both the intel_icd and primus_vk_wrapper configurations in VK_ICD_FILENAMES
AMDGPU - ERROR_INITIALIZATION_FAILED after vulkaninfo
If after running
vulkaninfo on AMD card from GCN1 or GCN2 family you got error message like:
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.135/vulkaninfo/vulkaninfo.h:240:vkEnumerateInstanceExtensionProperties failed with ERROR_INITIALIZATION_FAILED
Then check if you have correctly enable support for this models of graphics cards (AMDGPU#Enable Southern Islands (SI) and Sea Islands (CIK) support).
One of possibility to check if gpu drivers are correctly loaded is
lspci -k, after running this command check kernel driver of your gpu. It should be
$ lspci -k
... 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] Subsystem: Gigabyte Technology Co., Ltd Device 226c Kernel driver in use: amdgpu Kernel modules: radeon, amdgpu ...
Some forum threads about this problem:  
terminate called after throwing an instance of 'dxvk::DxvkError'
Having both AMD and NVIDIA drivers can cause issues. Check with
$ pacman -Qs vulkan
local/lib32-amdvlk 2022.Q2.3-1 AMD's standalone Vulkan driver local/lib32-nvidia-utils 515.57-1 NVIDIA drivers utilities (32-bit) local/lib32-vulkan-icd-loader 1.3.221-1 Vulkan Installable Client Driver (ICD) Loader (32-bit) local/nvidia-utils 515.57-1 NVIDIA drivers utilities local/vulkan-icd-loader 1.3.221-1 Vulkan Installable Client Driver (ICD) Loader local/vulkan-tools 1.3.217-1 (vulkan-devel) Vulkan Utilities and Tools
and remove the wrong driver package.
AMDGPU - Hangs when playing DirectX Vulkan games
Radeon-Vulkan seems to cause driver and/or GPU hangs when playing some games with usage of DirectX Vulkan.
kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out! kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled ..., emitted ... kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process ... pid ... thread dxvk-submit pid ...
Switching to or enabling AMDVLK seems to fix the problem.
AMDGPU - Crashes with DirectX Vulkan games
AMDVLK has been reported as causing crashes by multiple users (see BBS#284118, BBS#283008, BBS#274737): switching to or enabling the Radeon-Vulkan driver fixes the issue.