: Hi, i've had to revert back to WinXP cos I cant stand sitting at my PC without sound, so please help me get it back so i can use Linux once more



I'm using Slackware9.1 and have gone through allot of trouble to get it setup (with allot of help), after finally managing to get my USB ADSL Modem (Sagem 800 E2T) working i used the alsaconf command in a konsole to setup my sound card (Audigy2), which worked a charm...a friend of mine then logged in using ssh and tried updateing my kernel to 2.6 (not sure of the exact version number)...it failed tho, when i try and boot using the new kernel it gets stuck as it is loading my cd-rom device (dunno if thats what is causing it though)....anyway, I had to go back to my original kernel and reinstall my modem, but i get an error saying that it cant find my sound card....I think my m8 tried to compile new drivers for them both in order to work with the new kernel....

Is there a way to re-compile my drivers for my sound card? I mean ive tried the alsaconf command again, but now it says it cant find anything :'(

What im thiking i need to do is remove the drivers that are there and use alsaconf again or something, but i aint got a clue what to do....id be on their website but its down atm

Sorry for being a n00b, and thnx for any help

Hi a3Rogue,
the driver you want is the emu10k1. It is very well supported in the kernel. It is probably not loaded though.

It is weird that the only thing your friend did was add a kernel and the old one (which was not touched, right?) stops working correctly. This should not happen.

Since you managed to setup slackware on your own, I will assume you know a few basics. Feel free to ask questions whenever I assumed too much.

First things first. See, if the system recognizes your soundcard: cat /proc/pci | grep EMU10k1. If this command outputs anything, the system recognizes your soundcard and there should be no need to reinstall a driver. Post back, if this is the case.

Here's another thing you can try. This will work, if the driver is present on your system, but is not loaded (this should be done by alsaconf automatically though). Its worth a try: modprobe emu10k1 (open a terminal, become root and issue the command)

If you just want to know, how to compile the driver, here's what option you need to enable in your kernel configuration.
Enable Device Drivers -> Sound -> Advanced Linux Sound Architecture -> PCI devices -> EMU10K1 (SB Live! & Audigy, E-mu APS) and recompile the sucker.
(If you have no clue how to do that (after all, it's the holy grail of linux), speak after me: "Dude, what the f*** are you talking about?" and I will explain how to do it.)

Also, you might want to get your friend to fix what he just broke. ... Ahm, yeah, anyways, just a thought

Good luck with this information. Post back with any more questions,
- drowstar

Thnx for the reply

The thing is, the first time after installing Slackware the alsaconf did work, worked fine, even alsamixer worked and i was happy listening to XMMS

Its only happened after my m8 tried updateing my kernel....which makes me believe its because of what he has done (although he is dead good on linux, but his prefered distro is debian, so maybe he messed something up)...

All i wanna do is be able to use alsaconf again and then maybe I can set it up alright, but atm it cant find my sound card....but it is there :P (alsa and my Audigy)

Would installing alsa again be ok? Even though its already there? I have downloaded the latest version of it, and the instructions...but with me already having it i didnt want to try just incase i make it worse

This is the error i get on boot:-

http://img11.photobucket.com/albums/...ogue/error.jpg

Also, after typing the first thing u mentioned, it didnt say anything, was as if it was a command it knew, but didnt output anything:-

root@darkstar:/# cat /proc/pci | grep EMU10k1
root@darkstar:/# 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: insmod emu10k1 failed
root@darkstar:/#




Should i just install the alsa drivers i downloaded? It shouldnt do any damage should it?


Sorry for being a total n00b :'(

Sorted, Uninstall all the alsa files, then mounted me cdrom, installed the alsa files, then ran alsaconf and it worked


Im happy again, thnx for the help tho drowstar

You're welcome!