You are not logged in.

#1 2022-05-19 11:34:19

nullelement
Member
Registered: 2022-05-18
Posts: 3

Vulkan Wayland WSI broken after system upgrade

Hi all

I recently did a system upgrade with 'pacman -Syu' and since then I'm unable to run any Vulkan program using the Wayland WSI.
Any attempt to create a swapchain returns VK_ERROR_INITIALIZATION_FAILED.
At first I though it was my own program, however the same happens with vkcube-wayland.
vkcube running though XWayland runs just fine.

Steps taken with no effect:
- Reinstalling packages
- Installed the nvidia beta packages from the AUR
- Installed the vulkan git packages from the AUR
- Tested on Sway and GNOME

Log of relevant packages upgraded:

[2022-05-18T07:24:47+0100] [ALPM] upgraded nvidia-utils (510.68.02-1 -> 515.43.04-1)
[2022-05-18T07:24:47+0100] [ALPM] upgraded vulkan-icd-loader (1.3.209-1 -> 1.3.213-1)
[2022-05-18T07:25:13+0100] [ALPM] upgraded lib32-vulkan-icd-loader (1.3.209-1 -> 1.3.213-1)
[2022-05-18T07:25:13+0100] [ALPM] upgraded lib32-nvidia-utils (510.68.02-1 -> 515.43.04-1)
[2022-05-18T07:25:35+0100] [ALPM] upgraded nvidia (510.68.02-3 -> 515.43.04-4)
[2022-05-18T07:25:36+0100] [ALPM] upgraded nvidia-settings (510.68.02-1 -> 515.43.04-1)
[2022-05-18T07:26:12+0100] [ALPM] upgraded vulkan-headers (1:1.3.212-1 -> 1:1.3.213-1)
[2022-05-18T07:26:12+0100] [ALPM] upgraded vulkan-tools (1.3.207-1 -> 1.3.213-1)
[2022-05-18T07:26:13+0100] [ALPM] upgraded vulkan-validation-layers (1.3.204.1-1 -> 1.3.211.0-1)

Running dmesg:

[   96.994620] vkcube-wayland[1341]: segfault at 108 ip 00007f8e187e6cc3 sp 00007ffc22ecbbd8 error 4 in libnvidia-glcore.so.515.43.04[7f8e17600000+1cf8000]
[   96.994632] Code: 10 ba 08 00 00 00 4c 89 f6 41 ff d0 48 89 c1 e9 6b ff ff ff 48 c7 83 00 05 00 00 00 00 00 00 e9 a1 fc ff ff 0f 1f 00 48 85 d2 <44> 8b 87 08 01 00 00 74 54 44 39 06 44 0f 46 06

Can anybody confirm that they have the same issue as me, and if there is any solution?

System:
DE: KDE Plasma 5.24.5
Kernel: 5.17.8-arch1-1
GPU: Nvidia GTX 970

Last edited by nullelement (2022-05-19 12:05:25)

Offline

#2 2022-05-25 12:39:59

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,142

Re: Vulkan Wayland WSI broken after system upgrade

I'm not familiar with wayland WSI , could you explain what that is ?

Please post the output of

$ lspci -k
$ vulkaninfo --summary

Welcome to archlinux forum

Last edited by Lone_Wolf (2022-05-25 12:40:11)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#3 2022-05-25 14:03:24

progandy
Member
Registered: 2012-05-17
Posts: 4,966

Re: Vulkan Wayland WSI broken after system upgrade

Lone_Wolf wrote:

I'm not familiar with wayland WSI , could you explain what that is ?

It stands for window system integration. I'd guess either https://gitlab.freedesktop.org/mesa/vulkan-wsi-layer or the VK_KHR_wayland_surface vulkan /extension.

Last edited by progandy (2022-05-25 14:11:54)


| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |

Offline

#4 2022-05-29 17:06:17

nullelement
Member
Registered: 2022-05-18
Posts: 3

Re: Vulkan Wayland WSI broken after system upgrade

As a temporary fix I ended up rewinding my system's packages back to the latest archive snapshot that was using 510.68.02 drivers.
Obviously that isn't a acceptable long term fix, and I eventually had to upgrade again.
I hoped in that time that another update was pushed that fixed the issue but as of today with version 515.43.04-6 the issue persists. (segfault in libnvidia-glcore.515.43.04)

I've absolutely no idea how to solve this.
Do I just have to wait for nvidia to fix this, or is there some configuration I can change?

Lone_Wolf wrote:

I'm not familiar with wayland WSI , could you explain what that is ?

As progandy said it's the Wayland windowing integration for Vulkan, which allows you to create Vulkan surfaces on Wayland using VK_KHR_wayland_surface.
That gitlab link is mesa's implementation of that extension, but since I'm on nvidia I'm using their proprietary implementation instead.

Lone_Wolf wrote:

Please post the output of

