Non-gamer here simply looking to achieve a viable workstation setup.
With each successive driver release since the 550 series there’s a growing number of problems.
Currently tracking 4 known issues. To summarize, ordered by subjective severity, from lowest to highest:
Use-after free error in 570 driver. Needs to be addressed, but low impact with no crash.
This is a new bug first seen with the 570.124.04 Production Branch driver release.
I’ve about 30 instances over the past few days,.
Mar 02 16:47:17 kernel: ==================================================================
Mar 02 16:47:17 kernel: BUG: KFENCE: use-after-free read in _nv000177kms+0x439/0x2a10 [nvidia_modeset]
Mar 02 16:47:17 kernel: Use-after-free read at 0x00000000e7c09e3f (in kfence-#113):
Mar 02 16:47:17 kernel: _nv000177kms+0x439/0x2a10 [nvidia_modeset]
Mar 02 16:47:17 kern…
Chrome/Electron VK_ERROR_INCOMPATIBLE_DRIVER errors at launch. I don’t care about this one as I use neither software/platform.
Greetings.
Using 550-beta driver. Arch Linux. Using aur package for 550-beta-dkms.
Running electron app with --ozone-platform-hint=auto flag ( vesktop for example ), I got this error in my terminal:
▶
Summary
find / -type f -name “libnvidia-glvkspirv*” shows that libnvidia-glvkspirv exist in /usr/lib/libnvidia-glvkspirv.so.550.40.07
GTK4 application tooltips and popover dialogs are stretched/distorted/frozen. This affects the GL and NGL renderers for GTK4 apps and is wildly annoying.
Original thread - (GeForce RTX 4070) GTK application issue with NVIDIA GPU .
GNOME Bug report - Tooltips are stretched (#5832)
Reposting the thread with a more descriptive title for additional clarity/discoverability. In GTK applications, some menus and tooltips become stretched/improperly sized.
Have personally seen this issue crop up in GNOME Software dropdown menus and hover tooltips in any GTK applications. It’s especially apparent in GNOME Builder (IDE) with auto-completion.
A couple exa…
GTK4 apps background CPU usage and application crash-on-exit with Vulkan renderer. This is a showstopper for using the default Vulkan GTK4 renderer.
Originally filed against the GTK project:
GTK4 apps background CPU usage high with Vulkan renderer (#7117) · Issues · GNOME / gtk · GitLab
This was quickly identified as an nVidia driver issue.
As of gtk 4.16 the Vulkan rendering backend is used by default.
GTK4 apps are consuming unexpected CPU cycles while idle in the background when using the Vulkan backend.
This does not occur with the NGL renderer.
Using this roundup topic for myself to organize, track, and update the overall status of issues I’m facing for each successive driver release.
I’ve provided numerous nVidia bug reports, GDB backtraces, etc. where applicable, and will also continue providing feedback on the individual issue threads as well as driver-release-specific feedback topic threads.
Current stack:
Arch Linux | Kernel 6.13.5
Gnome-shell | Mutter 47.5
Wayland (meson_options: xwayland=false, x11=false )
Gtk4 4.16.12
Mesa 24.3.4
vulkan-icd-loader 1.4.304
nVidia 570.124.04
1 Like
Forgot one…
Nvidia driver isn’t compatible with simpledrm so boot output and TTYs are blank
Hi,
I run Fedora 37 and using nvidia proprietary drivers I cannot access any of my TTYs, and the kernel out during boot (disabling rghb quiet in grub) is blank once the driver gets loaded. As far as I can tell, this was caused by a change in Fedora 36 where fbdev (drivers?) were replaced with CONFIG_DRM and CONFIG_SYSFB_SIMPLEFB. On my gentoo install running the latest nvidia drivers, I can run CONFIG_FB_SIMPLE on my kernel (which I can’t on Fedora because it’s prebuilt) without an issue and I …
For older generation GPUs (<= Pascal), nvidia_drm.fbdev=0 kernel parameter is still required to have a functional TTY, display the full boot text, and avoid the “freezing” / black screen.
Also, nvidia_drm.modeset=1, used in combination with the patched Arch kernel , is still required as a kernel parameter to avoid the simpledrm device creation.
See Also:
Updating this tracking thread for the nVidia 570.133.07 Production Branch driver release.
Currently afftected by 5 issues with nVidia Linux drivers.
New bug reports attached and further details have been submitted for each individual issue.
Use-after free error
This is a new bug first seen with the 570.124.04 Production Branch driver release.
I’ve about 30 instances over the past few days,.
Mar 02 16:47:17 kernel: ==================================================================
Mar 02 16:47:17 kernel: BUG: KFENCE: use-after-free read in _nv000177kms+0x439/0x2a10 [nvidia_modeset]
Mar 02 16:47:17 kernel: Use-after-free read at 0x00000000e7c09e3f (in kfence-#113):
Mar 02 16:47:17 kernel: _nv000177kms+0x439/0x2a10 [nvidia_modeset]
Mar 02 16:47:17 kern…
Chrome/Electron VK_ERROR_INCOMPATIBLE_DRIVER errors at launch.
Greetings.
Using 550-beta driver. Arch Linux. Using aur package for 550-beta-dkms.
Running electron app with --ozone-platform-hint=auto flag ( vesktop for example ), I got this error in my terminal:
▶
Summary
find / -type f -name “libnvidia-glvkspirv*” shows that libnvidia-glvkspirv exist in /usr/lib/libnvidia-glvkspirv.so.550.40.07
GTK4 application tooltips and popover dialogs are stretched/distorted/frozen. This affects the GL and NGL renderers
Original thread - (GeForce RTX 4070) GTK application issue with NVIDIA GPU .
GNOME Bug report - Tooltips are stretched (#5832)
Reposting the thread with a more descriptive title for additional clarity/discoverability. In GTK applications, some menus and tooltips become stretched/improperly sized.
Have personally seen this issue crop up in GNOME Software dropdown menus and hover tooltips in any GTK applications. It’s especially apparent in GNOME Builder (IDE) with auto-completion.
A couple exa…
GTK4 apps background CPU usage and application crash-on-exit with Vulkan renderer. This is a showstopper for using the default Vulkan GTK4 renderer.
Originally filed against the GTK project:
GTK4 apps background CPU usage high with Vulkan renderer (#7117) · Issues · GNOME / gtk · GitLab
This was quickly identified as an nVidia driver issue.
As of gtk 4.16 the Vulkan rendering backend is used by default.
GTK4 apps are consuming unexpected CPU cycles while idle in the background when using the Vulkan backend.
This does not occur with the NGL renderer.
Nvidia driver isn’t compatible with simpledrm so boot output and TTYs are blank
Hi,
I run Fedora 37 and using nvidia proprietary drivers I cannot access any of my TTYs, and the kernel out during boot (disabling rghb quiet in grub) is blank once the driver gets loaded. As far as I can tell, this was caused by a change in Fedora 36 where fbdev (drivers?) were replaced with CONFIG_DRM and CONFIG_SYSFB_SIMPLEFB. On my gentoo install running the latest nvidia drivers, I can run CONFIG_FB_SIMPLE on my kernel (which I can’t on Fedora because it’s prebuilt) without an issue and I …
Latest stack:
Arch Linux | Kernel 6.13.7
Gnome-shell | Mutter 48.0
Wayland (meson_options: xwayland=false, x11=false )
Gtk4 4.18.2
Mesa 25.0.2
vulkan-icd-loader 1.4.304
nVidia 570.133.07
I will continue to update this tracking thread for each successive driver release.
2 Likes