<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Re: [PlanetCCRMA] Failure starting ALSA with an MAudio Delta 66</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
<BR>
I was getting the same problem, and I did some experimenting and found out the cause. Something takes a few seconds to load, so the command 'action "Restoring sound driver settings" $alsactl -f $asoundcfg restore' in /etc/init.d/alsasound fails because it happens right in the script, whereas the same command "alsactl restore" works because I type it in a few seconds later.<BR>
<BR>
There's a horrible hacky way to work around this: I added the line "sleep 5" (which makes the script wait for 5 seconds) to /etc/init.d/alsasound right before the line 'action "Restoring sound driver settings" $alsactl -f $asoundcfg restore'. It works now, but it takes an extra five seconds to load.<BR>
<BR>
Perhaps I should notify the alsa mailing list as well?<BR>
<BR>
--Mike George<BR>
<BR>
><BR>
> I think I get the same behaviour with my Tascam USB<BR>
> module. I could do store and restore and card 1 , but the<BR>
> script failed. (the tascam only has hardware mixers so<BR>
> store doesn't really do anything anyway). I just thought<BR>
> the error wasn't a real problem - just looks untidy<BR>
><BR>
> On Apr 1, 2005 4:25 AM, Brad Fuller <brad@sonaural.com><BR>
> > wrote: Fernando Lopez-Lezcano wrote:<BR>
> > On Thu, 2005-03-31 at 07:13, Brad Fuller wrote:<BR>
> > <BR>
> > <BR>
> > Fernando Lopez-Lezcano wrote:<BR>
> > <BR>
> > <BR>
> > On Mon, 2005-01-17 at 19:09, Brent Durbin wrote:<BR>
> > <BR>
> > <BR>
> > <BR>
> > Hi All,<BR>
> > I'm new to the whole Linux Audio thing and was hoping<BR>
> > you could help me out. I installed FC3 on my system that<BR>
> > has a MAudio Delta 66 card. I installed the PlanetCCRMA<BR>
> > stuff and updated to the Planet Edge so I could get ALSA<BR>
> > 1.0.8. When I do and alsasound restart I get: Shutting<BR>
> > down sound driver [ OK ] Starting sound driver<BR>
> > snd-ice1712 [ OK ] Starting sequencer [ OK ]<BR>
> > Restoring sound driver settings /usr/sbin/alsactl:<BR>
> > load_state:1267: No soundcards found...<BR>
> > [FAILED]<BR>
> ><BR>
> > Can anyone give me a clue as to what I should look at to<BR>
> > figure out what is wrong? Could it be a problem with<BR>
> > /etc/modprobe.conf? Here are the relevant lines:<BR>
> > alias snd-card-0 snd-ice1712<BR>
> > options snd-card-0 index=0<BR>
> > install snd-ice1712 /sbin/modprobe --ignore-install<BR>
> > snd-ice1712 && /usr/sbin/alsactl restore >/dev/null 2>&1<BR>
> > || : remove snd-ice1712 { /usr/sbin/alsactl store<BR>
> > >/dev/null 2>&1 || : ; }; /sbin/modprobe -r<BR>
> > --ignore-remove snd-ice1712<BR>
> > Also, envy24control starts, so I am pretty sure that I'm<BR>
> > using the correct kernel.<BR>
> > <BR>
> > <BR>
> > Meaning that the kernel module for the card is loaded<BR>
> > and the card is seen by envy24control? If so, you just<BR>
> > probably need to store the state of the mixer (some<BR>
> > settings and/or controls may have changed in the new<BR>
> > alsa). Do: /usr/sbin/alsactl store<BR>
> > And then:<BR>
> > /usr/sbin/alsactl restore<BR>
> > It should not complain anymore...<BR>
> > <BR>
> > <BR>
> > Just want to add that I also have a Delta66 and have<BR>
> > the same problem. I've done the store/restore but still<BR>
> > it doesn't remember. I too receive the following error<BR>
> > when restarting alsa:<BR>
> > Restoring sound driver settings /usr/sbin/alsactl:<BR>
> > load_state:1272: No soundcards found... [FAILED]<BR>
> ><BR>
> > This seems to be a msg that should go to the ALSA dist<BR>
> > list.<BR>
> > Have you tried to redo the mixer state from scratch?<BR>
> > Delete or move away /etc/asound.state, then fire your<BR>
> > mixer, get the settings done and "/usr/bin/alsactl<BR>
> > store".<BR>
> > -- Fernando<BR>
> > <BR>
> > just tried what you suggested. no change.<BR>
> > <BR>
> > /usr/sbin/alsactl store and restore work fine, though.<BR>
> ><BR>
><BR>
<BR>
Hi,<BR>
I at least found out what causes the trouble on my machine<BR>
even so I didn found a solution yet. A report:<BR>
I start the machine and the sounddriver is loaded fine<BR>
(alsasound status).<BR>
After starting the jack server and hydrogen for example i<BR>
have<BR>
got no sound comming out. When I open the alsamixer all the<BR>
settings are zero even so I stored them with<BR>
(/usr/sbin/alsactl store 0) the last time. So when I change<BR>
the dac of the alsamixer or do a (/usr/sbin/alsactl restore<BR>
0) I get sound out of the machine. When I stop alsasound and<BR>
start it again I get<BR>
the same errors than all the others.<BR>
[root@pygmalion erikos]# /etc/rc.d/init.d/alsasound start<BR>
Starting sound driver snd-ice1712 [ OK ]<BR>
Starting sequencer [<BR>
OK ]<BR>
Restoring sound driver settings /usr/sbin/alsactl:<BR>
load_state:1272: No soundcards found... [FAILED]<BR>
<BR>
So I say that the /etc/asound.state can`t be loaded<BR>
properly. As far as I understand the script alsasound, it<BR>
does load as default (asound.state).<BR>
<BR>
Best Regards<BR>
Simon</FONT>
</P>
</BODY>
</HTML>