You are not logged in.
Recently, I've encountered a problem wherein my ALSA settings are not stored, even though I have the alsa daemon running. The relevent settings are for PCM and CD - when I shut down, both are at 100 and unmuted; after booting, PCM is at 100 and muted, and CD is at 0 and muted. Any other changes I make are also lost on the next bootup. What is going on?
Offline
same here. I suspect its a udev thing; the devices haven't had time to set up when alsa is called. I added
sleep 5
underneath
stat_busy "Restoring ALSA Levels"
in /etc/rc.d/alsamixer and it works ok. Since I background the alsa daemon, this doesn't slow down bootup. THere's got to be a better way.
Dusty
Offline
I assume you've done an
alsactl store
Then you can restore with
alsactl restore
in rc.local. Tho, I think you might know that asready
Offline
I use the alsa script in /etc/rc.d - does the same thing. (Yes, it uses alsactl.)
Offline
I use the alsa script in /etc/rc.d - does the same thing. (Yes, it uses alsactl.)
Ditto - the /etc/rc.d/alsa script is part of one of the alsa packages now (alsa-lib?)
Offline
Yeah, that's the script I meant. Regardless, it only seems to work if you give udev time to propogate the devices. Maybe there's a way to set them up automatically. THis was discussed a while ago. I had to use the sleep 5 solution on my old system, but when I set up my new one it was working fine until recently (ie: with all the kerfluffle over udev).
Dusty
Offline
Ummm another thing to point out - if your module isn't loaded at the time of the alsa call, nothing will happen - if you are either:
a) running alsa *before* hotplug
b) backgrounding hotplug
This could be the cause - if you're running hotplug, run it before alsa as a non-backgrounded service (or dump it altogether, or use /etc/rd.c/hwd)
Offline
True enough. I don't use hotplug though; I load my modules in the MODULES array.
Dusty
Offline
True enough. I don't use hotplug though; I load my modules in the MODULES array.
I was talking to the original poster, heh
Offline
I was talking to the world at large.
I'm not sure how hotplug works, but does it ensure that the devices have been created by udev before exiting? Because if it just loads the modules and tells udev to have at it, its not going to solve the issue.
Assuming, of course, that I am correct in assuming that the delay is in udev's creating the devices.
Dusty
Offline
I don't use hotplug. Hotplug, in my experience, sucks.
As for my situation with the sound, it's the same as Dusty's: this didn't happen until the latest udev upgrade.
(Hmm... Why should udev take so long to do its job?)
Offline
What if you compile your ALSA stuff into the kernel rather than as modules?
Offline
Wouldn't help, this is a udev problem.
Offline
I would think it should be possible to make a udev rule to create the specific sound devices statically. Or maybe those devices could specifically be populated to /dev using mknod commands. I wonder...
Dusty
Offline