Alsa causing problems again

[krohnjw]

Ok, here's the skinny. For some reason alsa has decided to just load with ALL volumes muted each time I reboot. Now, this isn't a huge problem, as reboots are few and far between, but it is bothersome. This has never happened until now, even after the update to 10.1 (this is a mdk box).

However, on one reboot it couldn't load the settings and thus muted everything. Now, no matter what I do, it loads all volumes as default, even though the asound.state file states otherwise. Anyone have any ideas on making also load properly outside of just editing the init script to force it to use a file i specify? (this is about where my patience is right about now with ALSA)

All of the mixer settings are set properly and the driver is fine. Loading the sound module without alsa results in proper volumes, but lack of many audio options I even went ahead and recreated the darn file thinking that for some reason it might not be able to access it. Still nothing will make it load default volumes. This is the same kernel and module it worked fine with for months. Sound all works fine, it is just the default alsa volumes that will not load.

[James T]

In slackware I use alsamixer to set, alsactl store to create the asound.state file and that seems to work fine. I have found that kde sound likes to load it's own volume settings as well and this can override (coming second). I've gone through all the logins and set this setting in kde NOT to load. This was noticeable in my case because the kde defaults were stupid and caused a feedback loop. It might be that your equivalents just turn it quiet?

[krohnjw]

KDE isn't set to load volumes on login, and I verified earlier that alsactl was saving the file correctly.

It seems to certainly be easier to just modify the init script for the stop and start instructions to save/load a specific file and see how that works.