Soundblaster Live 5.1 not working.

[Nu-Bee]

I am not quite awake yet, maybe that.s my problem. :)

But, I just installed Mdk 9.2 and for the first time I seem to have been bitten with the SBLive 5.1 problem so many people have had.

I just did a modprobe and got this:

[root@localhost joseph]# modprobe -v emu10k1 /sbin/insmod /lib/modules/2.4.22-18mdk/kernel/drivers/sound/sound.o.gz /sbin/insmod /lib/modules/2.4.22-18mdk/kernel/drivers/sound/ac97_codec.o.gz /sbin/insmod /lib/modules/2.4.22-18mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz /lib/modules/2.4.22-18mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg modprobe: insmod /lib/modules/2.4.22-18mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz failed # delete ac97_codec # delete sound modprobe: insmod emu10k1 failed


I have been away from Linux for a few months and have gotten rusty about these things.

Can someone give me a clue about what to do next?

Thanks...

[Satanic Atheist]

I use an SBLive! card and I've never had any problems... except that time when it locked up solid after I unplugged my amp... but that's different.

Not too sure about Mandy, but should those modules be gzipped? On my Slackware machine, their all simply ".o" files.

Can you post back the results of lsmod, please?

James

[Nu-Bee]

Originally posted by Satanic Atheist
I use an SBLive! card and I've never had any problems... except that time when it locked up solid after I unplugged my amp... but that's different.

Not too sure about Mandy, but should those modules be gzipped? On my Slackware machine, their all simply ".o" files.

Can you post back the results of lsmod, please?


Sure...I wish I knew how to do the line breaks right.

[root@localhost joseph]# /sbin/lsmod Module Size Used by Not tainted parport_pc 25544 1 (autoclean) lp 8160 0 (autoclean) parport 34472 1 (autoclean) [parport_pc lp] r128 81556 19 agpgart 53508 3 (autoclean) nls_cp437 5116 1 (autoclean) smbfs 40624 1 (autoclean) snd-seq-midi 5056 0 (autoclean) (unused) snd-emu10k1-synth 5276 0 (autoclean) (unused) snd-emux-synth 31900 0 (autoclean) [snd-emu10k1-synth] snd-seq-midi-emul 6924 0 (autoclean) [snd-emux-synth] snd-seq-virmidi 4588 0 (autoclean) [snd-emux-synth] snd-seq-oss 32000 0 (unused) snd-seq-midi-event 6080 0 [snd-seq-midi snd-seq-virmidi snd-seq-oss] snd-seq 42544 2 [snd-seq-midi snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-oss snd-seq-midi-event] snd-pcm-oss 43652 0 snd-mixer-oss 14200 0 [snd-pcm-oss] snd-emu10k1 70948 0 [snd-emu10k1-synth] snd-pcm 79588 0 [snd-pcm-oss snd-emu10k1] snd-timer 18436 0 [snd-seq snd-pcm] snd-page-alloc 9044 0 [snd-emu10k1 snd-pcm] snd-rawmidi 17760 0 [snd-seq-midi snd-seq-virmidi snd-emu10k1] snd-util-mem 3040 0 [snd-emux-synth snd-emu10k1] snd-seq-device 5832 0 [snd-seq-midi snd-emu10k1-synth snd-emux-synth snd-seq-oss snd-seq snd-emu10k1 snd-rawmidi] snd-hwdep 6304 0 [snd-emu10k1] snd-ac97-codec 45752 0 [snd-emu10k1] snd 41380 0 [snd-seq-midi snd-emux-synth snd-seq-virmidi s nd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-emu10k1 snd- pcm snd-timer snd-rawmidi snd-util-mem snd-seq-device snd-hwdep snd-ac97-codec] soundcore 6340 0 [snd] nfsd 75280 0 (autoclean) af_packet 14856 1 (autoclean) sr_mod 19384 0 (autoclean) floppy 55932 0 8139too 17384 1 (autoclean) mii 3864 0 (autoclean) [8139too] ohci1394 27696 0 (unused) ieee1394 201284 0 [ohci1394] ntfs 77292 1 (autoclean) nls_iso8859-1 3484 4 (autoclean) nls_cp850 4284 2 (autoclean) vfat 11820 2 (autoclean) fat 38040 0 (autoclean) [vfat] supermount 84032 3 (autoclean) ide-cd 33956 0 cdrom 32608 0 [sr_mod ide-cd] ide-scsi 11376 0 scsi_mod 106176 2 [sr_mod ide-scsi] ehci-hcd 19212 0 (unused) usb-uhci 25136 0 (unused) usbcore 74988 1 [ehci-hcd usb-uhci] rtc 9004 0 (autoclean) ext3 60048 5 jbd 39296 5 [ext3]

