FS#69289 - [amdvlk] Installing overrides all Vulkan apps to use AMDVLK by default instead of RADV
Attached to Project:
Arch Linux
Opened by Kyle Devir (QuartzDragon) - Monday, 11 January 2021, 13:51 GMT
Last edited by Laurent Carlier (lordheavy) - Saturday, 17 September 2022, 03:03 GMT
Opened by Kyle Devir (QuartzDragon) - Monday, 11 January 2021, 13:51 GMT
Last edited by Laurent Carlier (lordheavy) - Saturday, 17 September 2022, 03:03 GMT
|
Details
Description:
When AMDVLK is installed, the VK_LAYER_AMD_switchable_graphics layer is enabled by default. It queries for the "AMD_VULKAN_ICD" environment variable, with a choice between "RADV" and "AMDVLK". If the environment variable isn't set, the layer automatically causes all Vulkan application to use AMDVLK instead of RADV by default. Installing AMDVLK should not cause such behaviour, and should be left to the user. Thus, AMD_VULKAN_ICD should be set to "RADV" by default, when installing AMDVLK. Additional info: * package version ~ amdvlk 2021.Q1.1-1 * upstream bug report ~ amdvlk 2021.Q1.1-1 Steps to reproduce: 1. run `vulkaninfo | grep RADV` to confirm that RADV is being used 2. Install AMDVLK via `pacman -Sy amdvlk` 3. run `vulkaninfo | grep RADV` to confirm that RADV is no longer being used, due to AMD's VK_LAYER_AMD_switchable_graphics |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Saturday, 17 September 2022, 03:03 GMT
Reason for closing: Fixed
Saturday, 17 September 2022, 03:03 GMT
Reason for closing: Fixed
Furthermore, by default it will still filter out RADV even if VK_ICD_FILENAMES gets pointed to RADV with multiple GPUs (which includes typical AMD+Intel or AMD+AMD laptop setups) resulting in breaking this common user paradigm.
Somewhat less contentious than setting AMD_VULKAN_ICD=RADV as the initial poster suggested would be to put the implicit layer symlinks into a dedicated package so the user has to make an explicit choice for this layer.
Do you think this is related ?