Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
0 answers
321 views
Vulkan not working correctly on ubuntu 24.04
I have been trying to get lutris to work on ubuntu for the last week or so now, but there seems to be some underlying issue with Vulkan and I do not know how to proceed. I get the following error: tue@tue-desktop:~$ vulkaninfo --summary MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid arg...
I have been trying to get lutris to work on ubuntu for the last week or so now, but there seems to be some underlying issue with Vulkan and I do not know how to proceed. I get the following error: tue@tue-desktop:~$ vulkaninfo --summary MESA: error: DRM_IOCTL_VIRTGPU_GET_CAPS failed with Invalid argument MESA: error: DRM_IOCTL_VIRTGPU_CONTEXT_INIT failed with Invalid argument, continuing without context... MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_dzn.so. Skipping this driver. MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection MESA: error: DRM_VIRTGPU_RESOURCE_CREATE_BLOB failed with Invalid argument MESA: error: Failed to create virtgpu AddressSpaceStream MESA: error: vulkan: Failed to get host connection WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -4 from call to vkCreateInstance in ICD /usr/lib/x86_64-linux-gnu/libvulkan_gfxstream.so. Skipping this driver. ========== VULKANINFO ========== Vulkan Instance Version: 1.3.275 Instance Extensions: count = 24 ------------------------------- VK_EXT_acquire_drm_display : extension revision 1 VK_EXT_acquire_xlib_display : extension revision 1 VK_EXT_debug_report : extension revision 10 VK_EXT_debug_utils : extension revision 2 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_EXT_headless_surface : extension revision 1 VK_EXT_surface_maintenance1 : extension revision 1 VK_EXT_swapchain_colorspace : extension revision 5 VK_KHR_device_group_creation : extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities : extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2 : extension revision 2 VK_KHR_get_surface_capabilities2 : extension revision 1 VK_KHR_portability_enumeration : extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_surface_protected_capabilities : extension revision 1 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6 VK_LUNARG_direct_driver_loading : extension revision 1 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.277 version 1 Devices: ======== GPU0: apiVersion = 1.3.277 driverVersion = 550.144.3.0 vendorID = 0x10de deviceID = 0x2204 deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = NVIDIA GeForce RTX 3090 driverID = DRIVER_ID_NVIDIA_PROPRIETARY driverName = NVIDIA driverInfo = 550.144.03 conformanceVersion = 1.3.7.2 deviceUUID = aee333ba-b8fb-d431-c14e-b6fc5ad3df7a driverUUID = 38474641-f375-59a9-952e-301ac330fdac GPU1: apiVersion = 1.4.305 driverVersion = 0.0.1 vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 19.1.1, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe driverInfo = Mesa 25.0~git2503210600.a801a4~oibaf~n (git-a801a4a 2025-03-21 noble-oibaf-ppa) (LLVM 19.1.1) conformanceVersion = 1.3.1.1 deviceUUID = 6d657361-3235-2e30-7e67-697432353000 driverUUID = 6c6c766d-7069-7065-5555-494400000000 I have tried to search for various parts of the error message, but have not been able to figure out what is wrong or how to fix it. I have tried to update my system and reinstall the drivers, but I do not really know how vulkan works and what exactly I should be looking at in order to fix this, so any insight on how to troubleshoot this would be appreciated.
Tue (101 rep)
Apr 6, 2025, 01:45 PM
0 votes
2 answers
108 views
how do I setup VULKAN_SDK environment variables in Debian/Raspberry Pi Os
First things first; I am new to Linux and I don't understand a lot of things. I'm working on a Raspberry Pi OS which is Debian based. There is a file with environment variables: "setup-env.sh". Execute the code in the terminal: source ~/vulkan/1.x.yy.z/setup-env.sh And we are in business. Except aft...
First things first; I am new to Linux and I don't understand a lot of things. I'm working on a Raspberry Pi OS which is Debian based. There is a file with environment variables: "setup-env.sh". Execute the code in the terminal: source ~/vulkan/1.x.yy.z/setup-env.sh And we are in business.
Except after I reboot, obviously. So how can I set up these environment variables automatically at boot? I am finding a lot of answers saying : sudo ~/.bashrc. But that gives me a "command not found" error. In the Vulkan docs they advise to implement it in *.profile*. But again sudo ~/.profile is command not found on my Raspberry Pi OS. And I found out the hard way that adding a PATH to /etc/environment definitely doesn't brighten your day. It seems so simpel, but most people/tutorials skip over it with the mention "*you are on Linux to you probably know how to.*" These are the Vulkan docs if you wish to have a look: https://vulkan.lunarg.com/doc/sdk/latest/linux/getting_started.html So what is the proper way to setup the VULKAN_SDK environment variables from the setup-env.sh file at boot? Thank you sincerely! Here is the contents of the file *setup-env.sh*: # Copyright (c) 2015-2023 LunarG, Inc. # source this file into an existing shell to setup your environment. # # See docs for in depth documentation: # https://vulkan.lunarg.com/doc/sdk/latest/linux/getting_started.html ARCH="$(uname -m)" VULKAN_SDK="$(dirname "$(readlink -f "${BASH_SOURCE:-$0}" )" )/$ARCH" export VULKAN_SDK PATH="$VULKAN_SDK/bin:$PATH" export PATH LD_LIBRARY_PATH="$VULKAN_SDK/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" export LD_LIBRARY_PATH VK_ADD_LAYER_PATH="$VULKAN_SDK/share/vulkan/explicit_layer.d${VK_ADD_LAYER_PATH:+:$VK_ADD_LAYER_PATH}" export VK_ADD_LAYER_PATH if [ -n "${VK_LAYER_PATH-}" ]; then echo "Unsetting VK_LAYER_PATH environment variable for SDK usage" unset VK_LAYER_PATH fi
Desert Wind (21 rep)
Mar 7, 2025, 06:53 PM • Last activity: Mar 11, 2025, 04:12 PM
1 votes
1 answers
64 views
Bad environment variables messed up booting on Debian bassed (Raspberry Pi OS)
I set the wrong path in some environment variables, and now booting gives a whole new taste. The OS is *Raspberry Pi OS*, which is *Debian* based. **RESULT:** Right after booting, I get a black screen with a mouse. Click any mouse buttons, and I get 2 options, "**reconfigure**" and "**exit**". "Reco...
I set the wrong path in some environment variables, and now booting gives a whole new taste. The OS is *Raspberry Pi OS*, which is *Debian* based. **RESULT:**
Right after booting, I get a black screen with a mouse. Click any mouse buttons, and I get 2 options, "**reconfigure**" and "**exit**". "Reconfigure" doesn't seem to do anything. I hit "exit" and it feels like the program is being shut down and starting up again. I get a brief moment where I can do "ctrl" + "alt" + "F1" and I get to see for a brief second some command/Terminal code thingy, and then the black screen with the mouse is loaded again. (bad terminology, I'm am very new to Linux) **What I did:**
The bad thing I did was sudo nano /etc/environment and added a path to the **Vulkan_SDK** enviroment file setup-env.sh. (I had no clue how to do it), and this was incredibly stupid of me. PATH="path/to/setup-env.sh" **Content of setup-env.sh:**
# Copyright (c) 2015-2023 LunarG, Inc. # source this file into an existing shell to setup your environment. # # See docs for in depth documentation: # https://vulkan.lunarg.com/doc/sdk/latest/linux/getting_started.html ARCH="$(uname -m)" VULKAN_SDK="$(dirname "$(readlink -f "${BASH_SOURCE:-$0}" )" )/$ARCH" export VULKAN_SDK PATH="$VULKAN_SDK/bin:$PATH" export PATH LD_LIBRARY_PATH="$VULKAN_SDK/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" export LD_LIBRARY_PATH VK_ADD_LAYER_PATH="$VULKAN_SDK/share/vulkan/explicit_layer.d${VK_ADD_LAYER_PATH:+:$VK_ADD_LAYER_PATH}" export VK_ADD_LAYER_PATH if [ -n "${VK_LAYER_PATH-}" ]; then echo "Unsetting VK_LAYER_PATH environment variable for SDK usage" unset VK_LAYER_PATH fi How can I get past this, remove this line in envrionment, and get it back to "normal" again?
Desert Wind (21 rep)
Mar 6, 2025, 03:52 PM • Last activity: Mar 11, 2025, 02:54 PM
0 votes
0 answers
45 views
I have an AI program which uses Vulkan API. I want to run it on a Debian server without GPU
I have an AI program which uses Vulkan API. I want to run it on a Debian server without GPU. I know running Vulkan on CPU is possible but it's slow. What should I install/configure to have Vulkan on CPU on Debian 9? Right now I just get this error: > error while loading shared libraries: libvulkan.s...
I have an AI program which uses Vulkan API. I want to run it on a Debian server without GPU. I know running Vulkan on CPU is possible but it's slow. What should I install/configure to have Vulkan on CPU on Debian 9? Right now I just get this error: > error while loading shared libraries: libvulkan.so.1: cannot open > shared object file: No such file or directory I think I found a solution: https://github.com/google/swiftshader But I can't test it because my cmake is too old.
Tom (237 rep)
Feb 20, 2025, 09:07 PM • Last activity: Feb 21, 2025, 06:34 AM
1 votes
1 answers
2353 views
How to launch games in Dolphin: "Failed to create Vulkan surface." and "Failed to initialize video backend!"
In Debian11/KDE with Wayland I can't launch games anymore with the Dolphin emulator. Created a bug report with some more details [here][1]. Don't know if that's due to building a newer version of Dolphin than the version with which launching games worked on this machine, or due to switching from X11...
In Debian11/KDE with Wayland I can't launch games anymore with the Dolphin emulator. Created a bug report with some more details here . Don't know if that's due to building a newer version of Dolphin than the version with which launching games worked on this machine, or due to switching from X11 to Wayland. However, because for a while launching games with Dolphin still worked on it but with Lutris it didn't , I think it must be due to a newer version of Dolphin. If there's an easy way to install the version from the Debian repos without parallel to the built version, I'd try if it works with that version. I installed mesa-vulkan-drivers and then in Dolphin changed "OpenGL" to "Vulkan" in Options->Graphics Settings->Backend. When I try to launch a ROM game that used to work before, I get an error message saying Failed to create Vulkan surface. and when I close it also Failed to initialize video backend!. If I have OpenGL set as backend I only get the second error. I don't have a graphics card but the game was working fine with the same hardware earlier. I'm using i915 graphics drivers. The only output in the console is: MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0. Has anybody solved this issue or a suggestion what I should try?
mYnDstrEAm (4708 rep)
Oct 30, 2022, 10:53 AM • Last activity: Nov 22, 2024, 12:58 PM
1 votes
1 answers
1063 views
Counter Strike 2 doesn't start with the error "Failed to initialize Vulkan"
I can't launch Counter Strike 2 on my Dell laptop, with Intel Haswell-ULT graphics, running Linux Mint. When I try I get an error telling me to check if my GPU supports Vulkan 1.2+: [![enter image description here][1]][1] ``` System: Kernel: 5.15.0-113-generic x86_64 bits: 64 compiler: gcc v: 11.4.0...
I can't launch Counter Strike 2 on my Dell laptop, with Intel Haswell-ULT graphics, running Linux Mint. When I try I get an error telling me to check if my GPU supports Vulkan 1.2+: enter image description here
System:
  Kernel: 5.15.0-113-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: MATE 1.26.0
    info: mate-panel wm: marco 1.26.0 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: Dell product: Latitude E7440 v: 00 serial:  Chassis:
    type: 9 serial: 
  Mobo: Dell model: 091TRH v: A00 serial:  UEFI: Dell v: A28
    date: 06/13/2019
