560 release feedback & discussion

Latest driver release (560.35.03) was not uploaded here Index of /XFree86

2 Likes

Vram issue fixed?

No, not yet

is there now.

@photmailw I’m trying the today’s build 560.35.03, we’ll see.
I was surprised that the issue ā€œFlip event timeoutā€ was on multi monitor configuration whereas I’m having only one display. But actually I have one unknown display because of the bug Bug #2060268 ā€œPhantom ā€œUnknown Displayā€ shown in Settings after ...ā€ : Bugs : linux package : Ubuntu

BTW just got the issue with freezing screen again.
nvidia-bug-report.log.gz (739.7 KB)

1 Like

Frametimes look improved on last release, I’m dropping significantly less frames on desktop at 180hz. Also with maxed clocks, issue is 99,9% gone (can keep multiple 3d apps on screen at 180fps).

@mirao - Hi, I found this thread (which perfectly described my issue), after first experiencing this bug in Ubuntu 24.04 (it wasn’t a problem in 22.04): Screen freezes at random intervals with RTX 4060 Max-Q / Mobile, multiple driver versions tested

They report exactly the same ā€œFlip event timeout on head 0ā€ error, along with the workaround of switching to a virtual console and back again to desktop. I’m hopeful of this being fixed in a future Nvidia driver, now it’s made their bug list (provided it is the same problem).

Just tested with onboard amd gpu, and full 6016x3384 resolution shows/works fine. So definitely an issue with the nvidia driver as far as I can tell.

I’m sure I’m in a minority here with my monitor, but maybe this issue is tied to other monitor /resolution / refresh detection issues with the drivers. Worth looking into, I hope :) Ty

Hi @mirao,

Can you confirm the steps to reproduce this issue :-
Toggle Night light settings for 30s on a PRIME setup with an external monitor?

The multi-monitor 4769163 screen freeze should be fixed on 560.35.03. This reported issue might have a different root cause. I will check this and file a bug. Thanks

1 Like

Hmm… any changelog available for this version?

Thanks! Just tested, so far awesome, many noticeable improvements.

The previous beta fixed all of my issues in XWayland on Gnome, haven’t had a chance to try the stable ones yet but I won’t be going back to 555.

NVidia stuff, I have one question. On process monitoring app it sometimes shows that game uses something like 7.8 GB of video ram, while GPU only has 6 GB. Running standalone configuration (mean only nvidia gpu, intel is BIOS level disabled). Does GPU somehow use ordinary RAM/drive swaps if running out of VRAM?

@photmailw @abchauhan
Confirmed. Now when I’m switching Night Light between on/off repeatedly, screen will freeze in a moment.
Interestingly when I did it in ā€œSetting => Displays => Night Lightā€, I wasn’t able to reproduce it. And later when I tried it over settings in the top right corner of my screen => Night Light, then it froze immediately. But I think it’s rather because a night time started. So now I’m able to reproduce both ways.

1 Like

Adding here that I’m also having this same problem with washed out colors when using HDR on games.
I’m using CachyOS on kernel 6.10.6 with KDE Plasma 6.1.4 and I’ve tried using HDR on two different displays, an Alienware AW2725DF (using DisplayPort) and an LG OLED C1 (using HDMI 2.1). My GPU is an RTX 4080, and I’m using driver version 560.35.03.

I enabled HDR in KDE’s Display Settings and launched my games through Steam with gamescope with the ā€œā€“hdr-enableā€ option, as described in the Arch Linux wiki’s KDE page:
https://wiki.archlinux.org/title/KDE#HDR

The GPUs have been able to use onboard memory and system memory for most things interchangeably since roughly when we started shipping PCIe GPUs (GeForce 8600 was the first to have what I consider a fully unified memory subsystem, but some cards before that came pretty close as well). I’m not sure how your tool is calculating vidmem usage, but it’s possible it’s including some system memory used by the GPU as well.

1 Like

I’ve hit this issue in the past, I’m not sure it’s related to the NVIDIA Driver.
I could only reproduce this with older versions of the !1441 MR for GNOME Shell which is included by default in Ubuntu.

Perhaps this is an issue with the older versions of the MR and the Ubuntu GNOME Shell build doesn’t yet have the subsequent improvements that fixed it on my system.
For me it was a general multi-monitor issue as I’m not on a PRIME system.

You can find my original thread on Gitlab.
I can no longer reproduce this on the latest iteration of the MR.

Anything new about Minecraft 1.12.2 crash on full-screen using lwjgl2 and Minecraft crash on exit that uses lwjgl3? Thanks for answering.

Unreal Engine 5.4.3 segfaults when running on the Wayland session on both R555 and R560 drivers. Not fixed with latest stable 560.35.03. Running the editor in X11 session works fine.
UE 5 R560 Wayland Segfault.txt (1.1 KB)