Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: aus9 on October 22, 2010, 04:57:19 AM

Title: [SOLVED] alsaconf (package alsa)
Post by: aus9 on October 22, 2010, 04:57:19 AM: hi

rather than private message I thought I would post a low priority information on the command

sudo alsaconf

I have deliberately deleted /etc/modprobe.conf

but when I run that alsaconf I always get a dialog that asks if I want to edit
/etc/modprobe.conf

2) so let it go ....and let it complete the full process and then redo alsaconf

this time I am kept /etc/modprobe.conf

but when the scripts says edit and I select YES it does not start vi or any other editor to allow me to edit.

submitted for you information
Title: Re: low priority alsaconf (package alsa) possible gremlin
Post by: Jason W on October 22, 2010, 05:11:04 AM: Actually it is medium priority since it has nothing to do with deleting modprobe.conf. This happens during normal operation, so I will peek in and try to fix.

EDIT: Umm, I ran alsaconf and I remembered that "Do you want to modify.." means to you want alsaconf to modify modprobe.conf with what it found, not do you want to open it in an editor.

But thanks for reporting.
Title: Re: [SUBJECT CHANGED] alsaconf (package alsa) part 2
Post by: aus9 on October 22, 2010, 07:49:59 PM: hi

rather than create a new subject as I am still testing alsaconf here is part 2.

I have read the script alsaconf.....I am not a programmer but when you run sudo alsaconf

IMHO ....if it detects your device it is supposed to play a sound....but not for me

I refer to line 826

-- it seems we need to run
Code: [Select]
cat /usr/share/doc/tc/release.txt
while most "turnkey" distros tend to have a file in /etc?

I am attempting to expand the sound wiki

http://wiki.tinycorelinux.com/Setting+up+Sound but I have not been able to show the full beautiful effects of alsaconf

thanks by the way for the work already done....I am just reporting my selfish needs in case it helps others....heh heh

b) maybe a programmer might find the fault?

maybe its to do with the distro release....we might need to tweak so it knows what to do with tinycore?

c) also I wonder about /opt/alsa

I think something is missing?

opt/alsa is in my .filetool.lst

Code: [Select]
ls -al /opt/alsa/ total 12 drwxrwsr-x 2 root staff 4096 Oct 22 23:28 ./ drwxrwsr-x 4 root staff 4096 Oct 22 23:28 ../ -rw-rw-r-- 1 root staff 2 Oct 22 23:38 .alsaconf -rw-rw-r-- 1 root staff 0 Oct 22 08:38 .alsadriver sudo su cat .alsaconf 1 root@box:/opt/alsa# cat .alsadriver root@box:/opt/alsa# (indicates its empty)
Title: Re: [SUBJECT CHANGED] alsaconf (package alsa) part 2
Post by: Jason W on October 22, 2010, 08:13:12 PM: Actually, your /opt/alsa has all the info it needs for a typical PCI setup. I use a directory in case other need files are later used to keep the entry in /opt/.filetool.lst to one line. The .alsadriver file would have data in case of an ISA PnP setup.

To make alsaconf play a sound, try this command before running it:

cd /usr/local/share/sounds/alsa
cp Side_Right.wav test.wav

That should make a sound when supposed to. I will look for the test.wav since it did not seem to be part of the normal install. If it is very small, I will add it in.
Title: Re: [SUBJECT CHANGED] alsaconf (package alsa) part 2
Post by: aus9 on October 22, 2010, 08:36:55 PM: hi

thats re-assuring on the /opt/alsa issue

FYI a debian sid distro has the same sound files as per your list for alsa and NO test.wav

http://distro.ibiblio.org/pub/linux/distributions/tinycorelinux/3.x/tcz/alsa.tcz.list

versus my

Code: [Select]
root@sid:/home/gordy# find / -name test.wav root@sid:/home/gordy#
looks like a gremlin from the Debian maintainers?

but it does exist on a rpm distro

http://fr2.rpmfind.net/linux/RPM/opensuse/11.3/i586/alsa-1.0.23-2.12.i586.html

section files refers

downloading the alsa package now to have a peek
Title: Re: [SUBJECT CHANGED] alsaconf (package alsa) part 2
Post by: Jason W on October 22, 2010, 08:41:22 PM: Yeah, I also saw it was not in the Debian package but in Suse's. I guess it is made to be either custom or distro specific. I don't remember any distros play a test.wav where alsaconf is directly used, but I am not against the inclusion of one.
Title: Re: [SUBJECT CHANGED] alsaconf (package alsa) part 2
Post by: aus9 on October 22, 2010, 09:04:06 PM: well bu$$er me I dowloaded numerous editons of

http://alsa.mirror.fr/utils/

which contain the other wav files and I gave up.

the folder speaker-test/samples does not appear to have test.wav

maybe the maintainer was not as alert as us tinycorers?

consider this closed thanks
Title: Re: [SOLVED] alsaconf (package alsa)
Post by: tinypoodle on October 22, 2010, 11:19:36 PM: What about just symlinking one of the included .wav files to test.wav.
Either by including a symlink, or by creating it with the install script.

I remember in Puppy the sound produced by alsaconf being distro specific.
Title: Re: [SOLVED] alsaconf (package alsa)
Post by: tinypoodle on December 20, 2010, 03:19:19 PM: Quote from: Jason W on October 22, 2010, 08:13:12 PM
To make alsaconf play a sound, try this command before running it:

cd /usr/local/share/sounds/alsa
cp Side_Right.wav test.wav

That should make a sound when supposed to. I will look for the test.wav since it did not seem to be part of the normal install. If it is very small, I will add it in.

Umm... 'alsaconf --help' (DUH) amongst other reveals:
Code: [Select]
-s|--sound wav-file use the specified wav file as a test sound
:P