search

Frogging-Family / nvidia-all

Nvidia driver latest to 396 series AIO installer
788 stars 69 forks source link

No Vulkan Support without using VK_ICD_FILENAMES #7

Closed gardotd426 closed 3 years ago

gardotd426 commented 3 years ago

So, I went over to the darkside and got an RTX 3090 (I know. Hush. :frog:). I used nvidia-all to install the necessary driver, and Vulkan won't work without first specifying VK_ICD_FILENAMES.

I've always used AMD GPUs, but in all my research before going to Nvidia I never saw anywhere where it was stated that you'd have to specify VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json in order to have any vulkan support.

When I put that in /etc/environment, everything works as expected, but surely that's not expected behavior, is it? Everything I've ever seen says all you need to do is install nvidia-utils, the nvidia drivers, and the 64 and 32-bit vulkan icd loader, and you'd have Vulkan support with no other tweaks.

But without specifying nvidia_icd.json, Lutris, Steam, vulkaninfo, vkcube, and all other vulkan stuff says I have no Vulkan support.

vulkaninfo go brrrrrrr with

ERROR: [Loader Message] Code 0 : /usr/lib32/amdvlk32.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /opt/amdgpu-pro/lib/i386-linux-gnu/amdvlk32.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.151/vulkaninfo/vulkaninfo.h:665:vkCreateInstance failed with ERROR_OUT_OF_HOST_MEMORY

I don't know if it's just the newness of the GPU, or what, but like I said, if I actually use VK_ICD_FILENAMES everything works fine and I get 350 fps in Doom Eternal @ 1440 so it's working flawlessly other than this.

If it's intended behavior/not your issue feel free to close

:frog:

gardotd426 commented 3 years ago

We figured it out. There's a bug in the AMD-developed vulkan drivers (amdvlk and vulkan-amdgpu-pro), which I hadn't gotten around to uninstalling yet after the switch, which causes any vulkan stuff to fail if there's no AMD GPU installed in the system. I'm going to report it to the GPUOpen repo because apparently it's not supposed to do that, it should just skip over them like it does with the intel icds.