soundblaster audigy and the newbie
 

i've read through a few threads here, and i'm just not following clearly.

i need to get my soundblaster audigy working, and have no idea where to start.

i have downloaded the emu10k1 driver, but have no idea what to do with it.

any help with this advanced windows user turned pre-school linux user would be greatly appreciated

thanks in advance

http://sourceforge.net/docman/displa...group_id=44773

Hopefully those instructions help! If not, post back.

well, when i do those steps, and i type make, it tells me that i shoulc copy the correct .config file into my linux-2.4 directory. and it tells me where to find it. the problem is there are about 15 .config files in there. which one do i copy?

[root@bluedoom emu10k1]# make
make -Cscripts
make[1]: Entering directory `/root/emu10k1/scripts'
cc -I/usr/src/linux-2.4/include get_version.c -o get_version
make -f /root/emu10k1/scripts/Makefile.get_options -C /usr/src/linux-2.4 get_version_target
make[2]: Entering directory `/usr/src/linux-2.4.18-3'
**
** /usr/src/linux-2.4/.config is missing
** if this is a custom kernel then you need to run make config in /usr/src/linux-2.4.
** if this is a distribution kernel then you need to copy the correct .config file to /usr/src/linux-2.4.
** for RedHat kernels the .config file is one of the /usr/src/linux-2.4/configs/*.config
**
make[2]: *** [get_version_target] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.18-3'
make[1]: *** [get_options] Error 2
make[1]: Leaving directory `/root/emu10k1/scripts'
make: *** [opts] Error 2


that's what i'm getting..............

post the output of
uname -a

In Redhat, they have a lot of .config files in /usr/src/linux/configs. You'll have to find the one that matches your processor and copy that to the /usr/src/linux. EX: "cp /usr/src/linux/configs/******.config /usr/src/linux/.config That worked for me in 7.3. After that, you should be able to compile no problem.

[root@bluedoom emu10k1]# uname -a
Linux bluedoom 2.4.18-3 #1 Thu Apr 18 07:32:41 EDT 2002 i686 unknown
[root@bluedoom emu10k1]#



i'll try that copy that you suggested, darkmage

okay, copying and renaming the .config with my processor name in it and renaming it just .config, worked.

now, new problem, when i try make install, i get one error. i have no idea what the error is..........

this is what i get...........

**
** The driver was succefully compiled, now install it with:
** make install
**
mkdir -p //lib/modules/2.4.18-3/kernel/drivers/sound/emu10k1
install -c -m 664 emu10k1.o //lib/modules/2.4.18-3/kernel/drivers/sound/emu10k1
install -c -m 664 ac97_codec.o //lib/modules/2.4.18-3/kernel/drivers/sound
/sbin/depmod -as 2.4.18-3
make: *** [install] Error 1

???

That is weird. I'll try to look for an answer. Anyone setup an Audigy in Redhat before that's seen this error???

I don't know if it will make a difference or not but are you compiling as root? If not, you may want to try. You never know!

yes, i am.........; )

You may need to update your kernel to at least 2.4.18-6, someone please tell me if I'm wrong.

well, i updated to the latest on the redhat site, 2.4.18-5, and still no luck

okay, i solved that problem, i get no errors throughout the entire install process, until i check it. i get this:

[root@bluedoom sbin]# modprobe emu10k1
/lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1 failed
[root@bluedoom sbin]#

problem solved

Awesome!!

How did you get it to work???
 

I'm having the exact problem.. Running 2.4.18-10 & errors out when doing make install for the Audigy drivers.

Silly Audigy 2...
 

I just loaded suse linux and have numerous problems. the first is that my new audigy 2 won't init. this causes linux not to load the audio mixer. does anyone know of a new audigy 2 driver or a generic SB driver i can use to get the baic sound functions running? if so please give me detailed instructions, still new.

-Herman

how did you solve the:
" /lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.18-5/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1 failed
"
problem? i've got exactly the same answer for modprobe

I'm having different problems with my Audigy. I'm running RH9 and recently "upgraded" my Kernel to 2.4.20-18.9. The previous version was 2.4.20-8. Sound didn't work in the previous version either, but since it was a newish install I didn't mess with sound in it and went to the newer update.

Per the instructions on the ALSA web site, everything seems to go fine up to the modprobe portion. When I do that step, I get errors along the lines of: "/lib/modules/2.4.20-18.9/kernel/sound/acore/snd.o: kernel-module version mismatch .... etc. Essentially continues on to say that snd.o was compiled for the previous kernel version I was running.

I'm sure this is an easy "fix" and hopefully this is my only hurdle for this newbie to get sound working!

thats weird i run rh8 and it picks up the audigy no problems..and it works fine.
kernel 2.4.18-14

Well in my quest to be able to play music I remembered my mobo had built in sound that I disabled in the BIOS when I bought my Audigy way back when. So I enabled that and now I have sound most of the time. I'm dual booting into windows or sometimes I just shut my system down while I'm away for the day and when I reboot back into Linux, sound isn't there (no errors display at boot though.) Sometimes I have to reboot 2-3 times before sound will work again. I have not physically removed the Audigy from the system yet and really don't plan to or want to.

Any thoughts on this? As far as getting the Audigy to work, might I have better luck patching the drivers into the kernel and recompiling? Should I try the newer kernel released in recent days?