$ lspci -k
$ vulkaninfo --summary
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: pcieport
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (2) I218-V
        DeviceName:  Onboard LAN
        Subsystem: ASUSTeK Computer Inc. Device 85c4
        Kernel driver in use: e1000e
        Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
        Subsystem: ASUSTeK Computer Inc. Device 8608
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 (rev d0)
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation Z97 Chipset LPC Controller
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: lpc_ich
        Kernel modules: lpc_ich
00:1f.2 RAID bus controller: Intel Corporation SATA Controller [RAID mode]
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
        Subsystem: ASUSTeK Computer Inc. Device 8534
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device 367a
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device 367a
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
02:00.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
        Subsystem: ASMedia Technology Inc. Device 118f
        Kernel driver in use: pcieport
03:01.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
        Subsystem: ASMedia Technology Inc. Device 118f
        Kernel driver in use: pcieport
03:03.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
        Subsystem: ASMedia Technology Inc. Device 118f
        Kernel driver in use: pcieport
03:05.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
        Subsystem: ASMedia Technology Inc. Device 118f
        Kernel driver in use: pcieport
03:07.0 PCI bridge: ASMedia Technology Inc. ASM1184e 4-Port PCIe x1 Gen2 Packet Switch
        Subsystem: ASMedia Technology Inc. Device 118f
        Kernel driver in use: pcieport
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 11)
        Subsystem: ASUSTeK Computer Inc. AM1I-A Motherboard
        Kernel driver in use: r8169
        Kernel modules: r8169
07:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device 858d
        Kernel driver in use: ahci
08:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
        Subsystem: ASUSTeK Computer Inc. Device 85fd
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
==========
VULKANINFO
==========

Vulkan Instance Version: 1.3.213


Instance Extensions: count = 19
-------------------------------
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_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

Instance Layers: count = 16
---------------------------
VK_LAYER_INTEL_nullhw             INTEL NULL HW                         1.1.73   version 1
VK_LAYER_KHRONOS_validation       Khronos Validation Layer              1.3.211  version 1
VK_LAYER_LUNARG_api_dump          LunarG API dump layer                 1.3.204  version 2
VK_LAYER_LUNARG_device_simulation LunarG device simulation layer        1.3.204  version 1
VK_LAYER_LUNARG_monitor           Execution Monitoring Layer            1.3.204  version 1
VK_LAYER_LUNARG_screenshot        LunarG image capture layer            1.3.204  version 1
VK_LAYER_MANGOAPP_overlay         Mangoapp Layer                        1.2.135  version 1
VK_LAYER_MANGOHUD_overlay         Vulkan Hud Overlay                    1.2.135  version 1
VK_LAYER_MESA_device_select       Linux device selection layer          1.3.211  version 1
VK_LAYER_MESA_overlay             Mesa Overlay layer                    1.3.211  version 1
VK_LAYER_NV_optimus               NVIDIA Optimus layer                  1.3.205  version 1
VK_LAYER_RENDERDOC_Capture        Debugging capture layer for RenderDoc 1.3.131  version 19
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer          1.2.136  version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer          1.2.136  version 1
VK_LAYER_VALVE_steam_overlay_32   Steam Overlay Layer                   1.2.136  version 1
VK_LAYER_VALVE_steam_overlay_64   Steam Overlay Layer                   1.2.136  version 1

Devices:
========
GPU0:
        apiVersion         = 4206797 (1.3.205)
        driverVersion      = 2160771328 (0x80cac100)
        vendorID           = 0x10de
        deviceID           = 0x13c2
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = NVIDIA GeForce GTX 970
        driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
        driverName         = NVIDIA
        driverInfo         = 515.43.04
        conformanceVersion = 1.3.1.0
        deviceUUID         = 12cccd08-233d-765a-a8a7-c0c01e459d95
        driverUUID         = c50a21fe-1add-508b-b23c-d7b64c4bda7e

Last edited by nullelement (2022-05-29 17:07:26)

Offline

#5 2022-05-31 09:47:05

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,142

Re: Vulkan Wayland WSI broken after system upgrade

Thanks for the explanations, progandy & nullelement.

You can try posting on nvidia forums and try to get the attention of their devs on this issue.

Assuming you can't do without this functionality and you need to stay on 5.10 for the foreseeable future , you should switch to https://aur.archlinux.org/pkgbase/nvidia-510xx-utils .

It's maintainer/creator has kept older nvidia drivers working and updated for archlinux for quite some time already.

Last edited by Lone_Wolf (2022-05-31 09:48:40)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#6 2022-05-31 16:10:23

nullelement
Member
Registered: 2022-05-18
Posts: 3

Re: Vulkan Wayland WSI broken after system upgrade

Thanks Lone_Wolf for the suggestion. I installed the 510xx packages and it solved the issue.
vkcube-wayland and my own programs now work as expected.

Offline

Board footer

Powered by FluxBB