https://bugs.kde.org/show_bug.cgi?id=477738
--- Comment #62 from Fotios Valasiadis <fvalas...@gmail.com> --- (In reply to Nate Graham from comment #61) > Thanks everyone. So I brought this to the attention of a KWin developer who > brought it to the attention of an NVIDIA developer. > > The conclusion here is that NVreg_PreserveVideoMemoryAllocations=1 is not a > workaround, and *should be* used. The only reason it's not turned on by > default is because if it's turned on without the appropriate pre-suspend > hooks in place, suspend will get broken. NVIDIA distributed systemd unit > files for these hooks, but they don't trust distros and users to install and > activate them, and of course those using non-systemd distros will have to > figure something else out as well. So they leave it off by default to avoid > having to handle those cases. > > This information has been added to > https://community.kde.org/Distributions/ > Packaging_Recommendations#Proprietary_NVidia_driver_configuration, and I've > emailed distros about it. > > So from a KDE perspective this is basically a downstream/distro issue at > this point. I encourage everyone to go contact their distros about it as > well, and ideally submit patches if you're a distro packager or like to play > one on TV. Honestly, replicating the exact same systemd scripts you mention to get suspend working on runit did not work for me. Looking online I found other users experiencing the same exact problem when enabling NVreg_PreserveVideoMemoryAllocations=1 even on systemd distros using the exact same setup. Back to debugging I guess. -- You are receiving this mail because: You are watching all bug changes.
