I’m seeing the exact same issue of displays freezing with explicit synchronization in hyprland 0.42. Hopefully it’s better for testing and reproducibility since it’s a hyprland full release rather than a git version of sway.
I don’t have The Finals so I can’t test it, maybe it’s the same issue as with Control?
Same but I can’t think of any other reason why it would be happening.
Disabling 4G also helps in Alan Wake 2, though not in the same way. With GSP off it would go to 99% utilization, the difference is actually that it stops plummets to 21% utilization… and instead those plummets are closer to 60% or so. This reduces frame time spikes, and their frequency is also reduced.
1 Like
DX12 performance is still bad compared to dx11 on a rtx 4090 mobile.
Thank you for the tip! I disabled 4G Decoding and Resize Bar, but unfortunately, I didn’t notice any improvements in The Finals. The game starts at 1845MHz core clock when I log in, but after about a minute, it drops to around 1200MHz. Additionally, I’m unable to set a frame limit cap in the video settings, almost as if the game isn’t recognizing the NVIDIA parameters properly.
1 Like
Have there been any developments on flickering with Electron apps?
VSCode is a flickery nightmare, and both Discord and Obsidian have really stuttery text input. All three are running native Wayland, with ELECTRON_OZONE_PLATFORM_HINT set
1 Like
It’s not fixed… it decided to start crashing again. Seems like it always works after a fresh driver install, if you then reboot your computer or even just sometimes relaunching the game … it stops working again.
@amrits
Did some more testing and I noticed if I I delete ~\.cache\nvidia it seems to work again. until I relaunch the game. Driver cache issue?
We filed bugs for 2 more issues today and were able to reproduce issue locally.
Issue 1 - Overriding EDID makes VRR stop working under WAYLAND - 4797139
Issue 2 - Xwayland VRAM usage is still excessive when resizing X11 apps under wayland. - 4806756
We will be monitoring other issues as well and will keep updated.
11 Likes
560-nvidia-bug-report.log.gz (1.5 MB)
555-nvidia-bug-report.log.gz (1.6 MB)
560 vs 555 in Cyberpunk, GSP OFF
modinfo nvidia | grep license
license: NVIDIAnvidia-smi -q | grep GSP
GSP Firmware Version : N/A
Operating System: Arch Linux
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.10.4-zen2-1.1-zen (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: ASUS
Windws 11 native for compare
1 Like
really nice to see fps increases especially in dx12 games like these, This isn’t a small amount either :)
edit: guess my hopes were too high lol
The order of the screenshots seems wrong, the first is 560.31.xx while the second is 555.58.xx.
This actually shows a regression in overall performance.
Can you attach a bug report log? You can generate one by running sudo nvidia-bug-report.sh.
Also, are they both the proprietary kernel modules? You can send the output of modinfo nvidia | grep license with both drivers.
DE might also be useful to know, and also whether you’re running it on Wayland or X11.
I think this is not the first instance of a regression between the 555 and 560 branches, I’ll see if I can find other reports and perhaps potential correlations between them as I think I’ve seen some already over on the CachyOS discord server.
Another useful detail is whether there is a meaningful reported difference in GPU/CPU usage (and GPU/VRAM Clocks) between both drivers.
Sorry for the noise but I just wanted to say I appreciate the Nvidia staffs activity in this thread. Having even a vague understanding of what issues are known about and being looked into/fixed is pretty neat.
6 Likes
Fixed original post. Thanks.
1 Like
Log after the system wakes from sleep mode in a wild session.
The system needs to be rebooted to get rid of artifacts on the screen.
emphasized textnvidia-bug-report.log.gz (975.9 KB)
Set PreserveVideoMemoryAllocations to 1. It will fix artifacts on resume.
the EA app issue is NOT from NVIDIA driver, after digging found out it come from by ( Adding ipv6.disable=1 to the kernel line)
don’t know why but it causing launchers via wine to not opening like ea app and battlenet ,
I’m so sorry NVIDIA staff for the mistake, very weird ngl .
1 Like
Set options nvidia NVreg_PreserveVideoMemoryAllocations=1
This works on X11.
And on Wayland the output is with artifacts.
Will we have another beta release?
btw I recommend NVreg_EnableS0ixPowerManagement instead of NVreg_PreserveVideoMemoryAllocations
Check S0ix-based power management part
https://download.nvidia.com/XFree86/Linux-x86_64/560.31.02/README/powermanagement.html
What about the kernel panic on suspend/resume regression introduced in 555? Is that still being worked on?
1 Like