vulkaninfo can't detect discrete gpu

[sarvalabs-akashpaul]

vulkaninfo can't detect discrete gpu

[charles-lunarg]

Whenever you set VK_ICD_FILENAMES, you are causing the loader to only search for drivers using that path. Which means that if the nvidia_icd.json fails to load, then the Vulkan-Loader cannot find any available GPUs, causing all vulkan apps to fail.

If the nvidia driver that is installed on the system isn't loading, that indicates that the nvidia driver isn't properly setup. Unfortunately, this repo isn't the place to diagnose nvidia driver installation issues. (Or rather, this doesn't appear to be a problem with vulkaninfo).

I can recommend setting the environment variable VK_LOADER_DEBUG=all to see what the loader is doing. If you could run vkcube (or any vulkan application) with that env-var set, then upload the log file, that would be helpful.

[sarvalabs-akashpaul]

here logs VK_LOADER_DEBUG=all prime-run vkcube
https://dpaste.com/4AB3TZGGD

[charles-lunarg]

/usr/share/vulkan/icd.d/amd_pro_icd64.json is the only place searched when you run the app through prime-run. That makes me think prime-run is intentionally setting environment variables that limit which drivers are used.

If you run printenv, what env-vars are present that have VK_` in their name? If you can check with both prime-run and without, that would be great.

[sarvalabs-akashpaul]

fsociety@iSSAC111 ~ $ printenv |grep VK
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json
fsociety@iSSAC111 ~ $ prime-run printenv |grep VK
__VK_LAYER_NV_optimus=NVIDIA_only
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json

[charles-lunarg]

Well, if VK_ICD_FILENAMES is set in the env, that would explain why the nvidia driver can't be used unless you set VK_ICD_FILENAMES to point to the nvidia driver.

I fear the amd driver installer set it in your setup scripts. Which is a bad thing to do, but thats only speculation.

If you unset VK_ICD_FILENAMES does vulkaninfo --summary report the nvidia driver again?

Can you review all the setup scripts (.bashrc, .profile, etc etc) to see if VK_ICD_FILENAMES was set in one of those files?

[sarvalabs-akashpaul]

found the bug

cat /etc/env.d/99amf-env-vulkan-override
VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd64.json

this is set by ffmpeg ebuild script
https://gitweb.gentoo.org/repo/gentoo.git/tree/media-video/ffmpeg/ffmpeg-6.0.1.ebuild#n603
if u set amf use flag means specifying to use amd pro drivers then script at last will install this env var

thanks for the help

[sarvalabs-akashpaul]

yes unset VK_ICD_FILENAMES also works

[charles-lunarg]

No problem!
I will close the issue since that bug isn't a Vulkan-Tools related one.
The benefit of being an open ecosystem is that everyone can do their own thing. The downside is that sometimes things DONT work well together.