CPU:
  Info: dual core model: Intel Core i5-4300U bits: 64 type: MT MCP smt: enabled arch: Haswell
    rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 2694 high: 2852 min/max: 800/2900 cores: 1: 2736 2: 2594 3: 2852 4: 2595
    bogomips: 19953
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Dell driver: i915 v: kernel ports:
    active: eDP-1 empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0a16 class-ID: 0300
  Device-2: Microdia Integrated Webcam type: USB driver: uvcvideo bus-ID: 2-4:2
    chip-ID: 0c45:64d2 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") s-diag: 414mm (16.3")
  Monitor-1: eDP-1 model: Chi Mei Innolux res: 1366x768 hz: 60 dpi: 112
    size: 309x174mm (12.2x6.9") diag: 355mm (14") modes: 1366x768
  OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
    v: 4.6 Mesa 24.2~git2407100600.ae3e0a~oibaf~j (git-ae3e0ae 2024-07-10 jammy-oibaf-ppa)
    compat-v: 4.6 direct render: Yes
Audio:
  Device-1: Intel Haswell-ULT HD Audio vendor: Dell driver: snd_hda_intel v: kernel
    bus-ID: 00:03.0 chip-ID: 8086:0a0c class-ID: 0403
  Device-2: Intel 8 Series HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:9c20 class-ID: 0403
  Sound Server-1: ALSA v: k5.15.0-113-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Ethernet I218-LM vendor: Dell driver: e1000e v: kernel port: f080
    bus-ID: 00:19.0 chip-ID: 8086:155a class-ID: 0200
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: 
  Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 8086:08b1 class-ID: 0280
  IF: wlp2s0 state: down mac: 
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 port: f060
    bus-ID: 00:1f.2 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
  Local Storage: total: 465.76 GiB used: 152.01 GiB (32.6%)
  ID-1: /dev/sda vendor: Western Digital model: WD5000LPVX-75V0TT0 size: 465.76 GiB
    speed: 6.0 Gb/s type: HDD rpm: 5400 serial:  rev: 1A01 scheme: GPT
