560 release feedback & discussion

[JKrych]

Another issue is games are running with llvmpipe on my F40 Silverblue system. @leigh123linux not sure if this is a rpm-fusion or Nvidia issue here.

[abchauhan]

Hi @JKrych , Sorry, that issue remains under investigation and has not been fixed yet.

1. Are you building Unreal Engine 5.4.3 from source?
2. Can you confirm the stack trace matches the one posted in

560 release feedback & discussion

Hi all, listing bugs from this feedback & discussion :- 4764568 - Minecraft crashes when entering full screen → Under investigation 4767941 - 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:…

under 7. 4717891 - On 555, Unreal engine crashes after running for some time. Thanks!

[abchauhan]

Hi @edgarscirulis , 4764568 - Minecraft crashes when entering full screen remains under active investigation. We do not have a fix yet. Thank you

[abchauhan]

Thank you @mirao, I have filed NVBug #4821165 - ‘Screen freeze observed when Night Mode is toggled on Ubuntu 24.04 PRIME notebooks with an external monitor’ for tracking. This is under investigation.

I can reproduce this only on Wayland sessions. Are you able to reproduce this on both X and Wayland?

[gplourde]

Same here, but only flatpak applications. Please confirm it’s any applications for you in or out of flatpak.

[abchauhan]

Hi @lord , @andre_trekx , @jeisom , @asubstanced,

Sorry for the delay on this issue.

I have filed NVBug #4821290 - Colours appear washed out on multiple displays - Deco Gear 40, LG OLED C1, Alienware AW2725DF, Alienware AW3423DWF and Samsung Odyssey G8 OLED, when HDR is enabled

Can you please capture a NVIDIA bug report from your systems for an initial Engineering review.
We are waiting for suitable hardware to free up for testing this issue.

Thank you

[lord]

Here is mine. I took it with 555 driver, but both 555 and 560 share exactly the same problem. I will wait for 560 release (in Arch repos) and could take it again if that’s necessary.
nvidia-bug-report.log.gz (428.7 KB)

[asubstanced]

This is for a Samsung QN90B on 560 where colour space Gamut is stuck at BT.709 on HDMI 2.1.

nvidia-bug-report.log.gz (767.6 KB)

[shishimaru]

It’s funny, the Beta driver was working great, the stable version of 560 instead breaks my external monitor (is not detected).

[mirao]

@asubstanced
100% reproducible with Wayland and never was able to reproduce with X.Org.
It’s on a PC with Ubuntu 24.04, GPU RTX 4060 (MSI GeForce RTX 4060 VENTUS 2X BLACK 8G OC) and a connection to one external monitor (Dell).

I did some more testing on the same PC with a GPU integrated in CPU Ryzen 9700X. In Wayland, Night Light switched on/off many times is stable there.

So in my environment only the configuration nVidia + Wayland is affected.

[birdie]

Still not fixed: Multiple kernel oopses before suspending caused by nvidia-sleep.sh, Linux 6.10 regression? WARNING: CPU: PID: at include/linux/rwsem.h:80 follow_pte

[jeisom]

I have NO IDEA what has changed. I would have tested right before I commented, so proton(9.0-2), kwin and gamescope should be the same and I just checked with downgraded drivers as well and can no longer reproduce. I tried Ghost of Tsushima, Ghostwire Tokyo, Horizon forbidden west and CP2077. I hate when this happens because at that point I just want to know then is what has changed.

[asubstanced]

DP->HDM2.1 same QN90B. Here all colours are washed out.

nvidia-bug-report.log.gz (765.8 KB)

[andre_trekx]

Here’s my report. I did a quick test with Elden Ring on the AW2725DF before generating it.
nvidia-bug-report.log.gz (762.0 KB)

[JKrych]

Thank you for the response!

1. No, I’m using the precompiled binaries provided by Epic.
2. Yes, it’s very similar. One notable thing would be the one known function here:
   libUnrealEditor-RHI.so!_ZN19FRHICommandListBase7ExecuteER17TRHIPipelineArrayIP18IRHIComputeContextEPNS_16FPersistentState9FGPUStatsE(+0x4dc)

[JKrych]

System apps run and store shader binaries in GLCache dir correctly (eg. UE5), but Flatpaks seem to be running llvmpipe. Some Flatpak apps store mesa_shader_cache like Blender, Bitwig Studio or games running through Flatpak Steam. Blender is very choppy, unusable and games crash during launch. Some apps don’t seem to cache any shaders like Discord or Spotify.

[abchauhan]

@abchauhan

4. 4769163 - Screen freeze observed with directly scanned out windows on a multi-monitor configuration

Jul 26 15:52:35 beefiercake kernel: [drm:nv_drm_atomic_apply_modeset_config.isra.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to initialize semaphore for plane fence
Jul 26 15:52:35 beefiercake kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to apply atomic modeset.  Error code: -11
Jul 26 15:53:00 beefiercake kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 2
Jul 26 15:53:03 beefiercake kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 2

Hi all, Can you please confirm the above issue is resolved on your systems with 560.35.03?

I have filed a new bug for the screen freeze with night mode - NVBug #4821165 - ‘Screen freeze observed when Night Mode is toggled on Ubuntu 24.04 PRIME notebooks with an external monitor’ for tracking.

2024-08-20T19:35:18.662981+02:00 rog kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0
2024-08-20T19:35:21.798987+02:00 rog kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Flip event timeout on head 0

We can reproduce the issue and this is under investigation. Thank you

[faz]

#4769163 seems solved for me since updating.

[Sanx1]

#4769163 seems solved here as well with 560.35.03. Great work.

[bryandelrichard01]

Hi there, I am still experiencing this in the most recent driver, same Operating System and a fresh install.