565 release feedback & discussion

NVIDIA developers, I would like to ask questions regarding bit color and whether or not this driver release will resolve it in Linux ? My questions are : "

  1. Is my monitor(AW3423DW) outputting 8 bit or 10 bit color in Plasma Wayland 6.2.2 ?
  2. If the bit color output is wrong, will this driver(565.57.01) fix the bit color in my monitor when I enable the HDR option in Plasma ?"

I was checking my system information on Steam and in Desktop Color Depth, it said 24 bit color.

I was curious whether or not that was true or not so I scrolled around the internet for more information about bit color and I have learned two commands that query the bit color that is showing and I am conflicted on whether or not my monitor is displaying 8 or 10 bit color ( on Plasma Wayland).

One command I have used first to query the bit color is xdpyinfo , under ā€œsignificant bits in color specificationā€ it says 8 bit . But when I use drm_info , under ā€œFormatā€ it says ABGR2101010(which from a Reddit comment confirms that this is 10 bit color). Could you confirm to me whether Plasma( or specifically Kwin, correct me if Iā€™m wrong) is outputting the correct bit color( with hdr disabled ) . And if you confirm that the output of the Kwin compositor outputs the wrong bit color, will this driver release fix that or on a future release ?

Thank you for reading

Here are the sources that help me learned about this topic:

https://www.reddit.com/r/kde/comments/syf2gq/kde_on_wayland_how_to_set_30bit_color_ie_10bit/

https://github.com/ValveSoftware/steam-for-linux/issues/4399

Here are the snippets of the output of the two commands

  1. xdpyinfo
  visual:
    visual id:    0x24c
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x255
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x256
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x257
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x258
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  1. drm_info
    ā”‚   ā”‚   ā”‚   ā”œā”€ā”€ā”€Format: ABGR2101010 (0x30334241)
    ā”‚   ā”‚   ā””ā”€ā”€ā”€Formats:
    ā”‚       ā”‚   ā”œā”€ā”€ā”€Format: ABGR2101010 (0x30334241)

Suspend is still broken on kernels 6.10 and newer.

