On Sun, 5 Feb 2006 14:17:45 -0500 Michael Marsh <[EMAIL PROTECTED]> wrote:
> Did you get alsa-modules-2.4.27-2-386 ? That should have the modules > you're looking for, though you'll need to run depmod before you can > modprobe for them. You can also install alsa-modules-2.4-386 instead > of the more specific version, and that will keep alsa-modules synced > up with your kernel if you have kernel-image-2.4-386 installed as > well. The 2.4-386 version will *always* depend on the specific 2.4 > kernel in the repository, so only install that if you're going to > follow the latest 2.4 kernel. > > Once you've installed the modules package and run depmod, the alsaconf > program from alsa-utils should get everything configured. You might > have to add the appropriate module to /etc/modules, if alsaconf > doesn't do it for you. > > -- > Michael A. Marsh > http://www.umiacs.umd.edu/~mmarsh > http://mamarsh.blogspot.com Did all that and as root, all worked well for a minute. After a reboot, this is what I'm getting: modprobe emu10k1 /lib/modules/2.4.27-2-386/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.27-2-386/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.27-2-386/kernel/drivers/sound/emu10k1/emu10k1.o failed /lib/modules/2.4.27-2-386/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1 failed What did I do wrong and how do I fix? If you need the dmesg, let me know... I hate feeling like an idiot... but I sure do appreciate your help! alsaconf didn't update /etc/modules, but I have no idea what I need to add. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
