no sound on a fresh install slackware 10...

i have searched the forums for answers and didnt find any for my problem...this is the output of some commands after i tried alsaconf and followed steps in it... i am root when i tried these commands:


# alsamixer
alsamixer: function snd_ctl_open failed for default: No such device

# lsmod | grep snd
snd-pcm-oss 37736 0 (unused)
snd-mixer-oss 12504 2 [snd-pcm-oss]
snd-intel8x0 18924 3
gameport 1420 0 [snd-intel8x0]
snd-mpu401-uart 3200 0 [snd-intel8x0]
snd-rawmidi 12740 0 [snd-mpu401-uart]
snd-seq-device 3888 0 [snd-rawmidi]
snd-pcm 56072 0 [snd-pcm-oss snd-intel8x0]
snd-timer 13604 0 [snd-pcm]
snd-page-alloc 6328 0 [snd-intel8x0 snd-pcm]
snd-ac97-codec 49500 0 [snd-intel8x0]
snd 30852 2 [snd-pcm-oss snd-mixer-oss snd-intel8x0 snd-mpu401-uart snd-rawmidi snd-seq-device snd-pcm snd-timer snd-ac97-codec]
soundcore 3396 4 [snd]

# cat /proc/asound/cards
1 [I82801CAICH3 ]: ICH - Intel 82801CA-ICH3
Intel 82801CA-ICH3 at 0x1c00, irq 10

#


please help.. thanks in advance!

Are you getting any permissions errors? You may need to run

chmod 666 /dev/dsp
chmod 666 /dev/mixer

That may be a red herring but might also be worth checking -- J.W.

nothing happened.. same error..


# chmod 666 /dev/dsp
# chmod 666 /dev/mixer
# alsamixer

alsamixer: function snd_ctl_open failed for default: No such device
#


hmmmmmmmmm

i tried this http://www.alsa-project.org/alsa-doc...odule=intel8x0

still no luck =(

You downloaded and installed all of the files? Strange, I have literally just now done that and it works perfectly - what errors are you now getting?

yes i downloaded all necessary files from the official alsa page... same errors...

Can you post your modules.conf file?

Mine, for example, reads:

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.5 ---
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0

        # ALSA portion
        alias char-major-116 snd
        alias snd-card-0 snd-intel8x0
	# modul
        # OSS/Free portion
        alias char-e options should go here

        # OSS/Free portion
        alias char-major-14 soundcore
        alias sound-slot-0 snd-card-0
	
	# card #1
	alias sound-service-0-0 snd-mixer-oss
	alias sound-service-0-1 snd-seq-oss
	alias sound-service-0-3 snd-pcm-oss
	alias sound-service-0-8 snd-seq-oss
	alias sound-service-0-12 snd-pcm-oss



# --- END: Generated by ALSACONF, do not edit. ---

alias char-major-10-181 toshiba

this is my /etc/modules.conf

# cat /etc/modules.conf
alias /dev/ttySHSF* hsfserial
alias char-major-240 hsfserial
alias /dev/ttyCUA* hsfserial
alias char-major-241 hsfserial
alias /dev/modem hsfserial
options hsfserial serialmajor=240 calloutmajor=241

#options snd-intel8x0 index=0

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.6rc1 ---
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0
# --- END: Generated by ALSACONF, do not edit. ---

#

Here is a suggestion: backup your existing modules.conf file to say modules.conf.backup (so you don't lose it). Then overwrite the Alsaconf section with my Alsaconf section. See if that works. If not, restore your backed up version and you won't have lost anything.

problem solved! i just reboot-ed the pc and turned on again.. logged in as root.. run alsamixer .. everything is ok.. unmuted all and set the desired volume.. phew!

what am i missing? why do i need to reboot? is there a command to reload all alsa related files or devices for me not to reboot?

To be honest, I have not really delved too deeply - either a) it works as soon as it's installed, or b) it works after a reboot.

It's on my (very long) to do list .....

ic.. so i think its better to reboot. when you are trying to install something.... comments please lol =)

Since the sound install affects the kernel (going out on a limb here), I believe we are patching the kernel, a reboot makes sense - normally, we would only need to reboot after either installing new hadware or making amendments to the kernel (update, patch, remove something, etc). Does that sound as though it makes sense?

kewl.. but is there a way to reload the whole linux system as if it had reboot-ed?