Oct 30 15:05:11 archlinux kernel: ------------[ cut here ]------------
Oct 30 15:05:11 archlinux kernel: WARNING: CPU: 10 PID: 8555 at include/linux/rwsem.h:80 follow_pte+0x1de/0x200
Oct 30 15:05:11 archlinux kernel: Modules linked in: uhid rfcomm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_seq mt7921e mt7921_common mt792x_lib mt76_connac_lib mt76 bnep mac80211 btusb btrtl snd_usb_audio btintel libarc4 b>
Oct 30 15:05:11 archlinux kernel:  nvidia_uvm(OE) snd cryptd sp5100_tco usbhid soundcore rapl i2c_piix4 ccp video k10temp i2c_smbus pcspkr wmi mac_hid gpio_amdpt gpio_generic nvidia(OE) crypto_user dm_mod loop nfnetlink zram ip_tables x_tables ext4>
Oct 30 15:05:11 archlinux kernel: CPU: 10 UID: 0 PID: 8555 Comm: nvidia-sleep.sh Tainted: G           OE      6.11.5-arch1-1 #1 1400000003000000474e55005271cfbcddaab6f6
Oct 30 15:05:11 archlinux kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Oct 30 15:05:11 archlinux kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D75/MAG B650 TOMAHAWK WIFI (MS-7D75), BIOS 1.J0 07/24/2024
Oct 30 15:05:11 archlinux kernel: RIP: 0010:follow_pte+0x1de/0x200
Oct 30 15:05:11 archlinux kernel: Code: 52 d9 00 48 81 e2 00 00 00 c0 48 09 c2 48 f7 d2 48 85 fa 75 20 e8 42 f1 ff ff 48 8b 35 7b b5 5c 01 48 81 e6 00 00 00 c0 eb 8d <0f> 0b 48 3b 1f 0f 83 50 fe ff ff bd ea ff ff ff eb b6 49 8b 3c 24
Oct 30 15:05:11 archlinux kernel: RSP: 0018:ffffbb3f0549f850 EFLAGS: 00010246
Oct 30 15:05:11 archlinux kernel: RAX: 0000000000000000 RBX: 0000769ca002f000 RCX: ffffbb3f0549f890
Oct 30 15:05:11 archlinux kernel: RDX: ffffbb3f0549f888 RSI: 0000769ca002f000 RDI: ffff9e85e1e02730
Oct 30 15:05:11 archlinux kernel: RBP: ffffbb3f0549f8d0 R08: ffffbb3f0549fa28 R09: 0000000000000000
Oct 30 15:05:11 archlinux kernel: R10: 000000000040002c R11: ffffffffc111ee9e R12: ffffbb3f0549f890
Oct 30 15:05:11 archlinux kernel: R13: ffffbb3f0549f888 R14: ffff9e85c6945280 R15: 0000000000000000
Oct 30 15:05:11 archlinux kernel: FS:  000075ea7ed8bb80(0000) GS:ffff9e8cddf00000(0000) knlGS:0000000000000000
Oct 30 15:05:11 archlinux kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 30 15:05:11 archlinux kernel: CR2: 0000000000000003 CR3: 000000019687c000 CR4: 0000000000f50ef0
Oct 30 15:05:11 archlinux kernel: PKRU: 55555554
Oct 30 15:05:11 archlinux kernel: Call Trace:
Oct 30 15:05:11 archlinux kernel:  <TASK>
Oct 30 15:05:11 archlinux kernel:  ? follow_pte+0x1de/0x200
Oct 30 15:05:11 archlinux kernel:  ? __warn.cold+0x8e/0xe8
Oct 30 15:05:11 archlinux kernel:  ? follow_pte+0x1de/0x200
Oct 30 15:05:11 archlinux kernel:  ? report_bug+0xff/0x140
Oct 30 15:05:11 archlinux kernel:  ? handle_bug+0x3c/0x80
Oct 30 15:05:11 archlinux kernel:  ? exc_invalid_op+0x17/0x70
Oct 30 15:05:11 archlinux kernel:  ? asm_exc_invalid_op+0x1a/0x20
Oct 30 15:05:11 archlinux kernel:  ? follow_pte+0x1de/0x200
Oct 30 15:05:11 archlinux kernel:  follow_phys+0x49/0x110
Oct 30 15:05:11 archlinux kernel:  untrack_pfn+0x55/0x120
Oct 30 15:05:11 archlinux kernel:  unmap_single_vma+0xa6/0xe0
Oct 30 15:05:11 archlinux kernel:  zap_page_range_single+0x122/0x1d0
Oct 30 15:05:11 archlinux kernel:  unmap_mapping_range+0x116/0x140
Oct 30 15:05:11 archlinux kernel:  nv_revoke_gpu_mappings_locked+0x47/0x70 [nvidia 1400000003000000474e55009c5f68e515278c81]
Oct 30 15:05:11 archlinux kernel:  nv_set_system_power_state+0x1cd/0x480 [nvidia 1400000003000000474e55009c5f68e515278c81]
Oct 30 15:05:11 archlinux kernel:  nv_procfs_write_suspend+0xef/0x170 [nvidia 1400000003000000474e55009c5f68e515278c81]
Oct 30 15:05:11 archlinux kernel:  proc_reg_write+0x5a/0xa0
Oct 30 15:05:11 archlinux kernel:  vfs_write+0xf5/0x460
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? get_page_from_freelist+0x16db/0x1970
Oct 30 15:05:11 archlinux kernel:  ksys_write+0x6d/0xf0
Oct 30 15:05:11 archlinux kernel:  do_syscall_64+0x82/0x190
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? page_counter_uncharge+0x33/0x80
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? drain_stock+0x68/0xa0
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? __refill_stock+0x81/0x90
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? refill_stock+0x1a/0x30
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? try_charge_memcg+0x5dd/0x630
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? __mod_memcg_lruvec_state+0xa0/0x150
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? __lruvec_stat_mod_folio+0x83/0xd0
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? set_ptes.isra.0+0x41/0x90
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? do_anonymous_page+0xfe/0x870
Oct 30 15:05:11 archlinux kernel:  ? __pte_offset_map+0x1b/0x180
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? __handle_mm_fault+0xbe7/0x1030
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? __count_memcg_events+0x58/0xf0
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? count_memcg_events.constprop.0+0x1a/0x30
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? handle_mm_fault+0x1bb/0x2c0
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? do_user_addr_fault+0x36c/0x620
Oct 30 15:05:11 archlinux kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Oct 30 15:05:11 archlinux kernel:  ? exc_page_fault+0x81/0x190
Oct 30 15:05:11 archlinux kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Oct 30 15:05:11 archlinux kernel: RIP: 0033:0x75ea7ef23ca4
Oct 30 15:05:11 archlinux kernel: Code: c7 00 16 00 00 00 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 80 3d 05 94 0d 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 53 48 83 ec 20 48 89 54 24 18
Oct 30 15:05:11 archlinux kernel: RSP: 002b:00007ffcd7355fa8 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Oct 30 15:05:11 archlinux kernel: RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 000075ea7ef23ca4
Oct 30 15:05:11 archlinux kernel: RDX: 0000000000000008 RSI: 000057891724bd40 RDI: 0000000000000001
Oct 30 15:05:11 archlinux kernel: RBP: 000057891724bd40 R08: 0000000000000000 R09: 0000000000000400
Oct 30 15:05:11 archlinux kernel: R10: 0000000000000001 R11: 0000000000000202 R12: 0000000000000008
Oct 30 15:05:11 archlinux kernel: R13: 000075ea7eff6600 R14: 000075ea7eff4010 R15: 000075ea7eff3ec0
Oct 30 15:05:11 archlinux kernel:  </TASK>
Oct 30 15:05:11 archlinux kernel: ---[ end trace 0000000000000000 ]---
Oct 30 15:05:11 archlinux kernel: ------------[ cut here ]------------

