Volume Levels Set With alsamixer Don't Persist On Reboot
BodhiThis forum is for the discussion of Bodhi Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Volume Levels Set With alsamixer Don't Persist On Reboot
Hello,
I am not quite a Linux Newbie but am quite new to Bodhi.
I am able to set audio volume levels with alsamixer, but when I reboot all the settings are lost, and the setting are restored to where they were when I first logged in after installation. If someone could help me figure out how to make audio volume level persist on a reboot, I would appreciate it.
As root, once you have the volume set as you wish, run the command 'alsactl store' ( without the quotes ) should store the current value. See the man page for more details.
Thanks, but it didn't work. Neither sudo nor actually logging in as root and saving settings worked. When I rebooted the same totally weird setting were in place, rather than the ones I wanted.
May I ask a question: Why aren't volume setting a per-user thing, and why aren't they automatically saved and restored on logging in and out?
I don't know what I am doing wrong, but just can't seem to get this to work.
why aren't they automatically saved and restored on logging in and out?
They are on my system. This is just a guess, I was wondering if Bodhi uses Pulse Audio? If yes, your problems probably lie there.
If not, there is something wrong wrong with your permissions, or groups your user belongs to. I don't run Bodhi, so I can not tell you what groups you need to belong to. To find out what groups your user belongs to, run the command 'groups' ( without quotes ) and you should get a list of the groups your user belongs to. Another guess, add yourself to the audio group, if you do not belong to it.
There is usually only one active audio device at one time. Multiple users logging in with different settings would be havoc.
I had a similar problem after doing a regular update on my PCLinux with KDE. If I changed the settings and logged out or logged back in the volume was at 100% which was pretty annoying. I used alsamixer and it only showed two options: Master and PCM which was a little odd. The Kmix front end didn't save any changes either so I had an option in the control center to disable pulseaudio which I did and it works. The first thing I would suggest is to look for an option to disable it. The first link below explains removing it completely which might be a little drastic and the second link shows commands to remove, update and reinstall. I did an online search for "disable pulseaudio in Bodhi" and all I got were ways to remove. You might have better luck trying it.
1) i'm not sure what's going on because i don't have the problem
2) if it's pulseaudio related, i'm even more lost because i don't use it
3) bodhi linux does have its own forum
that said, looking at
Code:
man alsactl
i'm having a few ideas:
a) make sure that your system doesn't run "alsactl init" at startup or login
b) try a manual "alsactl (n)restore", does it help?
c) have a look at /var/lib/alsa/asound.state (nausea warning) - maybe you can find some clues
d) try saving and restoring settings to a different file with the "-f" option.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.