Some of my games using vulkan stopped working after latest update

After the latest update. some of my games using vulkan stopped working or have reverted to opne gl … dota2 will not start with -vulkan option and reverts back to open gl. war thunder fails to start citing “your video card or it’s driver may not be supported. Be sure to install the best video card driver and try again” specifying -vulkan on the command line will have no effect since war thunder is vulkan only now.

vulkaninfo

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: XDG_RUNTIME_DIR not set in the environment.
==========
VULKANINFO
==========

Vulkan Instance Version: 1.2.166


Instance Extensions: count = 18
===============================
        VK_EXT_acquire_xlib_display            : extension revision 1
        VK_EXT_debug_report                    : extension revision 8
        VK_EXT_debug_utils                     : extension revision 2
        VK_EXT_direct_mode_display             : extension revision 1
        VK_EXT_display_surface_counter         : extension revision 1
        VK_KHR_device_group_creation           : extension revision 1
        VK_KHR_display                         : extension revision 23
        VK_KHR_external_fence_capabilities     : extension revision 1


```vulkaninfo | grep error
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: XDG_RUNTIME_DIR not set in the environment.
ERROR at /build/vulkan-tools/src/Vulkan-Tools-1.2.162/vulkaninfo/vulkaninfo.h:248:vkEnumeratePhysicalDeviceGroupsKHR failed with ERROR_INITIALIZATION_FAILED

i also hae other bugs now, but will report them seperately

Your post is… unreadable.

Can you please use ``` before and after your outputs?

Thanks!

is there any hope?

Please post the output of inxi -Fazy, so we get an idea of what kind of system you actually have.
Latest updates included both mesa and linux kernel updates, so chances are it has something to do with either of those.
Lastly, if you are in a hurry, you could try reverting the last update:
https://wiki.archlinux.org/index.php/Downgrading_packages

than you, here is the data requested

System:
  Kernel: 5.10.7-3-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 
  root=UUID=b1beb20b-cc4f-48d6-b4dd-8af0c2d1c655 rw quiet apparmor=1 
  security=apparmor resume=UUID=3cf867c8-0a8f-4184-8734-723e7fc75c34 
  udev.log_priority=3 nordrand 
  Desktop: KDE Plasma 5.20.5 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: Micro-Star model: MEG X570 ACE (MS-7C35) v: 1.0 
  serial: <filter> UEFI: American Megatrends v: 1.92 date: 04/23/2020 
CPU:
  Info: 8-Core model: AMD Ryzen 7 3800X bits: 64 type: MT MCP arch: Zen 2 
  family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021 
  L2 cache: 4 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 124863 
  Speed: 2237 MHz min/max: 2200/3900 MHz boost: enabled Core speeds (MHz): 
  1: 2237 2: 2064 3: 3161 4: 2084 5: 2193 6: 2199 7: 2200 8: 2194 9: 2885 
  10: 2079 11: 2199 12: 2199 13: 2203 14: 2199 15: 2215 16: 2077 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
  vendor: Gigabyte driver: amdgpu v: kernel bus ID: 2d:00.0 chip ID: 1002:67df 
  Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: 
  loaded: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa 
  display ID: :0 screens: 1 
  Screen-1: 0 s-res: 4480x1080 s-dpi: 96 s-size: 1185x285mm (46.7x11.2") 
  s-diag: 1219mm (48") 
  Monitor-1: DisplayPort-2 res: 1920x1080 hz: 60 dpi: 92 
  size: 531x298mm (20.9x11.7") diag: 609mm (24") 
  Monitor-2: HDMI-A-0 res: 2560x1080 hz: 60 dpi: 97 
  size: 673x284mm (26.5x11.2") diag: 730mm (28.8") 
  OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.40.0 
  5.10.7-3-MANJARO LLVM 11.0.1) 
  v: 4.6 Mesa 20.3.3 direct render: Yes 
Audio:
  Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] 
  vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 2d:00.1 
  chip ID: 1002:aaf0 
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 2f:00.4 chip ID: 1022:1487 
  Device-3: Creative Live! Cam Chat HD [VF0700] type: USB 
  driver: snd-usb-audio,uvcvideo bus ID: 1-2.1.1:6 chip ID: 041e:4088 
  serial: <filter> 
  Device-4: Insignia (Best Buy) Desktop Microphone NS-PAUM50 type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-2.1.4:8 
  chip ID: a014:b014 serial: <filter> 
  Sound Server: ALSA v: k5.10.7-3-MANJARO 
