You are not logged in.
The 560 drivers should be out soon, they're in their second beta. No idea if they've fixed this issue, though.
Based on the Nvidia forums thread above, it doesn't look like they have fixed it yet...
Offline
I had display issues with newer drivers too. Every time my laptop sleeps the monitor turn off, move the mouse and when turn on, everything is frozen.
Sometimes a little slow but I can change to TTY2 , kill Xorg and reboot. Using a Legion 5 RTX 3060, external monitor via USB-C to DP adapter on Dell aw2724dm
On journal I had few errors like:
Xid (PCI:0000:01:00): 79, pid='<unknown>', name=<unknown>, GPU has fallen off the bus.
nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:6:0:0x0000000f
nvidia-modeset: ERROR: GPU:0: Error while waiting for GPU progress: 0x0000c67d:0 2:0:4048:4044
To test just open a terminal and try: sleep 1; xset dpms force off
Also tried few boot args, but nothing worked ( nvidia-drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_EnableGpuFirmware=0 )
What finally solved the problem is to downgrade every package to 550.x and compatible kernels.
I'm not using DKMS so I just downloaded the packages from https://archive.archlinux.org/
nvidia-550.90.07-4-x86_64.pkg.tar.zst
nvidia-settings-550.90.07-1-x86_64.pkg.tar.zst
nvidia-utils-550.90.07-4-x86_64.pkg.tar.zst
linux-6.9.6.arch1-1-x86_64.pkg.tar.zst
(If you're using LTS too)
linux-lts-6.6.36-1-x86_64.pkg.tar.zst
nvidia-lts-1_550.90.07-6-x86_64.pkg.tar.zst
Offline
On the Nvidia thread referenced above they (Nvidia) are now saying "Issue has been root caused and fix will be available in future release drivers." I don't know if this'll get merged into the 560 drivers or we'll have to wait for another one, but I'm *really* hoping it's the 560.
Offline
Saw an update in the NVidia thread that the issue has been resolved. I can confirm that things are working on my end again with:
nvidia-dkms-560.35.03-2
nvidia-settings-560.35.03-1
nvidia-utils-560.35.03-2
lib32-nvidia-utils-560.35.03-1
Offline
This issue returned with the 565 series drivers for me. It has been acknowledged by Nvidia and is expected to be fixed in the next beta driver release (570?).
Offline