* Emanuele Morozzi ([EMAIL PROTECTED]) wrote: > I have esperienced your problem; in my case it was caused by the lack of > a var, and that that caused the mixer not to load the previously saved > settings. > > 1. Specifically in /etc/conf.d/alsasound I had to add this lines > RESTORE_ON_START="yes" > SAVE_ON_STOP="yes" > that referes to the mixer setup saving and restoring. > > 2. In make.conf see if the var > ALSA_CARDS="ens1371" > > 3. Be sure the correct module is loaded; use the alsa daemon or put the > module in /etc/modules.autoload.d/kernel-2.6 > using "cat snd-ens1371 >> /etc/modules.autoload.d/kernel-2.6" > (alsa daemon is preferred by me because it saves at 'stop' and restores > at 'start') the mixer level. > > Emanuele >
Many thanks for the tips. I took a look and ALSA_CARDS="ens1371" is in make.conf, and the two lines you mentioned are also in /etc/conf.d/alsasound. I am curious about number three. What exactly is the alsa daemon? Is that what is invoked by alsaconf? I do agree that the saving at stop which my system always did is nice and I hesitated going the modules.autoload.d method for that reason. Fortunately things do seem to be moving better now that I have copied back the old alsasound init.d script. The new one was empty which really fouled things up apparently. Thanks again, Patrick -- [email protected] mailing list
