Problem Saving ALSA Settings

[Rich]

Hi Drew
The first thing I would try is creating an  /etc/libao.conf  file containing:

Code: [Select]

default_driver=alsa

[Drew]

Okay, did that.  Observations:  No change to rdesktop yet, still shows libao as driver, also, libao.conf file goes away after reboot. 

What else can we do?

[gerald_clark]

Well, Core is not a distro per se.  It is a tool kit.
I would try the~/.libao/libao.conf first.
If you wish to contact the extension authors, you do it with a private message, not a forum post, but since libao is compiled in, that will probably be the answer.

[Rich]

Hi Drew
Gerald_clark beat me to it but Tinycore is not a turnkey system so you need to spend some time reading about how it
works.

... also, libao.conf file goes away after reboot.

Case in point, you haven't even learned about how persistence works, which is very important in this distro. I strongly
recommend you take some time to read this:
http://tinycorelinux.net/book.html
It will serve you well.

[gerald_clark]

Note : home should be backed-up when you do a shutdown, so how did /home/tc/.libao/libao.conf disappear?
You did do a backup at shutdown, didn't you?
Did you remove home from .filetool.lst?

[Drew]

First of all, I am NOT a TC expert, obviously.  And I have read the manual on persistence, I have a .pdf copy of it on my desktop that I have referenced many times since the start of this project.

Secondly, I am not as concerned as to what TC is classified as out of the box -- is it a distro or not?  Anyone's guess.  You say it's a tool kit -- perfect, we'll go with that.  But the shear FACT of the matter is, with just a handful of small extensions, it should accomplish what we need it to, just needs to be ironed out a little for our purpose.

Thirdly, this is what .filetool.lst looks like:

opt
home
opt/eth0.sh
opt/alsa
opt/modprobe.conf
usr/lib/alsa/asound.state

Fourthly, backup is performed on each reboot.  Probably won't need to do that every time, but will reduce the frequency of that when we reach a fully working platform that will have no changes made.  That was my understanding of persistence.  If it is wrong, okay.  Then I misunderstood what was well documented in the book, but it wasn't as if it hasn't been consulted.  When I installed TC to a flash drive, the only bootcode I used was nodhcp.  Everything else was default.

[gerald_clark]

Backup is NOT performed on reboot.  Restore is.
Backup is done at shutdown if:
1. You use the gui shutdown and have backup selected.
2. At the command line if you run 'filetool.sh -b" or run "backup".
3. You run "exitcheck.sh".

Please post the output of "showbootcodes".

[curaga]

The libao extension only seems to include the OSS plugin. So it seems a rebuild of libao.tcz is what's needed, please PM that extension's author.

[Drew]

gerald_clark

showbootcodes gives:

initrd=/tce/boot/core/gz quiet nodhcp waitusb=5:UUID="7999f790-92ac-4d8c-8fde-d88dc347281a" tce=UUID="7999f790-92ac-4d8c-8fde-d88dc347281a" BOOT_IMAGE=/tce/boot/vmlinuz

[gerald_clark]

That looks good.

[gerald_clark]

Perhaps you could try OSS instead of alsa.

[Drew]

Interesting you should mention that.  I actually installed a set of ALSA plugins from the list of extensions that were shown to include the oss plugin.  I'm not exactly sure how to make that plugin operative, or that it would even make a difference.

[gerald_clark]

The alsa plugins allow you to run alsa programs on OSS, not the other way around.
I would give OSS a try until such time as libao supports alsa.
Be aware, however, that you cannot load both alsa and OSS.  They will conflict.

[Drew]

I will try that, thanks.  Don't care what or how it works, just need this to work.  Will report back with results.  May need to do some looking to find out how to get OSS working.  Don't know if it's similar to ALSA or not.

[curaga]

Remove all alsa extensions from onboot -> reboot -> install OSS.

That's it, if your sound chip is supported, you will now hear some music when you run osstest.