After migrating to Kernel 2.6 my sound-module is not automatically started
Hi!
I just got 2.6.4 set up so far, everthing seems to be working pretty good, but I don't know how to set up the module loading... (same goes for my network card, but I compiled it in to the kernel for now). In it I think the important stuff is in: /etc/modules.conf options snd-emu10k1 enable=1 index=0 options snd cards_limit=1 major=116 alias snd-card-0 snd-emu10k1 alias sound-slot-0 snd-emu10k1 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-11 snd-mixer-oss alias sound-service-0-12 snd-pcm-oss what do i need to automatically load the emu10k1 module for my soundblaster? After modprobe emu10k1 it works. Im running suse 9.0, alsa 1.0.3 and modutils 0.9.15-pre4 Btw: What is the difference between module-init-tools-0.9.15-pre4 and module-init-tools-3.0-pre10 ? I got a little confused about the version numbers (0.9 vs 3). Thanks in advance:-) |
I ran into this, but you do need the module-init tools installed, untar and configure. The reason my sound (same sound card) was not working was my ALSA was out of date, so I upgraded it. You could try compiling the sound into the kernel rather than as a module.
Also 2.6.x uses modprobe.conf, not modules.conf when you install module-init-tools, there is a shell script for generate-modprobe.conf, did you miss this step out by any chance? From the README in the tarball... ______________ 3) If running for the first time, you might want to convert your old modules.conf to modprobe.conf: ./generate-modprobe.conf /etc/modprobe.conf ______________ hope this helps |
Thank you very much! Now it works! I did forget the generate-modprobe.conf...
Frederik |
All times are GMT -5. The time now is 09:21 AM. |