Causes some monitors to sometimes not wake from sleep.
Also causes some other weird bugs like layouts swapping monitors on certain DEs.

1 Like

Known issue. Should be resolved/obsoleted by API changes included with kernel 6.12.

See:

-and-

1 Like

Ah thanks. Just tested with 6.12 rc and looks like it works. No more errors and no more troubles with suspend.
Hopefully itā€™s completely fixed, but will update if occurs again.

This is fixed! Thank you! I can finally just launch programs on my laptop without weird work arounds.

Seems true. My monitor also didnā€™t wake once today. But at least it works in most cases. In previous releases my machine didnā€™t resume after suspend at all.

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

This nvidia-sleep kernel ooops is still happening , when can you fix this?!

Are you reading the thread?

From today:

Try kernel 6.12 and let us know your results.

Donā€™t think all the Unreal Engine editor crashes have been fixed, still getting a crash and itā€™s easily to replicate. Open project built on older version eg. 5.1 in a newer version eg. 5.4, select make a copy and then give it a few seconds and it crashes. Didnā€™t happen on 535, it takes a little longer before crashing compared to 555 and 560 which crashes near instantly.

Operating System: Arch Linux
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.5-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 Ɨ 12th Gen IntelĀ® Coreā„¢ i5-12400F
Memory: 62.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
Manufacturer: ASUS

LoginId:5dd1433c01064299ae5582f2547adf36-000003e8

Caught signal 11 Segmentation fault

