No sound after KDE 3.2.1

I downloaded all packages in a dir and then with pkgtool installed them.Now I have no sound with root or any other user.I tried:
1.adduser username sys
2.adduser username audio
3.chmod 666 /dev/dsp* chmod 666 /dev/mixer*
4.chmod 666 /dev/sound/*
And nothing works.But when I start XMMS and click on a song it says that it plays it - but actually no sound comes out.

Thanks in advance

P.S. Here are the messages http://forums.openclub-bg.org/error.jpg

Sound support compiled in your kernel? 'lsmod' to find out.

EXACT same error message and problem I get whenever i upgrade a slack install to kde 3.2.1.

I can see from your screen shot that you have the quicklaunch menu button for KDE configuration. So click that green looking button, go to Sound and Multimedia -> Sound System -> 2nd Tab, and then mess around with the "Select audio device" drop down menu. Right now, my drop down menu is set to "Open Sound System."

Hope this solves the problem.

i'm having the same problem and changing to OSS isn't helping. beforehand it said denied but now that I used chmod 777 /dev/snd it's just not doing anything.. no error message but no sound either...

Are you sure it isn't alsa? After I upgraded with swaret, I didn't have any sound. Turns out the current version of alsa can have problems with Intel onboard sound. I rolled back my alsa to 9.1 (Slack 9.1 that is) and sound is back working and I am using KDE 3.2.

let me try alsa in flux real fast with xmms (it's currently using the oss driver)..

again.. this works in flux just not in KDE.. (actually I guess I didn't say that in this forum.. sorry)

Try to look if it's working under other DE such as GNOME or XFCE or IceWM or whatever else. If yes, it is certainly because KDE has its owns sound server, aRts, which monopolizes your sound card and your programs don't send the sound to aRts. So you must configure them to use the aRts output instead of ALSA or others outputs.
Or perhaps you can just disable aRts at the KDE launch...

Originally posted by Mark Havel Try to look if it's working under other DE such as GNOME or XFCE or IceWM or whatever else. If yes, it is certainly because KDE has its owns sound server, aRts, which monopolizes your sound card and your programs don't send the sound to aRts. So you must configure them to use the aRts output instead of ALSA or others outputs. Or perhaps you can just disable aRts at the KDE launch...

i got the same problem on a latpot, a compaq presario 1005EA, when KDE start the mute button of my pc start to work. and so no software error, but no sound comes out... i have upgraded to kde 3.2 with kernel 2.4.24

any suggestion?

I had the same problem too. Go into Control Center under sound and multimedia. In the mixer subsection uncheck the box next to "load volumes on login". You will have to do this for all users. Run alsamixer and alsactl store and you are good to go.

i have only user root on my machine, i've tried to uncheck that box, of course nothing happened instantly cause the mute button was enabled (and i couldnt disable it because kde was started) then exit from KDE (mute button still enabled) run alsamixer, all was ok, no mute on any channel then quit alsamixer, run alsactl store.. mute button still enabled.. rebooted.. start slackware. and this time there was a news!!! : now the mute button is enabled still on console mode!! before i've to login! incredible... have i done wrong something?

an integration...
i have KDE 3.2 not 3.2.1....

another integration...

the mute button became enabled when those 2 strings are loaded in the boot process :

"Loading ALSA mixer settings : /usr/Sbin/alsactl restore
Loading OSS compatibility modules for ALSA."

uhmmmmm ???!?!?!?!!?

This is very bad an quite unsafe to log in only as root. You should create a normal user you will use in the future.

The messages just means that ALSA is loading the stored settings and the OSS compatibility; OSS is an old sound API like ALSA.

Originally posted by Mark Havel This is very bad an quite unsafe to log in only as root. You should create a normal user you will use in the future. The messages just means that ALSA is loading the stored settings and the OSS compatibility; OSS is an old sound API like ALSA.

why unsafe?? i'm the only one that will use slackware on that laptop...
anyway.. i have another user on that pc... but as i've said.. the mute button become enabled during the boot process. so if login with the other user the mute button remain enabled... i think this is not the point...

i've unchekd the load volume setting at startup in the kde sound panel...
dunno what to do now...

i've unchekd the load volume setting at startup in the kde sound panel... dunno what to do now...

what are the permissions for......../dev/mixer or /dev/mixer0
and /dev/dsp or /dev/dsp0---???