The Testing Area :: alsa.dsl for 2.0



http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?;act=ST;f=6;t=3056
Quote (Phinger @ Dec. 13 2005,15:37)
I have a HDD install, with the gnu-utils already present. I got this package for the 2.0 dsl, right click....run the alsa script.......nothing. Is there supposed to be a menu to select chipsets or something? The thing just looks like a command line............runs by real fast and then dissapears without asking me anything.

in mvv's post above yours he said he 'added the "alsa" boot parameter to the "append=..." section in [his] lilo.conf' for his harddrive install.  Can you try the same thing?  You are correct: there should be a menu that comes up (after autodetecting your card) that lets you choose which card you want.  The script that the menu runs can be found in /opt/alsa/

After having it work the other day I got nothing now!  I've retried alsaconf without any success.  What have I done?

lilo.conf still has the alsa parameter.
The audio section of the slit is still there so something is loaded.
After running alsaconf for the 10th time, I still have no sound.

TIA
-Mark

I've reinstalled my DSL 2.0 using the Frugal install this time and had the same experience.  I made sure to use the menu items for GNU Utils and ALSA Setup.  It all looked and sounded good until I did a reboot and then I had nothing.  
Re-running the alsaconf produced a pile of errors and didn't help.  I looked in modules.conf and there's no mention of my audio configs.  I expected to see something there.
Not sure why but the audio controls never did show in the slit at any point in this install.

-Mark

After you did the Alsa setup, did you do back up? I'm not using alsa because I was able to get sound working using a short line in the bootlocal.sh script. Maybe there is a script for the alsa setup that needs to be referenced in bootlocal.sh, or filetool.lst in order to call the parameters for your alsa setup.
For example, iwconfig writes a script for it's parameters that is placed in /opt, but you need to place a line in bootlocal.sh to call that script at bootup, or your settings will not be reloaded.

Next Page...
original here.