Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 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.
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!
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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.