I wrote the order “systemctl status alsa-restore.service” and did not work
In any case, it would be …
systemctl enable alsa-restore.serviceand then reboot
Edit: @koliadelis → welcome!!!
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:
• A unit may be statically enabled by being symlinked from another unit’s
.wants/ or .requires/ directory.
• A unit’s purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, …).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
hello!I have a problem for alsamixer, when I make a change of setting after reboot no save settings,
please help me, what to do to maintain the settings? I installed it antergos deepin I wrote the order “systemctl status alsa-restore.service” and did not work thanks!!!