I also did an:
aumix -q
...and got a "command not found".

Any idea what's missing there, and how to install it?

[RAMWolff]

I had the exact same issue (now I have my share of new ones in MDK 9.2! :D )

I noticed that the driver that was "chosen" for me was called the snd-emu10k1 and then there was another one in the pull down list called emu10k1 and so I chose the one named emu10k1 and all was well after that.

Richard ;)

[Nu-Bee]

Originally posted by RAMWolff
I had the exact same issue (now I have my share of new ones in MDK 9.2! :D )

I noticed that the driver that was "chosen" for me was called the snd-emu10k1 and then there was another one in the pull down list called emu10k1 and so I chose the one named emu10k1 and all was well after that.


Thanks for the reply....yes, I found the same thing here.

FYI; While I was playing, I found that the Audigy driver worked also.

BTW, the emu10k1 is the driver that I have used in every version prior to this. I don't know why 9.2 set me up with the snd-emu10k driver...but it definitely does not work here.

[RAMWolff]

Hope you got it fixed. I know I love my sound too!! :)

Richard ;)

[Luineancaion]

Hey I'm a complete newbie, anyway I'm having problems with my redhat 9 getting my sb live 5.1 to go, I read somewhere that I should turn off plug n play in my bios, which with my bios means putting it to manual and assigning the irq's, I did that a did a fresh install of rh9 but still no sound, is there a specific irq that should be assigned to my sb live? This is really annoying, I'd comletely switch to linux if I could get my sound goin

[bandwidth_pig]

Originally posted by Nu-Bee
Thanks for the reply....yes, I found the same thing here.

FYI; While I was playing, I found that the Audigy driver worked also.

BTW, the emu10k1 is the driver that I have used in every version prior to this. I don't know why 9.2 set me up with the snd-emu10k driver...but it definitely does not work here.

Just a thought, but couldn't you just download the newest kernel sources and compile the emu10k1 driver in? Or load it as a module? Perhaps that is more trouble than it is worth, although I bet it would only take about 15 minutes.

[RAMWolff]

Originally posted by Luineancaion
Hey I'm a complete newbie, anyway I'm having problems with my redhat 9 getting my sb live 5.1 to go, I read somewhere that I should turn off plug n play in my bios, which with my bios means putting it to manual and assigning the irq's, I did that a did a fresh install of rh9 but still no sound, is there a specific irq that should be assigned to my sb live? This is really annoying, I'd completely switch to Linux if I could get my sound going

I would imagine that maybe the same thing is happening to you over on Red Hat as happened to myself and Nu-Bee. Try getting to your hardware configuration and make sure you sign on as root and then check to see if the snd-emu10k driver is loaded up instead of the emu10k driver. You SHOULD have the emu10k driver in there. Also there is a possibility that your sound is muted!! I use one of the mixers to check and if it's muted or turned all the way down then try turning it up and then testing the sound. Those seem to be the two things in the Mandrake platform that give the impression that the audio card was not configured correctly. The mixer I use and recommend is called the Aumixer, you should either have that installed by default or you should have it one of your disks and if not then go and download and install it. It's VERY self explanatory. Usually I just set all the sliders to the 1/2 way mark and then make sure to save the mixers file (you will get a Save dialog and just save it as it is, don't rename it, that way it will look for that configuration each time you boot in and if you change the sliders at any time do a save and it will be there next time you boot in!!).

Hope this gives you some useful information! :)

Richard ;)

[MMYoung]

If you still want to use ALSA (snd-emu10k1), open a terminal window of your choice (I usually use Konsole). Type su (logs you in as root) then the root password.

At the promt type in alsamixer. More than likely you will see several columns that are muted (they will have an MM at the top of them). Select that column and press the m key on your keyboard to unmute that control and press the up arrow key to turn up the volume. Some of the columns won't do anything when you try to increase the volume so I just mute them again, by pressing the m key again, and move to the next column. Do not change the bass or treble levels, leave them at 50%.

After you get all of them set at 100%, except for the bass and treble, press the esc key. Now you should be back at the root prompt. Type in alsactl store to save your new settings.

I don't have a clue as to WHY Mandrake chose to do things this way, or even if it is specific to Mandrake as I had to do the EXACT same thing in Slackware 9.1 to get my sound to work. Be that as it may, that's what I had to do to get my SB Live to work using ALSA.

Hope this helps,
MMYoung