SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm new to linux and tried installing the emu10k1 driver for my SBLive Value card but have had no luck getting all 4 speakers to work, just 2. I have 2 comps running Slackware and both have SBLives and I can't get all 4 speakers to work on either I've seen quite a few questions regarding this but the ones I found didn't answer my problem.
Here is what I get when I run modprobe emu10k1:
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o: init_module: No such device
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o: 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
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: init_module: No such device
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: 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
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: insmod /lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz failed
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o.gz: insmod emu10k1 failed
Here is the output when I run lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
00:08.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
00:08.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
00:09.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev 11)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06)
00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 18)
00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 18)
00:11.4 USB Controller: VIA Technologies, Inc. USB (rev 18)
01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 200] (rev a3)
It looks to me like you are using the alsa modules for your soundcard. That is what I am doing (I have an audigy with my speakers working.) Try opening up alsamixer in a console window and up the SURROUND volume. see if that helps you out.
I had same problems with the combination alsa/sblive value card. I didn't like the enormous amount (15 !!) modules alsa loads to support my card so I decided to get rid of the alsadrivers.
- I uninstalled the alsa-driver package
- I removed the emu10k1 module from /etc/hotplug/blacklist
- restart (you can unload all the alsa modules by hand if you want to, then rebooting isn't necessary)
The fact your emu10k1 driver can't be loaded is caused by the fact that you loaded the alsa-drivers first. A device can't be used by 2 drivers at the same time.
But will it work for all 4 speakers ? I don't know because my soundcard is connected to the stereo and has no speakers attached.
It seems you still have your old driver, do you?
At least I had those kind of messages while the kernel had compiled support for the old driver.
In this case disable it (N) and select sound as module (M)
It was a little bit fuzzy but I used a good howtos from google.
you disable your sounddriver in the kernel and let sound configured as module
build kernel and modules and install.
then build alsa-driver, afterwards alsa-lib and utils
I downloaded also the alsaplayer and put everything under /opt/alsa. (--prefix=/opt/alsa)
Now I just miss a gtk-mixer
What was important to do is run after installation from the shell following lines - that actually unmuted the alsa-driver
# amixer set Master 100 unmute
# amixer set PCM 100 unmute
# amixer
starting alsamixer didn't unmute
now after this I added some stuff like this below in /etc/modules.conf (Oh, my god, debians conf area! Don't warry it worked!)
I got the output from another program called alsaconf (you find it under $PREFIX/sbin)
If you have devfs (i.e. distros like mandrake and redhat use it as far as I know), then there are different files to modify, consult the docs.
#
## ALSA portion
alias snd-card-0 snd-emu10k1
## If you have more than one, add:
## alias snd-card-1 snd-intel8x0
## alias snd-card-2 snd-ens1370
## OSS/Free portion
## alias sound-slot-0 snd-card-0
## alias sound-slot-1 snd-card-1
##
I think it's better to start experimenting with kernel higher than 2.5 as alsa can be compiled from within the kernel
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.