Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: alanl on September 19, 2009, 10:47:26 PM
-
I run alsamixer and set it up. I run alsactl store. asound.state shows
up in /etc. I add etc/asound.state to /opt/filetool.list. When I boot up
alsamixer is set to off. The asound.state file is in /etc.
-
It works fine here.
But I see the same behavior when I do not run "/usr/local/etc/init.d/alsasound start" after rebooting. Running that would most likely result in restored volume settings.
-
I have that in /opt/bootlocal.sh.
-
Try removing it or commenting it out of bootlocal.sh and waiting until the desktop is up and see if running it then will help. I one time had an issue like that on one of my machines.
-
I commented it out and on reboot went to /usr/locat/etc/init.d
and ran alsasound start.
bin/sh: alsasound: not found! Alsasound was starting before.
It worked fine with tc-143. Now with tc-2.2 - problems.
-
Do you have the latest version of the alsa extension(s) - I believe they were updated several times?
-
Also, if in the /usr/local/etc/init.d directory use the command "./alsasound start". Or use the full path "/usr/local/etc/init.d/alsasound start".
-
Now I ran it with the full path and it worked.
Checked alsamixer and it was set up correctly.
So what`s happening? Is alsasound getting setup
before asound.state is added to /etc?
I`m going to re-install the alsa tces.
-
I have that in /opt/bootlocal.sh.
You can try add
sleep 4
alsactl restore
to your /opt/bootlocal.sh
-
I use the tcz version of alsa and it is loaded automatically, only
alsactl restore
in bootlocal
-
Wow. Same person. Sorry to trouble you yet again. I really am working hard at this.
I have gotten alsa to support my mic. Testing with arecord and aplay works fine.
However, alsasound start will not automatically configure my mic correctly; hence I need to configure manually and then save and restore.
I am having trouble saving and restoring the configuration.
I thought from reading this thread that what I need to do is:
Save/restore asound.state via filetool.list
Run alsactl restore or /usr/local/etc/init.d/alsasound start via bootlocal.sh at re-boot.
Problems:
I could not find a file: /etc/asound.state as described. I tried saving with filetool.list anyway but no joy. Perhaps the alsa config file is someplace else. I poked around but could not find it.
Probably because of the asound.state problem, alsactl restore fails. alsasound start brings up alsa but without my configuration.
Can you advise me?
Thanks yet again.
As soon as I get this working I can try out the skype module.
sci_fi
-
a: You need to run alsamixer and set it up as you want.
Then run alsactl store and the file...asound.state
will appear in /etc.
b: I tried all the suggestions and no luck. I added alsactl restore
to /opt/bootlocal.sh. No workee. Then I added sleep 4 and
now it works! Thanks to all for your help.
-
alan, jls,
Thank you so much for your assistance. I have alsa (really needed that sleep 4 as you suggested) and the skype version you provided working now. Initial skype testing seems OK. Possibly some voice quality issues on my transmission. I probably need to play with the alsa mic settings some more, but at least it works. Incoming voice quality is fine.
Thanks hugely, once again.
Now, I am free to go obsess about something else.
Best regards,
sci_fi
-
I don't have any alsasound start in my bootlocal, but alsa works
-
Yes, I have alsactl restore in bootlocal.sh. Not alsasound start. Works fine.
-
<bump>
Ran into this same problem of alsa not starting up. In bootlocal.sh I rmmod and modprobe the sound chip to get the sample speed right and then run the alsasound start script. This generally works fine but when I ran TCL 2.5 with a very small set of extensions the sound didn't start. Adding sleep 4 to bootlocal.sh prior to the sound commands seems to resolve this. Some strange timing issue maybe? It started happening after I upgraded the extensions to the new squashfs [sp?] format where TCL boots faster than it used to.
-
I have seen the same behavior, were adding "/usr/locla/etc/init.d/alsasound start" did not work, but running the command just after booting to the desktop does work. As you have stated, adding a sleep command in bootlocal.sh may be needed in some cases as it evidently is a timing issue. I will add that to the info file as it is a common situation.
-
Dam, booted this morning and alsa didn't start even with sleep 4 in bootlocal.sh.
edit: rebooted and alsa started [???].
Further fiddling after I get home from work.
edit: sleep 6 seems to work, but I'll see.
edit: as of 11/21 sleep 6 works OK.