Most Vulkan applications begin by enumerating all devices in the system and selecting one or more based on their capabilities. Currently, the NVIDIA driver must power on GPUs to discover their capabilities during this enumeration phase. The engineering team is investigating methods to perform these operations without powering on the GPU, but we cannot commit to an ETA for such a solution at this time.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| GPU randomly fails to wake up from D3Cold | 2 | 350 | October 18, 2024 | |
| 570 release feedback & discussion | 657 | 49706 | October 11, 2025 | |
| How to deal with nvidia-modprobe when switching between nvidia/nouveau | 9 | 9457 | December 30, 2023 | |
| NVIDIA driver 440.44 / Vulkan vulkaninfo reports too many GPUs | 3 | 868 | October 12, 2021 | |
| vulkan failed to initialize with 440.36 on ubuntu 18.04 | 8 | 5138 | October 12, 2021 | |
| Crash on Wayland with Vulkan apps | 11 | 888 | March 7, 2024 | |
| VK_KHR_present_{id,wait} causes device loss on Nvidia 525.60.11 on PRIME setup | 5 | 2602 | March 25, 2023 | |
| Vulkaninfo failure when using cgroups to limit GPUs on CUDA11.2 driver | 1 | 1388 | April 22, 2021 | |
| Trouble using dGPU acceleration with Vulkan (Driver 470, Mesa 20.8, Loader 1.3.224) | 1 | 778 | October 19, 2022 | |
| Headless Vulkan with multiple GPUs | 22 | 5997 | October 24, 2025 |