Network:
  Device-1: Intel I211 Gigabit Network vendor: Micro-Star MSI driver: igb 
  v: kernel port: e000 bus ID: 26:00.0 chip ID: 8086:1539 
  IF: enp38s0 state: down mac: <filter> 
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 
  v: kernel port: d000 bus ID: 27:00.0 chip ID: 10ec:8125 
  IF: enp39s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: d000 
  bus ID: 28:00.0 chip ID: 8086:2723 
  IF: wlo1 state: down mac: <filter> 
Drives:
  Local Storage: total: 4.57 TiB used: 715.59 GiB (15.3%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 PRO 512GB 
  size: 476.94 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 1B6Q 
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 PRO 512GB 
  size: 476.94 GiB block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 1B6Q 
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST2000DM008-2FR102 
  size: 1.82 TiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 0001 
  ID-4: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST2000DM008-2FR102 
  size: 1.82 TiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 0001 
Partition:
  ID-1: / raw size: 459.43 GiB size: 451.22 GiB (98.21%) 
  used: 38.49 GiB (8.5%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 
  ID-2: /boot/efi raw size: 300 MiB size: 299.4 MiB (99.80%) 
  used: 280 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 
  ID-3: /home raw size: 1.82 TiB size: 1.82 TiB (100.00%) 
  used: 677.1 GiB (36.3%) fs: btrfs dev: /dev/sdc maj-min: 8:32 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 17.21 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda3 maj-min: 8:3 
Sensors:
  System Temperatures: cpu: 60.6 C mobo: 37.0 C gpu: amdgpu temp: 46.0 C 
  Fan Speeds (RPM): fan-1: 0 fan-2: 1433 fan-3: 0 fan-4: 0 fan-5: 0 fan-6: 0 
  fan-7: 0 gpu: amdgpu fan: 709 
Info:
  Processes: 441 Uptime: 3h 36m wakeups: 0 Memory: 15.64 GiB 
  used: 4.24 GiB (27.1%) Init: systemd v: 247 Compilers: gcc: 10.2.0 
  clang: 11.0.1 Packages: 1639 pacman: 1606 lib: 439 flatpak: 25 snap: 8 
  Shell: Bash v: 5.1.0 running in: konsole inxi: 3.2.02

reading the document about downgrading, it is very scary to start with, many of us can’t afford to render our main rig inoperable. Now on a different note, it might be very beneficial to create a checkpoint file where the updated / installed packages are listed verbatim, and just pass that to the package manager. i don’t need to figure out which of the 300 updated packages need downgrading and to which versions.

Hey,

You shouldn’t do partial downgrades or upgrades really as this is a super easy way to break your system.
Some are very enamoured with timeshift though.
What you can try without any fear is a different kernel.

Give 5.4 or 5.9 a try and see if your mileage changes. I’ve heard complaints of glitchy graphics drivers from AMD and nvidia users in regards to the 5.10 kernel.

timeshift would have been interesting, but i missed out on the opportunity :wink: i am also not sure flipping the kernel around is going to have any effect on the vulkan , that is the only thing broken, apart from my “favourite” game , everything works just fine … I tried reinstalling the vulkan packages, but that didn’t do anything.

ok,
after making some tests in my old rig, i got warthunder / vulkan to work just fine there, on the same kernel version ( different distro ), i just wanted to clear the point of the kernel not being an issue without potentially upending my own main rig.

so i went back to my system, and

i uninstalled

lib32-vulkan-icd-loader
lib32-vulkan-intel
lib32-vulkan-mesa-layers
lib32-vulkan-radeon
lib32-vulkan-validation-layers

rebooted and tried to run warthunder, to my surprise steam has been removed too, so i installed it, it brought the lib32 dependencies with it, and after a very long ( about an hour ) vulkan initialization screen, warthunder started fine.

vulkaninfo | grep error
ERROR: [Loader Message] Code 0 : /usr/lib32/amdvlk32.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib32/amdvlk32.so: wrong ELF class: ELFCLASS32

so i still have the previous 2 errors, but not the third one.
now, while this may have solved my direct problem, i am still at a loss as to how this failure could have come about.

I think those elf class errors are because the game is 64-bit and can be ignored. I imagine on a 32-bit game inverse errors will be presented.

i am beginning to think that the update process failed to resolve a switch between libvulkan_radeon.so
to what is the currently installed amdvlk32.so and that caused the vulkan to detect a failed state, and the game to not run. since the rest of the system was running on opengl, nothing else was effected. so when i removed the wrong stack of vulkan drivers, and reinstalled them again as dependencies of steam, then things started working again. as to why the update failed to detect this situation and resolve it correctly, i don’t know the answer :slight_smile: