It requires root for nvidia-settings but fails each time I make my own autostart on systemd
[Unit] Description=NVIDIA Fan Control on Wayland Arch After=graphical-session.target [Service] ExecStart=sudo /home/rob/Documents/fan.sh User=root [Install] WantedBy=default.targetI’m not good with command line stuff but is sudo necessary if you’re already running as root?
nope
Post your service file and the output of the systemctl status command for your service when it fails to start. Otherwise we will just be guessing.
● fan.service - NVIDIA Fan Control on Wayland Arch Loaded: loaded (/etc/systemd/system/fan.service; enabled; preset: disabled) Active: active (running) since Tue 2023-10-17 18:29:39 EDT; 4s ago Main PID: 2691 (sudo) Tasks: 3 (limit: 38401) Memory: 5.9M CPU: 39ms CGroup: /system.slice/fan.service ├─2691 sudo /home/rob/Documents/fan.sh ├─2692 /bin/bash /home/rob/Documents/fan.sh └─2699 sleep 5 Oct 17 18:29:39 robpc systemd[1]: Started NVIDIA Fan Control on Wayland Arch. Oct 17 18:29:39 robpc sudo[2691]: root : PWD=/ ; USER=root ; COMMAND=/home/rob/Documents/fan.sh Oct 17 18:29:39 robpc sudo[2691]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0) Oct 17 18:29:39 robpc sudo[2694]: ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information. Oct 17 18:29:39 robpc sudo[2692]: Current GPU temperature: 0 Oct 17 18:29:39 robpc sudo[2698]: ERROR: The control display is undefined; please run `nvidia-settings --help` for usage information.The output here lets us know that systemd is running the service file and starting the script just fine. The echoed GPU temperature is making it to the journal, but the
gpuTempvariable isn’t being updated (staying at0) because of a problem executingnvidia-settings. Specifically, it wants a display: “The control display is undefined”.You could add a line to the service file:—
Environment = DISPLAY=:0
Although if
echo DISPLAYin your terminal gives you a different value, use that. There’s a possibility that that will just push one error further down the line, but it’s something to try.Alternatively/additionally, you could try changing the
User=line to your own username to see if it picks up the environment your manual executions work with.You aren’t the only one to run into problems trying to automate
nvidia-settings. You might end up needing to track down anXauthorityfile or use the display manager’s initialisation options.
- You shouldnt constantly check if that app is installed, especially not using package manager testing. Do it once.
- You forgot some argument to run the settings from CLI, it seems to try to launch a GUI
the reason for more than one elif is for different package managers like apt, yum and dnf, other than that it just skips it if the package is detected.
Afaik it uses cli to find the temperature. i couldnt set the temperature with nvidia-smi so i had to use nvidia-settings
gpuTemp=$(nvidia-settings -q gpucoretemp | grep ‘^ Attribute’ |
head -n 1 | perl -pe ‘s/^.?(\d+).\s$/\1/;’) echo -en “Current GPU temperature: $gpuTemp \r”Yes the loop is nice, but you know your packagemanager and that this package will not disappear randomly, so keep it out of this service script, its just an extra break point and wastes resources :D
The rest, idk
If it works when run manually, but fails via systemd, then you should post your service file.
As soon as I get home I’ll do it. Afaik if you try to run it normally without root access it spits out errors about not being able to set the fan speed because it uses nvidia-settings as a dependancy. Also failed to mention this is a Wayland script, not xorg
