Dxvk games freeze

Hi I recently installed Garuda Sway and its been really cool overall but I'm having some issues when playing dxvk games, they freeze, when looking into the lutris logs I see this error "MESA-INTEL: error: ../mesa-21.2.3/src/intel/vulkan/anv_batch_chain.c:2053: execbuf2 failed: Error de entrada/salida (VK_ERROR_DEVICE_LOST)" and recently thins one "MESA-INTEL: error: ../mesa-21.2.3/src/intel/vulkan/anv_device.c:3713: GPU hung on one of our command buffers (VK_ERROR_DEVICE_LOST)" before installing Garuda Sway I was using Manjaro Gnome and this never happened, any idea how to fix it? From what I can see its a vulkan driver issue but I have tested vulkan-intel 21.1.2, 21.2.2 and 21.2.3 and the error persist, the only luck was with 20.2.1 that I had lying around but that has its own issues (shader flickering and volumetric effects go crazy). any idea? thanks in advice
system log here

inxi -Fazy
  Kernel: 5.14.12-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
  parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
  root=UUID=60cb14bd-f4e9-4922-8346-b077eda5aced rw rootflags=subv[email protected] quiet
  splash rd.udev.log_priority=3 vt.global_cursor_default=0
  systemd.unified_cgroup_hierarchy=1 loglevel=3
  Desktop: sway 1.6.1 vt: 1 dm: N/A Distro: Garuda Linux base: Arch Linux
  Type: Laptop System: ASUSTeK product: X453SA v: 1.0 serial: <filter>
  Mobo: ASUSTeK model: X453SA v: 1.0 serial: <filter>
  UEFI: American Megatrends v: X453SA.302 date: 04/19/2019
  ID-1: BAT0 charge: 2.5 Wh (100.0%) condition: 2.5/31.7 Wh (7.8%) volts: 7.6
  min: 7.6 model: ASUSTeK X453-42 type: Li-ion serial: N/A status: Full
  Info: Dual Core model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont
  family: 6 model-id: 4C (76) stepping: 3 microcode: 368 cache: L2: 1024 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400
  Speed: 736 MHz min/max: 480/2160 MHz Core speeds (MHz): 1: 736 2: 1860
  Vulnerabilities: Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
  IBRS_FW, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx
  Integrated Graphics
  vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:22b1
  class-ID: 0300
  Device-2: Realtek USB2.0 VGA UVC WebCam type: USB driver: uvcvideo
  bus-ID: 1-4:2 chip-ID: 0bda:57de class-ID: 0e02 serial: <filter>
  Display: wayland server: X.Org compositor: sway v: 1.6.1 driver:
  loaded: modesetting alternate: fbdev,vesa 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: XWAYLAND0 res: 1366x768 hz: 60 dpi: 112
  size: 310x170mm (12.2x6.7") diag: 354mm (13.9")
  OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (BSW) v: 4.6 Mesa 21.2.3
  compat-v: 3.0 direct render: Yes
  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series
  High Definition Audio
  vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  chip-ID: 8086:2284 class-ID: 0403
  Sound Server-1: ALSA v: k5.14.12-zen1-1-zen running: yes
  Sound Server-2: sndio v: N/A running: no
  Sound Server-3: JACK v: 1.9.19 running: no
  Sound Server-4: PulseAudio v: 15.0 running: no
  Sound Server-5: PipeWire v: 0.3.38 running: yes
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: ASUSTeK
  driver: r8169 v: kernel port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8136
  class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: Lite-On
  driver: rtl8723be v: kernel port: d000 bus-ID: 03:00.0 chip-ID: 10ec:b723
  class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
  bus-ID: 1-5:3 chip-ID: 0bda:b721 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 1 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: <filter>
  Local Storage: total: 525.24 GiB used: 365.01 GiB (69.5%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/mmcblk0 maj-min: 179:0 vendor: SanDisk model: SL64G
  size: 59.48 GiB block-size: physical: 512 B logical: 512 B type: SSD
  serial: <filter> scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: MQ01ABF050
  size: 465.76 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
  type: HDD rpm: 5400 serial: <filter> rev: 1J scheme: GPT
  ID-1: / raw-size: 24.12 GiB size: 24.12 GiB (100.00%)
  used: 16.77 GiB (69.5%) fs: btrfs dev: /dev/sda8 maj-min: 8:8
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
  used: 30.5 MiB (31.8%) fs: vfat dev: /dev/sda2 maj-min: 8:2
  ID-3: /home raw-size: 25.22 GiB size: 24.7 GiB (97.93%)
  used: 21.92 GiB (88.7%) fs: ext4 dev: /dev/sda9 maj-min: 8:9
  ID-4: /var/log raw-size: 24.12 GiB size: 24.12 GiB (100.00%)
  used: 16.77 GiB (69.5%) fs: btrfs dev: /dev/sda8 maj-min: 8:8
  ID-5: /var/tmp raw-size: 24.12 GiB size: 24.12 GiB (100.00%)
  used: 16.77 GiB (69.5%) fs: btrfs dev: /dev/sda8 maj-min: 8:8
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 3.62 GiB used: 210.9 MiB (5.7%) priority: 100
  dev: /dev/zram0
  ID-2: swap-2 type: partition size: 4 GiB used: 189.6 MiB (4.6%)
  priority: 100 dev: /dev/sda7 maj-min: 8:7
  System Temperatures: cpu: 6280.4 C mobo: 60.0 C
  Fan Speeds (RPM): cpu: 2800
  Processes: 190 Uptime: 19m wakeups: 1 Memory: 3.62 GiB
  used: 1.12 GiB (31.0%) Init: systemd v: 249 tool: systemctl Compilers:
  gcc: 11.1.0 clang: 12.0.1 Packages: pacman: 1373 lib: 377 flatpak: 0
  Shell: fish v: 3.3.1 default: Bash v: 5.1.8 running-in: alacritty
  inxi: 3.3.06

I'd start here:


then move on to here:


Also keep in mind that Lutris might also be doing things behind the scenes".

1 Like

done, it does not say anything about the error, I have been researching and I found a dxvk issue saying that is an ANV bug, I would have thought that it was already fixed given that the post was from 2018, I guess it came back. I hope mesa 21.3 fixes it.

yep it appears to be an ANV issue, i just installed "vulkan-intel-git-1 22.0.0_devel.146254.182237e1e89-1-x86_64.pkg.tar.zst" from chaotic aur and it did crash but the lutris log did not show the vk_lost_device error so I think the crash can be attributed to the bugginess of the driver in its devel state.

Someone on some linux gaming forum (I read so many can't remember where) stated that if you are a heavy linux gamer, you should stick to the "seasoned" operating systems such as Kde, Gnome, etc. I think the reason is many of the tools are built based around them, compositors, etc. Not sure if that is the issue here, but just throwing it out there.

1 Like

There's also the potential that Sway itself is causing an issue - Manjaro GNOME is quite different to Garuda Sway, so reducing the number of variables will be useful.

Correct. The Intel page provides information about the different drivers and configuration options that are available for an Intel GPU, the Vulkan page provides information about the packages that are involved in Vulkan support. The idea was that you might spot a difference with Manjaro (e.g. does it still install the intel driver rather than modesetting?).

They say this because DEs that use Wayland exclusively may not play nice with some compatibility tools needed for games. I've seen it mentioned on these forums even.

If you want the best game support, I highly recommend the Garuda KDE Dragonized Gaming Edition.

1 Like

could be, I read somewhere that the vk lost device error could be caused because the compositor was not keeping the frame(?) when switching workspaces causing that vulkan write in a null surface, but sway its so light! I dont want to have to go back to gnome, I have only 4gb of ram so the lighter it is the better

1 Like

sorry if I miss pronounce myself (dont know how to say it other way, english its not may language) what I mean is that I went to the pages search and didn't found anything useful, the only interesting thing was the vulkan gpu database where I did found my gpu. I use the vulkan-intel driver, beyond that I dont even know what is modesetting... sorry for being a noob

I wanted to install that but I dont have enough bandwith to download the iso, I am waiting to start college to donwload it

Check garuda-gamer app.

I think I fixed it, I changed the offscreen rendering from FBO to backbuffer on lutris options and it appears to be fixed, the only caveat is that it takes longer to load but between that and the game freezing I prefer waiting a few moments more. Can anyone tell me what are the differences between FBO and Backbuffer? thanks

1 Like

wonderful isn't it? you just found the solution to your problem and comes the developer and removes it on the next update, just marvelous!

1 Like

it appears that is a driver bug, I am just getting vk lost device error on almost every app that uses vulkan heavily (even on mpv!) anyone knows where I can report this?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.