You are not logged in.
Pages: 1
I can't for the life of me get amdvlk to load as a driver (looking to test ray tracing support). Mesa and amdgpu-pro work fine. When I install amdvlk all applications segfault or coredump.
Here's the error I get when I run vulkaninfo:
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateI>
ERROR: [Loader Message] Code 0 : terminator_CreateInstance: Found no drivers!
Cannot create Vulkan instance.
This problem is often caused by a faulty installation of the Vulkan driver or a>
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.3.226/vulkaninfo/vulkaninfo.h:6>This is on a new Ryzen 7600x system with a B650 AM5 board. I'm thinking there is some conflict with the onboard gpu on the 7600x, as this didn't happen when I was running a 12600k. For reference, the newer AM5 chips all include a small integrated gpu on the chip, the GFX1036 "Raphael." When I run vulkaninfo and either the Mesa drivers or the amdgpu-pro drivers are loaded the output is:
VK_LAYER_AMD_switchable_graphics_32 (AMD switchable graphics layer) Vulkan version 1.3.235, layer version 1:
Layer Extensions: count = 0
Devices: count = 2
GPU id = 0 (AMD Radeon RX 6650 XT)
Layer-Device Extensions: count = 0
GPU id = 1 (AMD Radeon Graphics)
Layer-Device Extensions: count = 0
VK_LAYER_AMD_switchable_graphics_64 (AMD switchable graphics layer) Vulkan version 1.3.235, layer version 1:
Layer Extensions: count = 0
Devices: count = 2
GPU id = 0 (AMD Radeon RX 6650 XT)
Layer-Device Extensions: count = 0
GPU id = 1 (AMD Radeon Graphics)
Layer-Device Extensions: count = 0I can't fully disable the onboard iGPU in the bios, weirdly. I have updated to the latest bios for the board, which is a Asrock B650M Riptide. I was thinking this was a kernel bug but even after trying a drm-next kernel it persists.
Offline
This sounds like it is related to the very limited switching options VK_LAYER_AMD_switchable_graphics_* provide .
Verify you have vulkan-mesa-layers, install it if isn't present.
Then set DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 to disable the amd switching layers.
run vulkaninfo --summary , I expect it to show all installed drivers/vulkan devices now.
If things still don't work, try the AMD Vulkan Prefixes script , see https://wiki.archlinux.org/title/Vulkan … n_Prefixes
Welcome to archlinux forums
Last edited by Lone_Wolf (2022-12-16 11:18:30)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
This sounds like it is related to the very limited switching options VK_LAYER_AMD_switchable_graphics_* provide .
Verify you have vulkan-mesa-layers, install it if isn't present.
Then set DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 to disable the amd switching layers.
run vulkaninfo --summary , I expect it to show all installed drivers/vulkan devices now.
If things still don't work, try the AMD Vulkan Prefixes script , see https://wiki.archlinux.org/title/Vulkan … n_Prefixes
I feel like this is getting there a bit. When I disable switching using the environment variable it will correctly default to RADV if amdvlk is not working. However, it still fails if asking it explicitly to use amdvlk. For instance:
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 vk_amdvlk vulkaninfo
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 0. Skipping ICD.
ERROR: [Loader Message] Code 0 : terminator_CreateInstance: Found no drivers!
Cannot create Vulkan instance.
This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that does not support Vulkan.
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.3.226/vulkaninfo/vulkaninfo.h:672:vkCreateInstance failed with ERROR_INCOMPATIBLE_DRIVERMaybe I can report it to upstream? I wish I knew more about Vulkan in general but there's just not a lot of accessible information. Thanks for your help.
Offline
I doubt vulkaninfo works when forcing a specific vulkan driver with the vulkan prefix script .
Please post the output of
$ export DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1
$ vulkaninfo --summaryFor a basic test if vulkan works , vkcube is useful .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Pages: 1