"alsasound start" into "/opt/bootlocal.sh": i do not like this solution.

[paskali]

Hi, to avoid the message that tell me the codec is not ready, i have tried a similar solution on my bootlocal.sh:

Code: [Select]

sleep 3s && /usr/local/etc/init.d/alsasound start
Some time work and some no; i do not really want to increase the number of seconds, for me it does not have much sense.

I have found a similar (ugly) solution too, to wait the xserver to start:

Code: [Select]

while [ ! -e /tmp/wm_errors ]; do
            sleep 0s
done
/usr/local/etc/init.d/alsasound start
I do not know if these messages are a problem; i have noticed on kernel message log by dmesg that this happen in any case when i load alsa.tcz, sound always works fine.

What do you thik about?

[Juanito]

you don't mention which version you're using, but ever since 5.0, just loading the alsa extension is enough for sound to work on both of my machines, I have no further need to issue the "/usr/local/etc/init.d/alsasound start" command.

[paskali]

you don't mention which version you're using, but ever since 5.0, just loading the alsa extension is enough for sound to work on both of my machines, I have no further need to issue the "/usr/local/etc/init.d/alsasound start" command.

Sound volume is too low in my case. I use tiny core 4.7.6

[Juanito]

You could try an upgrade to 5.1?

[paskali]

I have found also this solution that works with alsa in conjunction  with flit, a small applet that shows the time, the day, the power status and the sound status. In bootlocal.sh i append the following commands:

Code: [Select]

while [ ! -e /tmp/wm_errors ]; do
        if [ -e /home/$USER/.flit.pid ]; then
                rm /home/$USER/.flit.pid
        fi     
done
/usr/local/etc/init.d/alsasound start
and in .xsession the followings:

Code: [Select]

if [ ! -e $HOME/.flit.pid ]; then
        while [ ! -e /sys/module/snd_via82xx_modem ]; do
                sleep 0s
        done
fi
flit &
This resolve the alsasound message and an issue of flit that some time does not start. I do not like this solution but it works.

[Juanito]

It might be better to start flit from ~/.X.d