Please provide feedback specific to the 560 release series here.
still issue on:
I can’t reproduce a crash when the game goes fullscreen, but I do see a similar-looking crash when exiting the game. I’ll investigate.
The crash on full-screen happens on 1.12.2 version.
No rtd3 power management for Turing gpus on open-source drivers, yet?
All Games run using Wine or proton seems to be crashing
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 146 ()
Minor opcode of failed request: 5
Value in failed request: 0x1c003ba
Serial number of failed request: 3986
Current serial number in output stream: 4003
0210:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 000000000011FE80
nvidia-bug-report.log.gz (647.1 KB)
This issue happens on Plasma and Gnome and even Cosmic DE
There are multiple issues going on with this release:
- Im getting massive segfaults from the driver, this happened after adjusting the packaging with the new libaries, see: nvidia: 560: Fix packaging · CachyOS/CachyOS-PKGBUILDS@d24099a · GitHub In the screenshot you can find the segfauts
- Any Pipewire based sharing (OBS, spectacle, Discord) only shows a blackscreen. Maybe due the new CaptureSDK missing?
- Games do not launch with Proton, tested: Rocket League, Palworld. CS2 is working fine
4070 S. I will upload after some debugging a nvidia-bugreport.sh
5 Likes
560 proprietary driver.
Baldur’s gate 3 ( DXVK and VK) , Dead By daylight ( DXVK ) not working at all. Just black screen on launch.
1 Like
I understand it’s beta and I’m not playing blame game here, but come on Nvidia, you need to test your drivers before releasing them.
10 Likes
With 560, the KDE Plasma 6.1.3 screen is corrupted and mouse pointer leaves trail.
Potential relevant log entries:
kwin_wayland_wrapper[nnnn]: I2024-07-23 18:57:30.450858 addonmanager.cpp:205] Loaded addon wayland
kwin_wayland_wrapper[nnnn]: Xwayland glamor: GBM Wayland interfaces not available
kwin_wayland_wrapper[nnnn]: Failed to initialize glamor, falling back to sw
Hardware:
1x NVIDIA Corporation TU104 [GeForce RTX 2080 Rev. A] (rev a1)
Alright, the segfaults go away, when packaging the new vksc differently.
Even tough, games do not launch yet.
1 Like
I am also unable to launch any Proton games on my Arch system after upgrading to the 560 drivers.
Also the GSP slowdown bug seems only partially addressed. KDE performance seems better than the 555 drivers when GSP is enabled, but moving windows around still starts to stutter after a while. You can test this by continuously dragging a window around for several seconds. It will initially be smooth and then start to judder. This seems to be much more apparent on 120Hz and faster refresh displays.
1 Like
The buggy egl-wayland 1.1.14 (OBS Studio began to crash after egl-wayland 1.1.14 was released · Issue #118 · NVIDIA/egl-wayland · GitHub) is required on Wayland, otherwise it will fallback to Zink or llvmpipe in EGL Wayland platform.
X11 EGL platform is still not working on Wayland despite the line Added support for EGL_KHR_platform_x11 and EGL_EXT_platform_xcb on Xwayland. in release highlights.
3 Likes
On Arch, GarudaOS. Installed with frogging family which went fine.
Wayland still has the KDE freezing bug and X11 crashed after a short while into a black screen, freezing whole PC, not even switching to TTY helped.
So, had to downgrade to 555 so at least X11 works. Sorry for the minimal feedback, maybe I’ll post more or try again later.
you ARE the tester ;)
3 Likes
Did anyone at NVIDIA even try the 560 driver?
1 Like
:) I’m fine with that, but some sort of basic QA functional tests would be nice.
Off the top of my head, run some games, try KDE/Gnome (wayland/X11), maybe some capture software… etc.
2 Likes
Too expensive friend, at least it didn’t break your system.
If you aren’t going to fix bugs or even respond, stop doing these posts.
Edit: lmao. go away troll.