type in xterm

lspci -v | grep -i audio - this gives you your soundcard

then reinstall aplay as root with the command

tazpkg get-install aplay --forced

then type as user: aplay -l

if evrything is ok until here, then you have a problem with amixer

see this thread: http://forum.slitaz.org/index.php/discussion/1160/problem-with-sound-card-via-vt8237-module-snd_via82xx-duplicate-front-option

Hi Gearhead

Have you tried alsamixer? Go along to the 'speaker' button and hit the "m" button to unmute it. I have to do this on my T61.

Are the headphones working?

Paul

kultex
lspci -v | grep -i audio gives me nothing

Linea
alsamixer won't load mixer attach default error: no file or directory
it is my understanding if it can't load the sound driver alsamixer doen't load.

Thanks for the help so far

CS4237B is an ISA chip so lspci won't return it's ID
alsamixer won't open without sound device installed
See this: http://alsa.opensrc.org/index.php/ThinkPad600
Check your bios to make sure that you have "QuickBoot = OFF"

root@slitaz: modprobe snd-cs4236 port=0x530 cport=0x538 irq=5 dma1=1 dma2=0

You may have to try some different settings,after you get it working make a text file/script called snd-cs4236.sh that's executable with the correct modprobe command from above. Place it in /usr/sbin , add snd-cs4236.sh to RUN_SCRIPTS=
of /etc/rcS.conf

Thanks mojo, I have sound now but 2 problems.
1. When I reboot...no sound. From a reboot I have to go into the bios and click the "QuickBoot" off again, even after I initalize it. I've read where you ad something to the grub/menu file. But that was with other systems and it would be nice to have a example instead of "just add it to the file".
2. I only have sound in root, not tux.
Thanks again

Problem 1. Could be symptom of a dead bios backup battery, bios settings you change will not save and revert to default which includes Quickboot=on
Configuration data lost: http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=migr-4yqmn7

Try this to autoload :

root@slitaz: nano /etc/init.d/local.sh

Add: modprobe snd-cs4236 port=0x530 cport=0x538 irq=5 dma1=1 dma2=0
Closeout/save with keystrokes:
Ctrl+x
Y
Enter

Problem 2.
Check group permissions of sound devices:

root@slitaz: ls -la -e /dev/snd -e /dev/mixer -e /dev/dsp

crw-rw-r-- 1 root scanner 14, 3 Sun Jan 3 02:09:25 2010 /dev/dsp
crw-rw-r-- 1 root scanner 14, 0 Sat Feb 6 00:22:40 2010 /dev/mixer

/dev/snd:
drwxr-xr-x 2 root root 4096 Sat Sep 25 11:16:27 2010 ./
drwxr-xr-x 13 root root 12288 Wed Oct 27 10:48:52 2010 ../
crw-rw-r-- 1 root scanner 116, 0 Mon Jan 4 14:10:32 2010 controlC0
crw-rw-r-- 1 root scanner 116, 4 Sat Sep 25 11:16:27 2010 hwC0D0
crw-rw-r-- 1 root scanner 116, 8 Sat Sep 25 11:16:27 2010 midiC0D0
crw-rw-r-- 1 root scanner 116, 24 Mon Jan 4 14:10:32 2010 pcmC0D0c
crw-rw-r-- 1 root scanner 116, 16 Wed Oct 27 12:09:29 2010 pcmC0D0p
crw-rw-r-- 1 root scanner 116, 17 Mon Jan 4 14:10:32 2010 pcmC0D1p
crw-rw-r-- 1 root scanner 116, 18 Mon Jan 4 14:10:32 2010 pcmC0D2p
crw-rw-r-- 1 root scanner 116, 27 Mon Jan 4 14:10:28 2010 pcmC0D3c
crw-rw-r-- 1 root scanner 116, 33 Mon Jan 4 14:10:27 2010 timer

On my system a member of scanner group can access sound devices.

Verify tux is a member of the group that has permission to access sound devices:

 tux@xubuntu:~$ cat /etc/group    