libnvidia-glcore.so.565.57.01!UnknownFunction(0xa14fc7)
libnvidia-glcore.so.565.57.01!UnknownFunction(0xe14868)
libnvidia-glcore.so.565.57.01!UnknownFunction(0xe14b4f)
libnvidia-glcore.so.565.57.01!UnknownFunction(0xd5005d)
libUnrealEditor-VulkanRHI.so!VulkanRHI::FFenceManager::WaitForFence(VulkanRHI::FFence*, unsigned long long) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanMemory.cpp:4690]
libUnrealEditor-VulkanRHI.so!FVulkanSwapChain::AcquireImageIndex(VulkanRHI::FSemaphore**) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanSwapChain.cpp:732]
libUnrealEditor-VulkanRHI.so!FVulkanViewport::Present(FVulkanCommandListContext*, FVulkanCmdBuffer*, FVulkanQueue*, FVulkanQueue*, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanViewport.cpp:916]
libUnrealEditor-VulkanRHI.so!FVulkanCommandListContext::RHIEndDrawingViewport(FRHIViewport*, bool, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanRHI.cpp:1184]
libUnrealEditor-RHI.so!FRHICommand<FRHICommandEndDrawingViewport, FRHICommandEndDrawingViewportString2188>::ExecuteAndDestruct(FRHICommandListBase&, FRHICommandListDebugContext&) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/RHI/Public/RHICommandList.h:1295]
libUnrealEditor-RHI.so!FRHICommandListBase::Execute(TRHIPipelineArray<IRHIComputeContext*>&, FRHICommandListBase::FPersistentState::FGPUStats*) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RHI/Private/RHICommandList.cpp:477]
libUnrealEditor-RHI.so!UE::Core::Private::Function::TFunctionRefCaller<FRHICommandListImmediate::ExecuteAndReset(bool)::$_0, void ()>::Call(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Templates/Function.h:405]
libUnrealEditor-Core.so!TGraphTask<TFunctionGraphTaskImpl<void (), (ESubsequentsMode::Type)0> >::ExecuteTask(TArray<FBaseGraphTask*, TSizedDefaultAllocator<32> >&, ENamedThreads::Type, bool) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Async/TaskGraphInterfaces.h:1235]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksNamedThread(int, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:760]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksUntilQuit(int) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:650]
libUnrealEditor-RenderCore.so!FRHIThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RenderCore/Private/RenderingThread.cpp:330]
libUnrealEditor-Core.so!FRunnableThreadPThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/HAL/PThreadRunnableThread.cpp:25]
libUnrealEditor-Core.so!FRunnableThreadPThread::_ThreadProc(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Private/HAL/PThreadRunnableThread.h:187]
libc.so.6!UnknownFunction(0x9439c)
libc.so.6!UnknownFunction(0x11949b)

Some additional feedback: after using driver 565 a little further, it seems Iā€™ve been hit by the resume bug that seems to plague kernels < 6.12 (itā€™s intermittent, but happens quite often). I guess Iā€™ll have to wait until kernel-6.12 is officially released.

EDIT: it seems to happen more frequently (only?) with automatic suspend; forcing suspend by pressing the power button usually donā€™t cause any problems with resume.

2 Likes

Good morning,
Debian 12,

  1. nvidia-smi not available:

nvidia-smi : Dipende: nvidia-alternative (= 560.35.03-1)
Dipende: libnvidia-ml1 (= 560.35.03-1) ma la versione 565.57.01-1 sta per essere installata
Raccomanda: nvidia-kernel-dkms (= 560.35.03-1) ma la versione 565.57.01-1 sta per essere installata oppure
nvidia-kernel-560.35.03 oppure
nvidia-open-kernel-560.35.03 ma non ĆØ installabile
E: Impossibile correggere i problemi, ci sono pacchetti danneggiati bloccati.

  1. glxinfo error:
    libGL error: glx: failed to create dri3 screen
    libGL error: failed to load driver: nouveau

do you have any solution?

Thank you.

Plasma 6.2.2. Wayland session. SDDM wayland also.
Linux 6-11.5 xanmod.
Nixos.
Main monitor. 1440p 240HZ. Display port.
Second monitor 1080p 60HZ. HDMI.
Using proprietary driver.

Since the release of Nvidia beta driver and installing in the same day, Iā€™ve occasionally encountered an issue (for the third time yesterday) where one of my monitors will unexpectedly freeze on a single frame.

