No sound! HELP!!

Kixdemp · 03-11-2006, 09:40 PM

Hello everyone!

Alright... I got sound the first 1 or 2 times I booted into Linux (Fedora Core 4), but then, I started getting this error when booting into Gnome:

Code:

No volume control elements and/or devices found.

I don't have the alsaconf command, but I do have the package installed...

I fixed it once, can't remember how, but it broke again on next login...

Here are the outputs for some 'common" commands:

[root@localhost PeopleDB]# cat /dev/urandom > /dev/dsp

(Didn't hear anything)
[root@localhost PeopleDB]# alsaconf
bash: alsaconf: command not found
[root@localhost PeopleDB]# alsamixer

alsamixer: function snd_ctl_open failed for default: No such device
[root@localhost PeopleDB]# rpm -aq | grep alsa
alsa-lib-devel-1.0.10-3.FC4
alsa-driver-1.0.5a-1
alsa-utils-1.0.10-1.FC4
alsaconf-0.4.3b-3
alsa-lib-1.0.10-3.FC4
[root@localhost PeopleDB]# work-or-i-will-punch-you-in-the-face
bash: work-or-i-will-punch-you-in-the-face: command not found
[root@localhost PeopleDB]#

I don't hear the sample guitar sound in Desktop > System Settings > Soundcard Detection... Anyone have any idea of what the problem can be? The sound card is an ADI SoundMax 1881 (built-in) and my computer is a Compaq Presario 6010US... (Often called Presario 6000) Thanks!

trscookie · 03-12-2006, 09:42 AM

according to the rpm output alsaconf is there have a look in /usr/sbin/alsaconf
and
/usr/bin; /bin; /sbin

whats in?
/etc/modprobe.conf

Kixdemp · 03-12-2006, 09:56 AM

Yeah, I ran that /usr/sbin/alsaconf (Why didn't slocate or locate detect that file though?

), I selected the SoundBlaster_1.0 card and used the default settings, and this is what I got afterwards:

Code:

Loading driver:
/usr/sbin/alsaconf: line 880: start: command not found
Setting the PCM volume to 100% and the Master output volume to 50%
amixer: Mixer attach default error: No such device
Could not initialize the mixer, the card was probably
not detected correctly.

And this is what the modprobe.conf file has:

Code:

alias eth0 forcedeth
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
options snd-intel8x0 index=0
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias usb-controller ohci-hcd
alias scsi_hostadapter sata_nv

What's wrong? Thanks!

trscookie · 03-12-2006, 10:14 AM

(for slocate/locate run: updatedb that should re-write the database) i used to have a problem where sometimes it would detect my sound card and sometimes it wouldnt, what i eventually ran the mixer, without the sound card i.e. run kmix or something then ran alsaconf with the mixer open for some reason this seemed to work for me try that, if it works try running this:

rc-update add alsasound default

if that doesnt work have a look at what modules you kernel has built:

cookie@hal# cd /usr/src/linux
cookie@hal# make menuconfig

then goto

device drivers -> sound -> advanced linux sound arch -> pci devices

and see if the module you need is selected with an M;

Kixdemp · 03-12-2006, 10:36 AM

Hmm... I'm screwed...

With kmix, I don't have any mixers to choose, I don't have the command rc-update, and the directory /usr/src/linux doesn't exist... *Starts screaming* *Makes 2 holes in wall*

What else can I try?

Thanks!

orgelman · 03-12-2006, 12:20 PM

Check /etc/modprob.conf and see if there are empty spaces at the end of some lines, especially the lines ending with the index=0;
if so remove those spaces

Kixdemp · 03-12-2006, 04:10 PM

*Turns music on at full volume*
*Starts dancing*
*Goes outside*
*Screams*

Dude... I found this line in the modprobe.conf file:

Code:

remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0

I removed it, rebooted, and voila!

I'm so happy!

Thanks very much!

trscookie · 03-12-2006, 05:25 PM

glad to hear that, no word of a lie i was actually going to suggest that but didnt undetstand it enough, maybe next time ill just go with gut feeling!

Kixdemp · 03-12-2006, 08:06 PM

Hehe! Yeah!

TypeONegative · 03-13-2006, 04:25 AM

Hey,
I `ve been using Slackware 10.2 since last 6 months. I have got a heavy maching with Intel D915GAV ( 3.0GHz and a gig of ram ). The sound card ( realtec high definition audio ) is built-in the motherboard. The problem is when I run Alsaconf it detects my card and after running alsamixer it shows that the card is detected and even after setting all the volumes to a meaningful limit, I cant hear anything :S What should I do. I also have tried alsactl store.

Regards,
_dm+

Kixdemp · 03-14-2006, 05:15 PM

Hmm... My problem isn't completely fixed either...

I booted, same message again... I saw there was a file "/etc/modprobe.conf~", deleted it, rebooted, happy again. Today, same thing happened, but this time I removed the file "/etc/modprobe.conf.dist", rebooted, happy again. Hmm... Maybe it was just about rebooting? And also, my music and PSX emulator's sound run perfect, but the background music at www.myspace.com is horrible... Is that related, or is it just a problem with the Firefox plugin? Thanks!

BTW, TypeONegative, nice machine you got there!

sixerjman · 03-21-2006, 04:40 PM

at

http://www.alsa-project.org/

alsaconf available here:

http://www.alsa-project.org/alsa/ftp/driver/alsaconf/

Kixdemp · 03-22-2006, 05:41 PM

No, I have those already... But I still get that error everytime I turn on my comp, and I have to restart everytime for it to fix...

Thanks!

sixerjman · 03-24-2006, 06:53 PM

I've had this symptom when I logged into Gnome (on Debian) as non-root, and the volume control wouldn't budge from 0.

The fix was to add the userid to the 'audio' group as follows:

usermod -G audio -a userid

Check the audio device on your system (I think mine is /dev/dsp, and symbolic link /dev/audio) and make sure the
userid has group permissions to the device.

Hope this helps.

sixerjman · 03-24-2006, 07:00 PM

OK, the problem and fix I mentioned don't seem to fit your situation, I just finished reading the entire thread. Sorry. I would guess something (maybe a device file?) is being deleted when the machine is shut down, then
recreated after the initial reboot. Check the Gnome log (.session_errors?)
and also your init and shutdown scripts. I'm away from my Linux box but so
I can't name specific file names but I'll try to get back to this tomorrow.