sound blaster audigy emu10k init_module: No such device
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
sound blaster audigy emu10k init_module: No such device
Anyone got an idea?
#modconf: emu10k
select it and go to install and:
Installing module emu10k1. If the device isn't there, or isn't configured correctly, this could cause your system to pause for up to a minute.
/lib/modules/2.4.21-4-686/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.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.21-4-686/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.21-4-686/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.21-4-686/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1 failed
Installation failed.
Please press ENTER when you are ready to continue.
Distro is debian unstable kernel 2.4.21 but seems to be independent of kernel as I have tried more than one stardard one. I feel as though it might need to be placed somewhere else on the PCI bus? PnP is disabled.
Hi,
When I try <modconf> from the CLI, it only gives me a choice of modules that I have built into the 2.4.21 kernel.
It may be possible that you did not put support for the emu10k1 module into your 2.4.21 kernel.You might look at the config file you used for 2.4.21, and see if CONFIG_SOUND and CONFIG_SOUND_EMU10K1 are being built in, OR are being built as modules.
You seem like a devil-may-care type of guy (much like myself), and I think it is possible that you are trying to use modules from one kernel build with another kernel. I also think that it is possible that I could be wrong.
Hi,
Although both Sound Card Support and CREATIVE SBLIVE! (EMU10k1) are built into my kernel, I see no reason why they should not work as modules. If you build ANY modules while configuring a new kernel, it is important to go and check what you have in </lib/modules>
There should be a directory for each kernel version that you have. There should not be more than one directory labeled <2.4.21>
If I have a working kernel 2.4.21 and I decide to recompile it , I go to /lib/modules and change the name of the existing directory <2.4.21> to <2.4.21.old> before I do the commands <make modules> and <make modules_install> . This renders it useless, but still available if I decide to go back to my first kernel configuration. ( Okay, actually I delete it, but that is because of my carefree nature, and damn-the-torpedos attitude )
When I do a kernel recompile, the <make modules> and <make modules_install> commands will build a new directory in /lib/modules called 2.4.21
This will be the directory I want working with my newly compiled kernel.
well I built it into the kernel, but it is no longer an option in modconf - which makes sense considering modconf should be configuring modules. I thought you said you still had access to it through modconf?
anyway can I assume it now works? and a program I can use to test it?
I did not make clear what I could access through modconf. It is only those things that I built AS modules that I have access to.
If you have not already done so, I would suggest copying the /usr/src/linux/.config file ( if that is your location ) that you used to build your new kernel to a safer location. If you are in the directory this file is in, then <cp .config /boot/config-2.4.20> should do it.
Assuming things has gotten me into more trouble than anything else in my life. I would think that you could test it by trying to play a CD, or an mp3 file.
Give it a shot, and report back any failure or error messages.
What exactly are you trying to get sound from, and what is it telling you in the way of error messages?
Are you doing this from the command line, or using a GUI? I don't think this really matters, except I get lost quick in KDE or Gnome.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.