I'm trying to install CUDA on my Ubuntu Budgie 17.10, with a GTX 1060. I'm stuck on this part of the instructions:


I've pasted the example into the specified file. When I try to run

sudo systemctl enable nvidia-persistenced

I get:

The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
   .wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
   a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
   D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
   instance name specified.

For reference, here's the exact content of my file:

Description=NVIDIA Persistence Daemon

ExecStart=/usr/bin/nvidia-persistenced --verbose
ExecStopPost=/bin/rm -rf /var/run/nvidia persistenced 


I don't know anything about these files, which is why I'm just copying and pasting - so I'd be happy if you could tell me what's wrong!

  • It is required by the nvidia service you installed earlier so run systemctl list-units | grep nvidia lets get the name of the service then add the line RequiredBy=<name-of-nvidia-service>, example RequiredBy=nvidia.service to the [Install] section and try that command again! Apr 21, 2018 at 17:40
  • If I grep nvidia I only find the process that I'm trying to enable (nvidia-persistenced.service) and interestingly enough it's marked as loaded active running. And yet even if I add the RequiredBy and try to enable it I still get the error message... But Thanks for the Hint!
    – anon
    Apr 21, 2018 at 20:08
  • What other nvidia service is seen in that query? Apr 21, 2018 at 20:16
  • None, just that one...
    – anon
    Apr 21, 2018 at 20:37
  • If that is the case then don't use that as a requirement in the install section! Apr 22, 2018 at 6:12

2 Answers 2


I may be a little late, but I hope this helps others with this.

From what I understand, you do NOT have a POWER9 system, not unless your system is a supercomputer.

According to this link and that.

Being a Linux rookie, I too was stuck on this for a long time.

Hope I helped.


You may want to reload systemd manager configuration first after making changes.

sudo systemctl daemon-reload

Then you can try to enable/start the service.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.