Another bug to report on the latest 565 series regarding CTMs which we thought was fixed in 560. Spamming night light or screen filters too much still causes entire displays to freeze. This is especially noticeable when Hyprland added a fade animation to these screen filters. The freezes now occur every time without fail. Here is the info I left on the 560 thread:
Looks like this old bug has come to haunt us still. It was not fully fixed. Hyprland recently implemented fading of these CTMs (including the night light filter from hyprsunset) and the issue is back. On my multi monitor setup (not a PRIME setup) toggling the night light causes one of my monitors to freeze literally EVERY time. Can bring my stuff back by going to tty2 and back to tty1.
here is the bug from the repro state, and running on nvidia open kernel modules version 565.77: nvidia-bug-report.log.gz (535.1 KB)
Repro steps:
launch hyprland on latest master and ensure you have hyprsunset latest master also installed / executable. Ensure youāre using a multi monitor setup. Simply run hyprsunset with the simple command hyprsunset -t 2000
you will notice at least one of the screens freeze, maybe both.
Hopefully this issue is observable on your end.
Hyprland has now since disabled these animations by default to nvidia bugs. To repro, you must now also re enable the animations by adding
render {
ctm_animation = 1
}
to the hyprland config at ~/.config/hypr/hyprland.conf and then attempt to run the blue light filter hyprsunset again.
This is extremely simple to repro, hopefully it can be fixed soon.
Iām using Nobara 41 with the Nvidia 565.77. Iām using 2 outputs, one LG OLED and a LG Ultragear. When I turn on HDR on KDE, it turns HDR on my TV but not on my monitor. Tried using the Kwin to turn on HDR but only changes the TV and not the monitor.
This may be relegated to 4000 series cards, as Iāve heard of 3000 series not having issues.
Again, really wish we could could know if the driver team is still alive, its been radio silence for a 570 release.
At least back when I had a 5700XT I could read a bunch of Valve and AMD engineers arguing about AMDGPU kernel driver implementation details. The bickering at least gave me hope.
Hi @luanv.oliveira
We have a bug 5004630 filed internally for tracking purpose.
However, we are still not able to reproduce issue in house and trying to debug it with the shared logs.
Something happened after version 416, and the display backlight has been off ever since. In this case a $7K razerblade pro 17" laptop with 4K IGZO G-Sync Nvidia - unreadably dark. Have been asking here for a fix for years.
Itād be great to get a JOB at NVidia, to gain access the secret source-code, and see what happened after version 416 and release a fix for everyone! LoL!
I wonder whether NVidia cares about computer graphics anymore? Is it all AI, bitcoin, and self-driving cars?
This IS the problem with closed source codeā¦ You cannot fix it. You have to beg & plead. Itās horrible.
Path of exile 2. Using Directx12 renderer, because vulkan broken atm on 565.
NixOS. Kwin wayland.
Proprietary driver.
6.12.9 kernel.
RTX 3090.
While playing/lvling on my new character, after some time of playing, both monitors freeze for are few seconds, then PoE2 just stuck on 1 frame, while everything else working normally after that. I keep hearing sound from PoE2, however.
This happens only on my new character for some reason. Probably related to āgemsā/combination of passives with gems? that Iām using on this character, because I have 2 other characters and never faced this issue on them. journalctl -b 0 | grep kwin
Jan 10 15:17:33 Nix kwin_wayland[1788]: kwin_core: Cannot grant a token to KWin::ClientConnection(0x1bc3a7c0)
Jan 10 15:24:05 Nix kwin_wayland_wrapper[1882]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Jan 10 15:24:05 Nix kwin_wayland_wrapper[1882]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Jan 10 15:24:06 Nix kwin_wayland_wrapper[1882]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Jan 10 15:24:06 Nix kwin_wayland_wrapper[1882]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Jan 10 15:24:06 Nix kwin_wayland_wrapper[1882]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
Jan 10 15:24:06 Nix kwin_wayland_wrapper[1882]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
journalctl -b 0 | grep NVRM
Jan 10 15:24:09 Nix kernel: NVRM: Xid (PCI:0000:0b:00): 109, pid='<unknown>', name=<unknown>, Ch 000000c4, errorString CTX SWITCH TIMEOUT, Info 0x7ec069
Absolute nightmare , no matter what I do I get stuck on the Ubuntu 22.04 splash screen. It also has issues with so many Nvidia softwares like DeepStream, GXF, Omniverse, TensorRT, CUDNN. Ubuntu kernel 6.8 seems to reject Nvidia drivers and Wayland makes things even worse.
Hi!
Iāve been having some weird issues with my 4080 and my 4k 196hz screen.
Whenever I detach the popup video player in a web browser, be it firefox or any other, I get glitches on the bottom right corner of the screen.
Sometimes, I also get the glitches by having a video in full screen (via a browser, I havenāt been able to reproduce it by simply using a video player, VLC for example).
Iāve tried it in CachyOS KDE and Manjaro Gnome and the same problem persists.
I also tried using X.org instead of Wayland and the problem continues, sometimes even worse.
The thing is, it only happens when my monitor is set at 165hz. Anything lower than that and the glitches are no longer visible.
Not sure if anyone have a clue on anything I could do to mitigate the issue.
Same thing happened to me and, after trying many things, what solved it for me was setting a window rule in Plasma to force allow tearing for Firefox. Give it a try.
Hm, I did what you recommended and I did get some results. Now when keeping the video player connected to the main window I get way less glitches, same with the video in fullscreen.
However, for the floating window I still get the same glitches I did before. I did add the window rule to the picture in picture window but still nothing.
Also tried the same with Brave and the picture in picture add-on and getting the same results.
Thanks for the suggestion tho!
Iāll keep trying things and post here if I find a solution.
My issue is related with my monitorās DSC and Wayland, it seems. In X11 the glitches disappear and Wayland without DSC also works fine. Theyāre the same glitches/artifacts on the same area of the screen.
The source of the problem may not be the same in both cases, but itās curious that the symptoms are exactly the same. I hope a future driver solves it.
Iāve been looking into it a bit more and it seems to be exactly the same issue sowed in DisplayPort DSC 4K@240Hz flickering artifacts
apparently, he was able to fix it by disabling the āallow flippingā option in the nvidia control panel.
So I tried it in the X session and indeed, it seems to fix the issue. But the X session in laggy and full of tearing. Not to mention some of the newest functions of KDE do not work properly there.
Iāve been looking to see if there was a way to disable that āflippingā option in wayland but found none.
there is a display detection issue with hdmi 2.1 that only happens on linux, if the display power cycles while on the desktop sometimes the display will receive no signal, the behavior seems dependant on the resolution/refresh rate that the display was set at the moment (all of these are with vrr on auto in kde):
1920x1080@60HDR: OK
1920x1080@60SDR: OK
1920x1080@120HDR: OK
1920x1080@120SDR: OK
1920x1080@144HDR: failed to set this mode at all
1920x1080@144SDR: failed to set this mode at all
2560x1440@60HDR: OK
2560x1440@60SDR: OK
2560x1440@120HDR: no signal after monitor power cycle
2560x1440@120SDR: no signal after monitor power cycle
2560x1440@144HDR: no signal after monitor power cycle
2560x1440@144SDR: no signal after monitor power cycle
no 60hz or 120hz on 4k for some reason
3840x2160@30HDR: OK
3840x2160@30SDR: OK
3840x2160@144HDR: no signal after monitor power cycle
3840x2160@144SDR: no signal after monitor power cycle
every time there is no signal i have to suspend the computer remotely, after waking it up it will detect the display.
i didnāt test as extensively over diplayport but i can confirm that 3840x2160@144HDR doesnāt have this issue.
Hey wassup people just to let you guys know the new Nvidia drivers 565.77 broke Assassinās Creed Valhalla, some weirds graphicals glitches making the game unplayable could it be fix on the new drivers update ?
Iāve been running more stable than ever before for months on 565.77/ 6.12 Kernel/ 3080 eGPU/ Arch/ Wayland/ KDE. Just want to say thanks to the devs, the work over the last few drivers has been so much better. All gaming, general desktop response and overall experience is 10x improved. Work is much appreciatedā¦