Partition:
  ID-1: / size: 456.89 GiB used: 152 GiB (33.3%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 511 MiB used: 11.9 MiB (2.3%) fs: vfat dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 235.2 MiB (11.5%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 2.0 speed: 480 Mb/s chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 speed: 480 Mb/s
    chip-ID: 8087:8000 class-ID: 0900
  Hub-3: 2-0:1 info: Hi-speed hub with single TT ports: 9 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 2-2:3 info: USB Optical Mouse type: Mouse driver: hid-generic,usbhid interfaces: 1
    rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 30fa:0300 class-ID: 0301
  Device-2: 2-4:2 info: Microdia Integrated Webcam type: Video driver: uvcvideo interfaces: 2
    rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 0c45:64d2 class-ID: 0e02
  Hub-4: 3-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 58.0 C mobo: 44.0 C sodimm: SODIMM C
  Fan Speeds (RPM): cpu: 4709
Repos:
  Packages: 2402 apt: 2393 flatpak: 9
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/microsoft-edge.list
    1: deb [arch=amd64] https: //packages.microsoft.com/repos/edge/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https: //mirror.albony.xyz/linuxmint virginia main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/oibaf-graphics-drivers-jammy.list
    1: deb [signed-by=/etc/apt/keyrings/oibaf-graphics-drivers-jammy.gpg] https: //ppa.launchpadcontent.net/oibaf/graphics-drivers/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/steam.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/steam.gpg] http: //repo.steampowered.com/steam/ stable steam
  Active apt repos in: /etc/apt/sources.list.d/vivaldi.list
    1: deb [arch=amd64] https: //repo.vivaldi.com/stable/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/winehq-focal.sources
    1: deb [arch=amd64 i386] https: //dl.winehq.org/wine-builds/ubuntu focal main
Info:
  Processes: 222 Uptime: 3h 9m wakeups: 1 Memory: 7.66 GiB used: 2.29 GiB (29.9%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
  inxi: 3.3.13
Result from vulcaninfo:
-shellsession
$ vulcaninfo | grep "Vulkan Instance Version" 

WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 2. 

Skipping ICD. WARNING: [Loader Message] Code 0 : terminator_CreateInstance:

 Failed to CreateInstance in ICD 4. Skipping ICD. 

MESA-INTEL: warning: Haswell Vulkan support is incomplete

 Vulkan Instance Version: 1.3.20
noerror (43 rep)
Jul 10, 2024, 10:31 AM • Last activity: Jul 12, 2024, 03:35 PM
1 votes
1 answers
268 views
Gnome Shell display error in Arch Linux / Problem with old Intel graphics card
In a fresh Arch Linux Installation with Gnome occurring display errors on specific applications. I have reinstalled Arch Linux (archlinux-2024.01.01-x86_64.iso) due to display errors after an update using "pacman -Syu" on January 2, 2024. On Apps like Console, Nautilus: - The application window flic...
In a fresh Arch Linux Installation with Gnome occurring display errors on specific applications. I have reinstalled Arch Linux (archlinux-2024.01.01-x86_64.iso) due to display errors after an update using "pacman -Syu" on January 2, 2024. On Apps like Console, Nautilus: - The application window flickers. - In particular, the window-backgroundcolor is missing and the controls ("X" for close) are missing. - There are streaks when moving the window. Unfortunately, the same display errors also occur in the fresh installation. With other applications, such as Gnome-Optimizations or Firefox, these display errors do not occur. What I have done so far Alternatively, I installed Arch Linux with Cinnamon and did not get these display errors. However, I would like to get Gnome working again. System: - Notebook: Lenovo B560 (Family: IDEAPAD) - Processor: Pentium P6100, 2 GHz - RAM: 3 GB - Graphic: Intel integrated Graphic Controller, rev. 02 - Kernel Driver in use: i915 Until this update attempt, this system worked flawlessly. Does anyone have an idea how I can solve this problem?Until this update attempt, this system worked flawlessly Best Regards
JD38292 (31 rep)
Jan 5, 2024, 05:05 PM • Last activity: Jan 6, 2024, 11:12 PM
0 votes
1 answers
59 views
Vulcan detecting GPU on TTY but not on gnome
I am on Debian 11 I have a program that works by overriding tty1. So when starting my computer, the program runs right away. This works fine, but I use Gnome as my GUI to develop and test the program. When running the program while in Gnome I get: WARNING: lavapipe is not a conformant vulkan impleme...
I am on Debian 11 I have a program that works by overriding tty1. So when starting my computer, the program runs right away. This works fine, but I use Gnome as my GUI to develop and test the program. When running the program while in Gnome I get: WARNING: lavapipe is not a conformant vulkan implementation, testing use only. Segmentation fault Running vulkaninfo --summary over tty outputs Devices: ======== GPU0: apiVersion = 420641 (1.2.145) driverVersion = 83898373 vendorID = 0x10002 deviceID = 0x1508 deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU deviceName = AMD_RADV_RAVEN *ACO) driverID = DRIVER_ID_MESA_RADV driverName = radv driverInfo = Mesa 20.3.5 (ACO) conformanceVersion = 1.2.3.0 GPU1: apiVersion = 4194306 (1.0.2) driverVersion = 1 (0x0001) vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 11.0.1, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe but running vulkaninfo --summary over gnome outputs Devices: ======== GPU0: apiVersion = 4194306 (1.0.2) driverVersion = 1 (0x0001) vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 11.0.1, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe driverInfo = Mesa 20.3.5 (LLVM 11.0.1) conformanceVersion = 1.0.0.0 driverInfo = Mesa 20.3.5 (LLVM 11.0.1) conformanceVersion = 1.0.0.0 So I can see that in Gnome it's just using my CPU. Is there any way to configure vulkan to also use my GPU?
fwan (11 rep)
Dec 11, 2023, 03:52 PM • Last activity: Dec 11, 2023, 05:02 PM
1 votes
1 answers
1623 views
How to force Vulkan applications to NOT use Nvidia proprietary GPU?
I have a laptop with two GPUs, a AMD integrated one and a headless Nvidia chip. According to [the Nvidia documentation](https://download.nvidia.com/XFree86/Linux-x86_64/515.86.01/README/primerenderoffload.html), setting the environment variable `__NV_PRIME_RENDER_OFFLOAD=1` will cause the Nvidia GPU...
I have a laptop with two GPUs, a AMD integrated one and a headless Nvidia chip. According to [the Nvidia documentation](https://download.nvidia.com/XFree86/Linux-x86_64/515.86.01/README/primerenderoffload.html) , setting the environment variable __NV_PRIME_RENDER_OFFLOAD=1 will cause the Nvidia GPU to appear first to applications, __VK_LAYER_NV_optimus=NVIDIA_only will hide other GPUs, forcing applications to use the Nvidia one, and __VK_LAYER_NV_optimus=non_NVIDIA_only will hide Nvidia GPUs. The former option works fine, but the latter option only adjusts the order, instead of hiding anything:
$ __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=non_NVIDIA_only vulkaninfo --summary | grep deviceName
        deviceName         = AMD Radeon Graphics (RADV RENOIR)
        deviceName         = NVIDIA GeForce RTX 3050 Ti Laptop GPU
        deviceName         = llvmpipe (LLVM 15.0.6, 256 bits)
$ __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only vulkaninfo --summary | grep deviceName
        deviceName         = NVIDIA GeForce RTX 3050 Ti Laptop GPU
        deviceName         = AMD Radeon Graphics (RADV RENOIR)
        deviceName         = llvmpipe (LLVM 15.0.6, 256 bits)
Indeed, with the latter option set, many applications still default to the (higher-performance) Nvidia GPU:
$ __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=non_NVIDIA_only vkcube
Selected GPU 1: NVIDIA GeForce RTX 3050 Ti Laptop GPU, type: DiscreteGpu
This is with Nvidia driver version 515.86.01, the one that currently ships with Debian testing. **How to get applications to only see the integrated GPU**?
whoKnows (138 rep)
Jun 4, 2023, 12:14 AM • Last activity: Jun 7, 2023, 03:53 PM
1 votes
1 answers
239 views
vulkan build error : 'createResultValue' is not a member of 'vk'
I'm trying to compile a program that uses vulkan hpp and it uses a method in a file named vulkan_driver.h like this: // Evaluate f and if result is not a success throw proper vk exception. #define CHECK_VK_RESULT(x) do { \ vk::Result res = vk::Result(x); \ int tmp = 0; \ vk::createResultValue(res, t...
I'm trying to compile a program that uses vulkan hpp and it uses a method in a file named vulkan_driver.h like this: // Evaluate f and if result is not a success throw proper vk exception. #define CHECK_VK_RESULT(x) do { \ vk::Result res = vk::Result(x); \ int tmp = 0; \ vk::createResultValue(res, tmp, __FILE__ ":" TOSTRING(__LINE__)); \ } while (0) when i compile i get the following error: [ 199s] In file included from /home/abuild/rpmbuild/BUILD/decaf-emu-20220508T212126/src/libgpu/src/vulkan/vulkan_driver.cpp:2: [ 199s] /home/abuild/rpmbuild/BUILD/decaf-emu-20220508T212126/src/libgpu/src/vulkan/vulkan_driver.cpp: In member function 'void vulkan::Driver::initialise(vk::Instance, vk::PhysicalDevice, vk::Device, vk::Queue, uint32_t)': [ 199s] /home/abuild/rpmbuild/BUILD/decaf-emu-20220508T212126/src/libgpu/src/vulkan/vulkan_driver.h:36:8: error: 'createResultValue' is not a member of 'vk'; did you mean 'createResultValueType'? [ 199s] 36 | vk::createResultValue(res, tmp, __FILE__ ":" TOSTRING(__LINE__)); \ [ 199s] | ^~~~~~~~~~~~~~~~~ [ 199s] /home/abuild/rpmbuild/BUILD/decaf-emu-20220508T212126/src/libgpu/src/vulkan/vulkan_driver.cpp:89:4: note: in expansion of macro 'CHECK_VK_RESULT' [ 199s] 89 | CHECK_VK_RESULT(vmaCreateAllocator(&allocatorCreateInfo, &mAllocator)); [ 199s] | ^~~~~~~~~~~~~~~ [ 199s] make: *** [src/libgpu/CMakeFiles/libgpu.dir/build.make:647: src/libgpu/CMakeFiles/libgpu.dir/src/vulkan/vulkan_driver.cpp.o] Error 1 How can I fix this error?
Ahmed Moselhi (35 rep)
Apr 11, 2023, 09:49 PM • Last activity: Apr 18, 2023, 11:17 AM
2 votes
0 answers
458 views
Why does vkd3d not work in wine?
I am fairly new to this world, but finally decided to switch from windows and learn the command line in Linux. I also want to play games on it, because my PC isn't the strongest. I installed Lutris and Epic Games Launcher on my fedora 37 pc. Then I installed Death Stranding, but when I opened it I g...
I am fairly new to this world, but finally decided to switch from windows and learn the command line in Linux. I also want to play games on it, because my PC isn't the strongest. I installed Lutris and Epic Games Launcher on my fedora 37 pc. Then I installed Death Stranding, but when I opened it I got this error message from wine: > CallStack : 2642518428 > > Your graphics card NVIDIA GeForce GTX 1060 does not support DirectX12 > features !Referenced image It ran on windows though, so I tried turning off DXVK in the runner options in Lutris Epic Games Lanucher configuration. Then I installed the NVIDIA driver for linux from https://www.nvidia.com/download/index.aspx because I thought maybe the driver is the problem. I read a lot about this on the internet, but I didn't find anything that worked. Can I solve this problem?
amnesia (21 rep)
Mar 25, 2023, 01:14 PM
7 votes
0 answers
2632 views
How does flatpak provide access to Vulkan / GPU
I am running the flatpak version of Steam, and it happens that my system has two discrete GPUs, a nvidia one and a lowend AMD one. Normally Steam opens proton games and it uses the nvidia card for running Vulkan, but sometimes, specially after some upgrade, it uses the AMD one. I have tried to under...
I am running the flatpak version of Steam, and it happens that my system has two discrete GPUs, a nvidia one and a lowend AMD one. Normally Steam opens proton games and it uses the nvidia card for running Vulkan, but sometimes, specially after some upgrade, it uses the AMD one. I have tried to understand which GPU is passed to the flatpak container, or if both, how it decides which ones to use, but apparently there is no Vulkan ICD loader in the flatpak container. How does flatpak provides access to the GPUs of the host system? How can I enforce to use one or another?
jjcasmar (353 rep)
Feb 21, 2023, 05:37 PM
1 votes
0 answers
923 views
Vulkan, DRI, X11, and KMS: how do they relate?
I think I have a decent understanding of the chain of software that gets graphics code from a program to your hardware, but I would like someone to correct me on any mistakes. When I write a program (in C, let's say) that uses Vulkan to render and present a 3D scene, I have to link to `libvulkan`. `...
I think I have a decent understanding of the chain of software that gets graphics code from a program to your hardware, but I would like someone to correct me on any mistakes. When I write a program (in C, let's say) that uses Vulkan to render and present a 3D scene, I have to link to libvulkan. libvulkan actually just dispatches my commands to the Vulkan library for my platform. This library makes calls into libdrm which talks to the kernel driver using the /dev/dri/renderX interface. This driver then interacts with my hardware. To recap:
program -> libvulkan -> libvulkan_platform -> libdrm -> /dev/dri/renderX -> kernel drm driver -> hardware
Is this correct? In addition, once the GPU has rendered my frames, they need to be presented on the screen. This is done by sending them to the platform's window library (X11, wayland, etc) using the Vulkan window system integration (WSI) layer. However, when I write programs in Vulkan, I also use glfw. where does it come in? The window server then has to display the composited frames on the display, also using libdrm. it interacts with the kernel KMS driver through the /dev/dri/cardX interface, which then interacts with the hardware. To recap:
program -> libvulkan (wsi) -> glfw??? -> libX11, libwayland-client -> X server (Xorg) + modesetting_drv, Wayland compositor -> libdrm -> /dev/dri/cardX -> platform KMS driver -> hardware
Is this correct?
Lennon McLean (326 rep)
Jan 18, 2023, 03:00 AM
0 votes
0 answers
284 views
Vulkan issue on AMD 5700G CPU onboard Radeon....'amdgpu'?
I have an AMD Ryzen 5700G and I tried installing Wine, however when I launch it I get "0074:err:vulkan:wine_vk_init Failed to load vulkan library". I'm running Debian 10 with an updated kernel, which so far has been fine. Then when it loads and I try to run project64 it that programme won't run, so...
I have an AMD Ryzen 5700G and I tried installing Wine, however when I launch it I get "0074:err:vulkan:wine_vk_init Failed to load vulkan library". I'm running Debian 10 with an updated kernel, which so far has been fine. Then when it loads and I try to run project64 it that programme won't run, so I think there's something wrong with vulkan. I've tried installing everything and modifying grub from what I've read online, but when I run vulkaninfo I still get the following: ========== VULKANINFO ========== Vulkan Instance Version: 1.1.97 amdgpu: Invalid PCI ID. amdgpu: Invalid PCI ID. /build/vulkan-tools-6bmpQy/vulkan-tools-1.1.97+dfsg1/vulkaninfo/vulkaninfo.c:3845: failed with VK_ERROR_INITIALIZATION_FAILED What testing can I do to further narrow down the issue, to rectify it? Thanks very much!!
1toneboy (465 rep)
Jan 16, 2023, 10:30 AM
0 votes
1 answers
687 views
Error running vulkan with iGPU
When I execute `vulkaninfo` I get this following error ``` WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 1. Skipping ICD. WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 5. Skipping ICD. vulkaninfo: symbol...
When I execute vulkaninfo I get this following error
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 1.  Skipping ICD.
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 5.  Skipping ICD.
vulkaninfo: symbol lookup error: /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so: undefined symbol: amdgpu_query_video_caps_info
I tried updating the packages and I installed the following ones
sudo apt install vulkan-amdgpu 
sudo apt install vulkan-amdgpu-pro
sudo apt install mesa-vulkan-drivers
even after updating and upgrading the packages and rebooting the system it is not working output of lshw -c video
*-display                 
       description: VGA compatible controller
       product: Renoir
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:04:00.0
       version: c3
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
       configuration: driver=amdgpu latency=0
       resources: irq:57 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:e000(size=256) memory:fe600000-fe67ffff
CPU: AMD Ryzen 5 4500U with Radeon Graphics (6) @ 2.375GHz 
GPU: AMD ATI 04:00.0 Renoir
binary_psychic (1 rep)
Oct 4, 2022, 07:35 PM • Last activity: Oct 4, 2022, 07:59 PM
0 votes
1 answers
1123 views
Vulkan not working
( Also on [Nvidia forum][1] ) Fedora 36 with Gnome 42.2, everything up to date Nvidia's latest proprietary drivers (515.57) Nvidia Geforce GTX 745 and Intel Core i5-6400 (no integrated graphics) Problem first occurred when launching Harry Potter and the Goblet of Fire through Lutris (flatpak). I get...
( Also on Nvidia forum ) Fedora 36 with Gnome 42.2, everything up to date Nvidia's latest proprietary drivers (515.57) Nvidia Geforce GTX 745 and Intel Core i5-6400 (no integrated graphics) Problem first occurred when launching Harry Potter and the Goblet of Fire through Lutris (flatpak). I get a terrible framerate and upon launching Lutris (flatpak) through a terminal, I receive these errors: libEGL warning: DRI3: Screen seems not DRI3 capable libEGL warning: DRI2: failed to authenticate libEGL warning: DRI3: Screen seems not DRI3 capable libEGL warning: DRI2: failed to authenticate Error: couldn't find RGB GLX visual or fbconfig 2022-07-09 12:29:21,250: Invalid glxinfo received And after 2022-07-09 12:29:21,644: Startup complete: 2022-07-09 12:31:05,686: Unable to load libGLX_nvidia.so.0 2022-07-09 12:31:05,686: Unable to locate libGLX_nvidia As soon as I run the game, I get this error while the game continues to run at a terrible framerate: WARNING: lavapipe is not a conformant vulkan implementation, testing use only. This seems like my Vulkan drivers are messed up, so I tried to run OMORI through Lutris (RPM) and instantly receive these errors and the game refuses to start: enter image description here enter image description here Trying to launch anyway gives me the normal Gnome application crash message ("Oops! We're sorry, it looks like OMORI crashed...") Here's the output of glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Memory info (GL_NVX_gpu_memory_info): Dedicated video memory: 4096 MB Total available memory: 4096 MB Currently available dedicated video memory: 3883 MB OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce GTX 745/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 515.57 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6.0 NVIDIA 515.57 OpenGL shading language version string: 4.60 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 515.57 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 Here's the output of vulkaninfo 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 /builddir/build/BUILD/Vulkan-Tools-sdk-1.3.204.0/vulkaninfo/vulkaninfo.h:649:vkCreateInstance failed with ERROR_INCOMPATIBLE_DRIVER lspci -k shows that my GPU is using the "nvidia" driver like it's supposed to. I checked through /usr/share/vulkan/icd.d/ and /etc/vulkan/icd.d/ and both of them were empty. Could this be the problem? How could I get my graphics thingies working?
tempacc (357 rep)
Jul 9, 2022, 09:47 AM • Last activity: Jul 9, 2022, 10:31 PM
2 votes
0 answers
832 views
Wine 6 cannot start the game when render = vulkan
Wine 6 introduces experimental Vulkan renderer. However when I try to execute a game having that renderer set I get the following error: ``` 0024:err:winediag:wined3d_dll_init Using the Vulkan renderer. 0024:err:winediag:wined3d_spirv_shader_backend_init_vk Wine was built without libvkd3d-shader sup...
Wine 6 introduces experimental Vulkan renderer. However when I try to execute a game having that renderer set I get the following error:
0024:err:winediag:wined3d_dll_init Using the Vulkan renderer.
0024:err:winediag:wined3d_spirv_shader_backend_init_vk Wine was built without libvkd3d-shader support.
I installed wine from deb https://dl.winehq.org/wine-builds/ubuntu/ focal main. The same is reproducible for stable and devel builds. Is there a way to get workable wine build having vulkan renderer supported?
Alexey R. (121 rep)
Feb 2, 2021, 07:04 PM • Last activity: Aug 23, 2021, 04:30 AM
0 votes
0 answers
202 views
Why game lagging?
I played in dota 2 at Windows perfectly, but at linux (Manjaro, Arch, Ubuntu, Linux mint and Fedora) it's lagging, fps dropping and frametime jumping + some issues with grass textures. Game on SSD (Filesystem: EXT4) Fedora at other SSD (Filesystem: BTRFS). My PC: CPU: i3-8100 GPU: AMD RX580 4GB RAM:...
I played in dota 2 at Windows perfectly, but at linux (Manjaro, Arch, Ubuntu, Linux mint and Fedora) it's lagging, fps dropping and frametime jumping + some issues with grass textures. Game on SSD (Filesystem: EXT4) Fedora at other SSD (Filesystem: BTRFS). My PC: CPU: i3-8100 GPU: AMD RX580 4GB RAM: 16GB All updates installed. I record video with mangohud. video
Lexa Berezin (11 rep)
May 12, 2021, 01:33 PM
0 votes
0 answers
50 views
I can't enter my fedora system
Yesterday I was messing around with android emulator setup. I tried some commands, but to be honest I don’t remember everything I did. Overall, it has something to do with video card driver settings. Among other things, I removed vulkan library. After I restarted my computer, my login screen looks l...
Yesterday I was messing around with android emulator setup. I tried some commands, but to be honest I don’t remember everything I did. Overall, it has something to do with video card driver settings. Among other things, I removed vulkan library. After I restarted my computer, my login screen looks like that: here is how my login screen looks like now It’s different from what I had before, and there is no way I can enter my system. I press "enter" but nothing happens. What options do I have to fix that? Can I enter my system somehow? Or can I recover it? Or can I install new fedora so that I can use all of the data and installed programs?
Vadim Samokhin (155 rep)
Apr 27, 2021, 09:22 AM
0 votes
1 answers
873 views
Running a singular application on startup, fullscreened
I want to run a single application, specifically a Vulkan game, on Linux. I kind of want it to be like a kiosk, but not just for displaying information. The operating system's one use for me is to run this application. How exactly do I do this? I am new to Linux, so I don't know much about how to wo...
I want to run a single application, specifically a Vulkan game, on Linux. I kind of want it to be like a kiosk, but not just for displaying information. The operating system's one use for me is to run this application.
How exactly do I do this? I am new to Linux, so I don't know much about how to work with it.
Kevin-Duel Trimble (103 rep)
Apr 7, 2021, 03:36 PM • Last activity: Apr 8, 2021, 12:43 AM
Showing page 1 of 20 total questions