Hello! You wrote: > severity 703761 normal > thanks > > * Markus Raab <[email protected]> [2013-03-23 12:04 +0100]: > > Package: alsa-utils > > Version: 1.0.25-4 > > Severity: important > > > > During boot following messages are printed: > > Sat Mar 23 09:40:04 2013: [....] Setting up ALSA...warning: 'alsactl > > restore' failed with error message 'Found hardware: "EMU10K1" "SigmaTel > > STAC9708,11" "AC97a:83847608" "0x1102" "0x8066" Sat Mar 23 09:40:05 > > 2013: Hardware is initialized using a generic method Sat Mar 23 09:40:05 > > 2013: [ ok tl: set_control:1328: failed to obtain info for control #43 > > (No such file or directory)'...done. > > This are messages if you run a new alsa version. If you have > different kernels in use it might be possible that you boot > different alsa driver versions. alsa stores the mixer settings in > /var/lib/alsa/asound.state. To update this file simply run:
I neither upgraded alsa nor the kernel. I just removed a line in /etc/modules (to avoid the FATAL at bootup because the module does not exist anymore). # uname -a Linux markusbyte 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.24. # sudo alsactl --version alsactl version 1.0.25 > # man 1 alsactl Does not mention the error, nor that "init" might help in this case. I think this could be updated there. Or even better: mention in the log_action_cont_msg of /etc/init.d/alsa-utils that "alsactl init" might help (or even execute it). Strangely the man page says for restore: "If restoring fails (eventually partly), the init action is called." Btw. it is not checked if the alsactl -F restore $CARD >/dev/null 2>&1 fails? > # alsactl init > > You will get a working EMU10K1 ;-) Thanks, you are right that fixes the problem! But I really wonder how it was triggered. best regards Markus -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
