You are not logged in.
After installing the latest NVIDIA drivers, it seems that anything running at 1920x1080 runs at around 20 FPS. Also some Vulkan stuff crashes.
I have a GTX 1660 (GV-N1660OC-6GD) and a 1920x1080 144hz monitor (XG2402). Kernel is 6.13.5-arch1-1, KDE Plasma 6.3.2-1. Right now, I'm using the proprietary drivers from the repo (570.124.04).
Performance is generally bad but seems to be closely tied to resolution which seems odd to me.
This runs at about 50 FPS...
mangohud vkcube --width 1280 --height 720While this runs at about 20 FPS.
mangohud vkcube --width 1920 --height 1080VKCube also segfaults on exit.
Vulkaninfo produces this error:
ERROR at /usr/src/debug/vulkan-tools/Vulkan-Tools/vulkaninfo/./vulkaninfo.h:901:vkCreateWaylandSurfaceKHR failed with ERROR_OUT_OF_HOST_MEMORYRunning glxgears with mangohud causes it to segfault immediately after showing a black window.
I believe there were two new versions of the NVIDIA drivers on the repo in quick succession both of which seemed to show the same behavior for me, but the version before that worked fine. If anyone could help me investigate and / or workaround, it would be much appreciated.
extra/egl-wayland 4:1.1.17-1 [installed]
extra/egl-x11 1.0.0-1 [installed]
extra/libvdpau 1.5-3 [installed]
extra/libxnvctrl 570.124.04-1 [installed]
extra/nvidia-dkms 570.124.04-1 [installed]
extra/nvidia-settings 570.124.04-1 [installed]
extra/nvidia-utils 570.124.04-1 [installed]
extra/opencl-nvidia 570.124.04-1 [installed]
multilib/lib32-libvdpau 1.5-3 [installed]
multilib/lib32-nvidia-utils 570.124.04-1 [installed]
multilib/lib32-opencl-nvidia 570.124.04-1 [installed]
extra/mangohud 0.8.0-3 [installed]
extra/nvidia-utils 570.124.04-1 [installed]
extra/qt6-shadertools 6.8.2-1 (qt6) [installed]
extra/renderdoc 1.36-2 [installed]
extra/spirv-tools 1:1.4.304.1-2 (vulkan-devel) [installed]
extra/vulkan-headers 1:1.4.304.1-2 (vulkan-devel) [installed]
extra/vulkan-tools 1.4.304.1-1 (vulkan-devel) [installed]
extra/vulkan-validation-layers 1.4.304.1-1 (vulkan-devel) [installed]
multilib/lib32-nvidia-utils 570.124.04-1 [installed]
extra/ocl-icd 2.3.2-2 [installed]
extra/vulkan-icd-loader 1.4.304.1-1 (vulkan-devel) [installed]
multilib/lib32-ocl-icd 2.3.2-2 [installed]
multilib/lib32-vulkan-icd-loader 1.4.304.1-1 [installed]Last edited by rbrauer (2025-03-01 19:36:48)
Offline
Cannot reproduce here on Wayland (no Xwayland) with a GTX 1050 Ti.
Does this occur if you take mangohud out of the equation?
Are there multiple GPUs?
What happens if you force Wayland?
vkcube --wsi wayland --c 600 --width 1920 --height 1080I only have a 60hz monitor, and get 60fps at any resolution for vkcube via stopwatch method.
Offline
The performance on vkcube seems the same with or without mangohud. Without mangohud it does not segfault on exit.
What happens if you force Wayland?
vkcube --wsi wayland --c 600 --width 1920 --height 1080
This segfaults immediately.
Investigating further, I noticed this as well:
Mar 01 10:47:29 computer kwin_wayland[865]: kwin_scene_opengl: eglInitialize failed
Mar 01 10:47:29 computer kwin_wayland[865]: kwin_scene_opengl: Error during eglInitialize 12289Offline
This segfaults immediately.
Investigating further, I noticed this as well:
Mar 01 10:47:29 computer kwin_wayland[865]: kwin_scene_opengl: eglInitialize failed Mar 01 10:47:29 computer kwin_wayland[865]: kwin_scene_opengl: Error during eglInitialize 12289
Hmm. I know nothing about kwin, nor its Wayland implementation.
Does:
eglinfo -BAlso segfault?
If so, does specifying:
__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json eglinfo -BHelp?
Offline
It looks like its only working partially with or without the variable.
With: https://hastebin.com/share/eyulobetaf.yaml
Wihtout: https://hastebin.com/share/uzomezozop.yaml
Offline
So it seems to be back to normal now. I think the only thing I did was reinstall egl-gbm.
Offline