root:x:0:
lp:x:10:tux
audio:x:20:tux
nogroup:x:99:
www:x:80:
messagebus:x:25:tux
haldaemon:x:26:tux
tux:x:1000:
scanner:x:96:tux
camera:x:97:tux

tux is member of scanner group so he can use sound devices on my system.

On a clean install the audio group has permission to access sound devices.

Thanks for the responce mojo
As for the battery I have not had codes yet,but i'll order a new one there not very expensive.
Here is the output from the 2 commands, as I read it tux should have sound permission...but it doesn't, no mixer, nothing.
root@slitaz:~# ls -la -e /dev/snd -e /dev/mixer -e /dev/dsp
ls: /dev/mixer: No such file or directory
crw-rw-rw- 1 root root 14, 3 Wed May 26 11:01:33 2010 /dev/dsp

/dev/snd:
drwxr-xr-x 2 root root 4096 Wed Oct 27 09:52:26 2010 .
drwxr-xr-x 13 root root 4096 Wed Oct 27 15:41:30 2010 ..
crw-rw-r-- 1 root audio 116, 0 Wed Oct 27 15:41:31 2010 controlC0
crw-rw-r-- 1 root audio 116, 4 Wed Oct 27 15:41:31 2010 hwC0D0
crw-rw-r-- 1 root audio 116, 24 Wed Oct 27 15:41:31 2010 pcmC0D0c
crw-rw-r-- 1 root audio 116, 16 Wed Oct 27 15:41:31 2010 pcmC0D0p
crw-rw-r-- 1 root audio 116, 1 Tue Oct 26 22:22:22 2010 seq
crw-rw-r-- 1 root audio 116, 33 Wed Oct 27 15:41:32 2010 timer
root@slitaz:~# cat /etc/group
root:x:0:
lp:x:10:
audio:x:20:tux:
nogroup:x:99:
www:x:80:
messagebus:x:25:
cdrom:x:1:
dialout:x:2:
disk:x:3:
floppy:x:4:
kmem:x:5:
tape:x:6:
tty:x:7:
video:x:8:
haldaemon:x:26:
tux:x:1000:
root@slitaz:~#

Correction I rebooted and ran this command again and got this...I don't know why but still no sound in tux.
The group file is the same as above.


root@slitaz:~# ls -la -e /dev/snd -e /dev/mixer -e /dev/dsp
crw-rw-r-- 1 root audio 14, 3 Wed Oct 27 20:57:58 2010 /dev/dsp
crw-rw-r-- 1 root audio 14, 0 Wed Oct 27 20:57:58 2010 /dev/mixer

/dev/snd:
drwxr-xr-x 2 root root 4096 Wed Oct 27 09:52:26 2010 .
drwxr-xr-x 13 root root 4096 Wed Oct 27 22:41:20 2010 ..
crw-rw-r-- 1 root audio 116, 0 Wed Oct 27 22:41:18 2010 controlC0
crw-rw-r-- 1 root audio 116, 4 Wed Oct 27 22:41:18 2010 hwC0D0
crw-rw-r-- 1 root audio 116, 24 Wed Oct 27 22:41:18 2010 pcmC0D0c
crw-rw-r-- 1 root audio 116, 16 Wed Oct 27 23:02:57 2010 pcmC0D0p
crw-rw-r-- 1 root audio 116, 1 Tue Oct 26 22:22:22 2010 seq
crw-rw-r-- 1 root audio 116, 33 Wed Oct 27 22:41:19 2010 timer

Install aplay:

root@slitaz: tazpkg get-install alsa-utils

See this : http://alsa.opensrc.org/index.php/TroubleShooting
Try playing sound: Verify aplay produces sound as user root
then login as user tux:

 tux@slitaz: aplay -vv /path/to/file.wav

Post any errors,or does player run but you hear no sound ?
Post output from

 tux@slitaz: aplay -L

Thanks for all your help mojo, but in the end the I ended up having to download and burn another iso. Turns out the one I was using was corrupt. Talk about pulling your hair out.
Sound works fine for all users with Quick boot off and the modprobe installed in locale.sh