Description of problem: /etc/udev/rules.d/90-alsa.rules looks like: SUBSYSTEM=="sound", KERNEL=="controlC*" RUN+="/sbin/salsa" SUBSYSTEM=="sound", KERNEL=="pcm*" RUN+="/sbin/salsa" I believe running "salsa" without arguments does not restore the settings. Wouldn't something like: SUBSYSTEM=="sound", KERNEL=="controlC*" RUN+="/sbin/salsa -l %n" SUBSYSTEM=="sound", KERNEL=="pcm*" RUN+="/sbin/salsa" be better? [With the controls messed up, running 'salsa' from root console seems to do nothing. Running 'salsa -l 0' does in fact restore the settings.] Is the second line ("pcm*") needed? Version-Release number of selected component (if applicable): alsa-utils-1.0.15-0.4.rc1.fc8 How reproducible: every time Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
/sbin/salsa w/o argument is specially designed for this purpose. It loads the card number from ENV (it's set by udev) and loads stored volume from disc.
If the volume loading doesn't work for you it could be a dupe of Bug 247468.
Nah, working now. [Sorry, filed this after running 'salsa' from terminal without udev's env variables...] I think this was and issue with SELinux blocking alsa_t access to /etc/alsa/asound.state, etc. Closing. Thanks for looking into this.