#How to save alsamixer settings?
1 messages · Page 1 of 1 (latest)
@little timber I think that's probably because we disable the Alsa State service. can you test to following to see if it works?
type in a terminal:
systemctl unmask alsa-state.service && systemctl enable --now alsa-state.service
then, try to change with alsamixer and reboot to see if it's reset again
I get "The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ 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.
"
that's ok, did you test alsamixer after that message?
Sorry for late answer, yeah and it didn't save through reboot
Any other ideas?
sorry, but I don't have any other suggestion.
remember to undo the thing:
systemctl disable --now alsa-state.service && systemctl mask alsa-state.service
something here may help you. take a look: https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture
Thanks, I think I solved the audio being low by switching output mode to “Analog Stereo Output + Mono Input” from "Pro Audio"
ah ye, you will always want to use Analog Stereo Output
it's the standard option to use
Pro Audio is only for professional equipment with lots of configurations