https://bugs.kde.org/show_bug.cgi?id=477738
--- Comment #60 from Victor Ryzhykh <victorr2...@yandex.ru> --- (In reply to Ilya Bizyaev from comment #57) > To me, it sounds like the “fix” above basically boils down to > NVreg_PreserveVideoMemoryAllocations=1, which is a well-known workaround: > https://wiki.archlinux.org/title/NVIDIA/ > Tips_and_tricks#Preserve_video_memory_after_suspend > > It basically saves the entire video memory to RAM or disk, then restores it. > I could be wrong, but I don't think requiring users to enable a hack is a > proper fix. I will return to this issue again. Before the latest changes to my configs, I periodically encountered problems after exiting sleep mode. This only happened when the dracut command was run after installing the nvidia kernel modules. If the dracut command was not executed after installing kernel modules, then I had no problems after waking up from sleep mode. Recently, after getting another error when waking up from sleep, I sent the log file to the nvidia developers, in this message https://forums.developer.nvidia.com/t/560-release-feedback-discussion/300830/241?u=victorr2007 I got a reply a few days later in this message https://forums.developer.nvidia.com/t/560-release-feedback-discussion/300830/262?u=victorr2007 It turned out that file /etc/modprobe.d/nvidia-power-management.conf was ignored in the wayland session. Then I decided to add a record about this file to file /etc/dracut.conf.d/10-nvidia560.conf, where I had previously added other configuration files for use. It turned out to be the right decision. Now everything works perfectly for me. I'm not sure that kde can restore video memory on its own when exiting sleep mode. -- You are receiving this mail because: You are watching all bug changes.
