first line has to do with backlight ajustment during boot
second line shall take care of a nice plymouth boot after sequence ‘kernel update - reboot (broken plymouth animations) - # dracut -f (new initrd file with restored plymouth animation)’
third line solved my hibernation & suspend issue that suddenly occured after an update this week
Maybe it works for you too; i have read it is a nvidia issue (just passing the solution, credits to others)
Glad to hear that too worked. If you wish you can ls the /usr/lib/modprobe.d/ dir, as mentioned in the thread I linked to a recent update either added or altered /usr/lib/modprobe.d/nvidia-power-management.conf so that it contained options nvidia NVreg_PreserveVideoMemoryAllocations=1 . To keep using the old nvidia power save mode I merely changed that to 0, I didn’t need to create a new config file.
In the end a suggestion in the thread made me lookup what this parameter does when the new power save mode is fully enabled and it preserves OpenCL for me in Darktable when the machine suspends. Merely changing the /usr/lib/modprobe.d/nvidia-power-management.conf param to 0 in order to keep using the old nvidia power save mode made suspend work but OpenCL was lost until relog if Darktable was running when the machine suspended.
/usr/lib/modprobe.d/nvidia-power-management.conf doesn’t exist if one uses the nvidia drivers from rpmfusion (like i do), guess if you use the proprietary nvidia driver that file does exist and peeps better follow your suggestion to alter that file.
nvidia-power-management.conf …at least for setting the variable.
I checked my terminal’s history just in case I had a mild case of amnesia and forgot that I made that file …(which would be weird since I found the gentoo bug and looked for the param and found it there but anyway) …but it went update, suspend, and then look for the param, where the first reference to nvidia-power-management.conf was to cat its contents.
So I don’t know whether you and everyone else in this thread have that file too and that the file you advice to create/edit overrides it or whether my machine is the only one who has that file. That feels wrong though since I installed via rpmfusion and there’s just the one proprietary nvidia driver afaik and the problem, very much echoed over the internet, is that the options nvidia NVreg_PreserveVideoMemoryAllocations=1 is set and it has to be set in a config file.
(I don’t want to argue or anything like that I’d just like to think the bug affected most people on fedora with the propriatery nvidia driver the same and would like to get to the bottom of it )
For all i know you can put all the options in /etc/modprobe.d/ in only one file. The fact one puts them in different files is just for our convenience.
So having a module option put in a different named file doesn’t matter, as long you don’t contradict (same option set in different files with different values). See man modprobe.d on your system.
So your options nvidia NVreg_PreserveVideoMemoryAllocations=1 line must be somewhere in a *.conf file located in /etc/modprobe.d/
Yeah. You mentioned nvidia-power-management.conf doesn’t exist for …and I’m still not certain what propietary nvidia driver or method your are referring to.
I don’t know that or whether the mentioned file does exist on other machines (I have no reason to believe it doesn’t); or indeed where the parameter line appeared on your machine after the update.
It doesn’t look as if this thread will provide answers, people are happy to create a new file and keep on using the old way to powersave nvidia cards. I’m merely glad I learnt about the new way as it has practical implications for me (and everyone else who likes to keep CUDA or OpenCL apps running when suspending their machine).