Could someone please sort out the sound on my laptop. I have just finished messing around with blfs.

When I boot the machine, the sound is off. After each boot, I have to go into alsamixer as root and turn the sound on.

Also, when I boot the machine, the files in /dev/snd are created from scratch and they have permissions 660. So as a user I cannot read these files so the sound won't work until I give users read access.

I really would like the sound to work without all this messing about. Can someone tell me how I can boot the machine, put on the phones and sit back and enjoy?

Thanks

After setting up your volume levels and unmuting everything in alsamixer, run:

alsactl store

And it should store your mixer settings and restore them at the next bootup.

I had the same problem.

What i did was: booting as root changing setting using alsamixer after you boot with your user and never more you'll have to change your settings at boot.

I tried doing

alsactl store

after setting up alsamixer but on the next boot everything is muted again.
What does alsactl do exactly? I would like to check that it is working correctly and things are being set as they should.

Moved: This thread is more suitable in Linux-General and has been moved accordingly to help your thread/question get the exposure it deserves.

This sounds like a perfect candidate for rc.local. Depending on your distro, check out /etc/rc.d/rc.local. This file is run right before your login terminal is displayed. You could raise the alsa volume, store it, then copy that configuration file to a new location. Then in your rc.local script have it move the max volume configuration file over the current (muted) alsa file.
You could also change the permissions of your /dev/snd device in the rc.local script.
Basically, you just use rc.local to cleanup and mess or misconfiguration a reboot did.
Hope that helps

Sorry, I'm green when it comes to using alsa.

When you say 'move the max volume configuration file over the current (muted) alsa file' could you be more precise please.

Do I put something like -

alsactl -f configfilename restore

in rc.local?

Okay, when you raise the volume with alsamixer, then do "alsactl store", it will create a configuration file (one that has the volume turned up). You would copy this file somewhere else, let's say "alsaconf.on". Then in rc.local you would do something like "cp alsaconf.on alsaconf.default", ie: overwrite the muted alsa configuration file with the one that has volume. The alsactl restore option might work as well, I hadn't looked too heavily into what is available for alsactl.
So basically:
Basically you want to restore your "loud" settings on reboot.
Hope that clarifies a bit more. I would offer to give you the exact code, but I only ran into this problem a few distros ago, and the rc.local file from there is long gone.

You can run alsamixer as a normal user, but you should run "alsactl store" as root, so that the volume levels are restored to whatever you set when the sysem boots up. I don't think there is any need to put alsa stuff in rc.local.

okay - here's where I've got to with this -

I have created rc.local in /etc/rc.d with the following lines -

cp /etc/alsamix.conf /etc/asound.state
/usr/sbin/alsactl restore 0
chmod 666 /dev/snd


that's all that's in rc local. When I do

source /etc/rc.d/rc.local

as root, the sound works fine.
alsamix.conf is the alsa configuration file that I created from alsactl store with the sound turned on. chmod gives the user access to the sound files.

now the next problem. I am running lfs and lfs doesn't use rc.local so this file is not read at boot time. Where should I put these coomands to ensure they are executed after /dev/snd has been set up? Remember I want this to work when logging in as a user.

For LFS try this;

http://www.linuxfromscratch.org/blfs...lsa-utils.html


Sorry if this is old but I see it was left unresolved.