Hi,
On my system - an HP Zbook Fury G8 with Intel UHD iGPU + Nvidia Quadro
T1200, running Sid - I think I have all the necessary GPU driver,
tools, and Vulkan pieces installed (all from the official Sid repos),
but Vulkan isn't working properly.
Vulkaninfo doesn't work when run as an ordinary user:
~$ vulkaninfo --summary
ERROR at ./vulkaninfo/./vulkaninfo.h:1413:vkGetPhysicalDeviceSurfaceSupportKHR
failed with ERROR_INITIALIZATION_FAILED
Debug messages don't seem to show the problem, just that the failure
occurs when trying the first GPU in its list, the Intel iGPU:
~$ VK_LOADER_DEBUG=all vulkaninfo --summary
...
[Vulkan Loader] DRIVER: vkCreateDevice layer callstack setup to:
[Vulkan Loader] DRIVER: <Application>
[Vulkan Loader] DRIVER: ||
[Vulkan Loader] DRIVER: <Loader>
[Vulkan Loader] DRIVER: ||
[Vulkan Loader] DRIVER: <Device>
[Vulkan Loader] DRIVER: Using "Intel(R) UHD Graphics (TGL GT1)"
with driver: "libvulkan_intel.so"
[Vulkan Loader] DEBUG | LAYER: Unloading layer library
libVkLayer_MESA_device_select.so
ERROR at ./vulkaninfo/./vulkaninfo.h:1413:vkGetPhysicalDeviceSurfaceSupportKHR
failed with ERROR_INITIALIZATION_FAILED
Vulkaninfo works fine when run as root:
~# vulkaninfo --summary
'DISPLAY' environment variable not set... skipping surface info
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.309
Instance Extensions: count = 24
...
Instance Layers: count = 4
--------------------------
VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1
VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.3.242 version 1
Devices:
========
GPU0:
apiVersion = 1.4.305
driverVersion = 25.0.5
vendorID = 0x8086
deviceID = 0x9a60
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) UHD Graphics (TGL GT1)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 25.0.5-1
conformanceVersion = 1.4.0.0
deviceUUID = 8680609a-0100-0000-0002-000000000000
driverUUID = 7361cdff-533c-3698-35b8-b33c6a136f07
GPU1:
apiVersion = 1.3.242
driverVersion = 535.247.1.0
vendorID = 0x10de
deviceID = 0x1fbc
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = NVIDIA T1200 Laptop GPU
driverID = DRIVER_ID_NVIDIA_PROPRIETARY
driverName = NVIDIA
driverInfo = 535.247.01
conformanceVersion = 1.3.5.0
deviceUUID = fd865416-f13f-50e7-3e57-03512ed070f1
driverUUID = 71e5ec5e-e2f3-57c8-97d3-cae30f2d0a98
GPU2:
apiVersion = 1.4.305
driverVersion = 0.0.1
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 19.1.7, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 25.0.5-1 (LLVM 19.1.7)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3235-2e30-2e35-2d3100000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
I don't know if the difference between running as user or as root is based on
the difference in
permissions or the difference in environment.
Vkcube runs fine (when run as an ordinary user):
~$ vkcube
Selected WSI platform: xcb
Selected GPU 1: NVIDIA T1200 Laptop GPU, type: DiscreteGpu
[spinning cube displays]
Vkmark works with the Intel iGPU but not with the Nvidia GPU:
~$ vkmark -L
=== Physical Device 0 ===
Vendor ID: 0x8086
Device ID: 0x9A60
Device Name: Intel(R) UHD Graphics (TGL GT1)
Driver Version: 104857605
Device UUID: 73eaaa764fde09d6ed1a58a171cf7249
=== Physical Device 1 ===
Vendor ID: 0x10DE
Device ID: 0x1FBC
Device Name: NVIDIA T1200 Laptop GPU
Driver Version: 2247999552
Device UUID: 3a9cdaba4ae6165f9b57921caa714bbd
=== Physical Device 2 ===
Vendor ID: 0x10005
Device ID: 0x0
Device Name: llvmpipe (LLVM 19.1.7, 256 bits)
Driver Version: 1
Device UUID: 32352e302e352d316161616161616161
~$ vkmark -D 73eaaa764fde09d6ed1a58a171cf7249
=======================================================
vkmark 2025.01
=======================================================
Vendor ID: 0x8086
Device ID: 0x9A60
Device Name: Intel(R) UHD Graphics (TGL GT1)
Driver Version: 104857605
Device UUID: 73eaaa764fde09d6ed1a58a171cf7249
=======================================================
[vertex] device-local=true:^C FPS: 13445 FrameTime: 0.074 ms
=======================================================
vkmark Score: 13445
=======================================================
=========================================
~$ vkmark -D 3a9cdaba4ae6165f9b57921caa714bbd
Segmentation fault (core dumped)
Any ideas?
--
Celejar