As for example: yesterday, one of my monitor ā€œfreezeā€ at 00.53. After 30 minutes ( in 01.23 ), kwin crashed.
In dmesg | grep nvidia this error appeared:

Nov 01 01:23:08 Nix kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Flip event timeout on head 1
Nov 01 01:23:11 Nix kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000b00] Flip event timeout on head 1

Couldnā€™t find the way to trigger/reproduce this issue reliable.
All three times this issue has occurred, it happened a few minutes (7ā€“10) after closing a game running through Wine +vkd3d ( Wow, DeadByDaylight ). Might be coincidence.
Full kwin journal attached.

nvidia-bug-report.log.gz (1.2 MB)
kwin_debug.txt (45.9 KB)

1 Like

Even on 565 I have this bug on wayland where if I open another app while playing a certain game minimizing it, and then I maximize the game again, then this happens

the game is running on xwayland

Iā€™m running into this on open drivers as well. Seems to be happening randomly.
Main monitor: 1080p, 144Hz, DP
Secondary monitor: 1080p, 60Hz, HDMI

[15108.516543] NVRM: nvAssertFailedNoLog: Assertion failed: CliGetEventInfo(rpc_params->hClient, rpc_params->hEvent, &pEvent) @ kernel_gsp.c:463
[15108.516551] NVRM: _kgspProcessRpcEvent: Failed to process received event 0x1003 (POST_EVENT) from GPU0: status=0x57
[15308.895094] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1
[15312.031036] [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000700] Flip event timeout on head 1

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

Hi all,

This issue has been fixed. The fix should be available in our upcoming driver releases.

Thank you

4 Likes

Dear NVidia, Iā€™d like to request some extra release of elg-wayland, especially with this patch included egl-wayland: Handle failure to acquire image in wlEglSendDamageEvent Ā· NVIDIA/egl-wayland@218f678 Ā· GitHub .
Maybe call it version 1.16.1 or something.
Thanks in advance!

I installed kernel 6.12.0rc5 on Fedora 41 from Fedora Rawhide, and gave it a shot with driver 565.57.01 to try to work around the suspend issues with kernels < 6.12. Second monitor plugged to HDMI (which is wired to Nvidia dGPU) doesnā€™t come up, it isnā€™t even recognized by GNOME. Had to revert back to kernel 6.11.5 in order to be able to use it again. Iā€™m attaching nvidia-bug-report below.

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

It needs additional patches for 6.12-rcā€¦ not sure if Fedora got them

1 Like

I was using it on arch with a 2070 Super, and a lot of things are broken

As far as i know, the only extra config Iā€™m using is nvidia-drm.modeset=1

I set my resolution with
nvidia-settings -a CurrentMetaMode=ā€œDP-2: 1920x1080_240 @1920x1080 +0+0 {ForceCompositionPipeline=Off, ForceFullCompositionPipeline=Off}ā€

  • All my games are stuttering, probably shader compilation stuff, I had no such issues on 560
  • My window manager is just blackscreened after waking from sleep. (Iā€™m using i3wm inside of KDE on X11). I still have access to my terminal but I canā€™t see anything. If I kill my compositor (picom) I can see again, but everything KDE is completely unresponsive (such as the KDE panel and the system settings app, the plasmashell process is using 100% of one of my CPU cores permanently). killing sddm or rebooting fixes the issue, until my computer goes to sleep again
  • One time my entire wm just hard-froze, I had to go into a different tty and kill it manually
  • Steam was acting strange in general. I could not close the app normally without killing the process
  • It would forget that Iā€™m using a 240hz monitor 50% of the time when I rebooted, and sometimes switching it back to 240hz didnā€™t work without another reboot
  • Minor things like the resolution of my tty being different form my monitorā€™s native resolution for some reason

I reverted back to 560 and everything is butter smooth. No more stuttering, no more crashes, no more issues after sleep

Since upgrading to 565 DeadLock have been building shaders every single boot. After some investigation my ~/.cache/nvidia/GLCachehas not had any files changed since before the upgrade from 560 to 565. My ~/.nvfolder is also empty.

2 Likes