Am Fre, 2002-11-08 um 17.43 schrieb Jack O'Quin: > > > > What does /etc/modutils/alsa contain? > > > > [...] > > That looks OK as far as I can see. One thing to watch our for: the > module option names were recently changed in ALSA 0.9rc5. The "snd_"
mine is alsa 0.9rc1 > You said earlier that you are running 2.4.18-k7 kernel with > precompiled alsa-modules (0.9). Does that mean you installed > alsa-modules-2.4.18-k7 from unstable? That version is based on ALSA > 0.9rc1, so your option names (like snd_major) are currently correct. > You may need to watch out for this change in the future, though. well, actually it's testing, but i think that's the same version. > > > snd-cmipci.o is in the appropiate /lib/modules directory > That would be /lib/modules/2.4.18-k7/alsa, right? right. > > > > Does "lsmod" show that any snd* drivers are loaded? > > "lsmod | grep snd" shows the following: > > snd-seq-midi 3232 0 (unused) > > snd-rawmidi 12864 0 [snd-seq-midi] > > snd-seq-midi-event 3096 0 [snd-seq-midi] > > snd-seq 37484 0 [snd-seq-midi snd-seq-midi-event] > > snd-timer 10432 0 [snd-seq] > > snd-seq-device 3904 0 [snd-seq-midi snd-rawmidi snd-seq] > > snd 25704 0 [snd-seq-midi snd-rawmidi > > snd-seq-midi-event snd-seq snd-timer snd-seq-device] > > soundcore 3684 2 [cmpci snd] > > That looks OK as far as it goes, but your snd-cmipci driver is not > getting loaded, for some reason. I believe that causes the error > you're seeing. > > What happens if you run (as root) "modprobe snd-cmipci"? aha! there seems to be some relevant information here, although i don't know what to do with it: "modprobe snd-cmipci" answers "/lib/modules/2.4.18-k7/alsa/snd-cmipci.o: init_module: No such device" dmesg has as last lines "ALSA ../alsa-kernel/pci/cmipci.c:2527: unable to grab ports 0xd800-0xd8ff C-Media PCI soundcard not found or device busy" it seems that on boottime a module "cmpci" is loaded -- could this be the reason why the alsa module can't be loaded?? unfortunately, i have no idea how to unload that module, on "rmmod cmpci" it claims that the device is busy, even if i killed esd. so question really might be: how do i get rid of the other sound module? thanks for any hints, thaden. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
