View Full Version : No sound from Soundblaster Live in FC2
kuestess
27th May 2004, 02:48 PM
I'm having alot of problems getting sound from my Soundblaster Live in FC2. I'm pretty new to Linux, but I think I've got a handle on most of how it works. I've followed the "Fixing FC2 Sound Problems" HOWTO at http://www.fedoraforum.org/forum/showthread.php?s=&threadid=2604 , and also followed the instructions at the ALSA webpage to no avail. My card is properly detected and I was able to get sound under FC1 using the emu-config utility. I've adjusted all of my volumes and un-muted everything in both Kmix and alsamixer, but still can't hear anything. not even the PC speaker works. I've searched through these (and other) forums for help, but nothing seems to work. my modprobe.conf file looks just like the one in the HOWTO, except that it references snd-emu10k1 instead of snd-ens1371.
Anyone have any ideas?
kbradl1
27th May 2004, 03:01 PM
I have a soundblaster Live and had the same problem in FC2. I messed with alsamixer and such; however my soundcard started working after I ran system-config-soundcard and played the test sound. The problem I have now is that it only plays from two speakers when in FC1 it used to play from all 4 speakers.
nibee
27th May 2004, 03:40 PM
I have a SB Live Value, using now FC2 and I have not been able to get it to work. I've followed many instructions but no luck so far. I ran alsaconf, modify my modprobe.conf, unmute everything in alsamixer, but FC2 can only detect the sound card, no sound at all. Here is a copy of my modprobe.conf:
alias eth0 tulip
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.4 ---
alias snd-card-0 snd-emu10k1
alias sound-slot-0 snd-emu10k1
# --- END: Generated by ALSACONF, do not edit. ---
# ALSA
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
#OSS
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
#Card 0
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
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && /usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-emu10k1
install sound-slot-0 /sbin/modprobe --ignore-install sound-slot-0 && { /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-0 { /bin/aumix-minimal -f /etc/.aumixrc -S >>/dev/null 2>&1 || :; }; /sbin/modprobe -r --ignore-remove
alias usb-controller uhci-hcd
dreadmo
27th May 2004, 07:01 PM
I don't have one of these cards, so can't address specifics, but I do know you've got a lot of redundant stuff in modprobe.conf, including command lines for two different mixers. Below I've pasted a minimal version of your modprobe.conf which should still load all the required modules.
alias eth0 tulip
alias usb-controller uhci-hcd
alias snd-card-0 snd-emu10k1
alias sound-slot-0 snd-card-0
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && /usr/sbin/alsactl restore >/dev/null 2>&1 || :
remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-emu10k1
A further tweak you could make to this is to change the 0 in sound-slot-0 to an asterisk:
alias sound-slot-* snd-card-0
The OSS and Card 0 stuff is all in the file modprobe.conf.dist, which is a list of default settings for modprobe.conf. With the minimal version of modprobe.conf above, you should be able to confirm that the OSS modules are still loading by issuing /sbin/lsmod in a terminal (as root). I don't know if alsamixer conflicts with aumix, but it's probably safer to do the volume settings for only one mixer, and since alsamixer is the native ALSA program it should be the one. I moved
the usb-controller line up mainly to make the file easier to read at a glance. Try it and see what happens. You also want to think about pulling the card out, rebooting, removing the soundcard configuration when prompted by kudzu, shutting down, reinstalling the card, booting, and letting kudzu configure the card again. Good luck!
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.