"[kamstrup]" <[EMAIL PROTECTED]> writes: > http://qa.mandrakesoft.com/show_bug.cgi?id=5488 > > > [EMAIL PROTECTED] changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|RESOLVED |REOPENED > Resolution|FIXED | > > > > > ------- Additional Comments From [EMAIL PROTECTED] 2003-16-09 13:53 ------- > I just ran mcc and tried to change my driver to emu10k1: > > [EMAIL PROTECTED] libDrakX]# mcc > [EMAIL PROTECTED] libDrakX]# sh: line 1: sane-find-scanner: command not found > Doing alsactl to store mixer settings... [ OK ] > Shutting down ALSA sound driver (version 0.9.6): no. (sound is being used by pid > 2201 )) [FAILED] > snd-via82xx: Device or resource busy > Doing alsactl to store mixer settings... [ OK ] > Shutting down ALSA sound driver (version 0.9.6): no. (sound is being used by pid > 2201 )) [FAILED] > snd-emu10k1: Device or resource busy > rmmod: module emu10k1 is not loaded > sh: line 1: sane-find-scanner: command not found > rmmod: module emu10k1 is not loaded > > <SOMEWHERE ABOUT HERE I STOPPED THE MIXER SINCE THIS IS THE ONE BLOCKING THE > DRIVERS - THEN I TRIED TO SELECT emu10k1 AGAIN...> > > rmmod: module emu10k1 is not loaded > ALSA driver (version 0.9.6) is already running. > Doing alsactl to store mixer settings... [ OK ] > Shutting down ALSA sound driver (version 0.9.6): [ OK ] > rmmod: module snd-emu10k1 is not loaded > Loading sound module (snd-emu10k1) [ OK ] > Loading sound module (emu10k1) > /lib/modules/2.4.22-6mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz: 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 > init_module: No such device > modprobe: insmod > /lib/modules/2.4.22-6mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz failed > modprobe: insmod emu10k1 failed > [FAILED] > Loading sound module (emu10k1) > /lib/modules/2.4.22-6mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz: 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 > init_module: No such device > modprobe: insmod > /lib/modules/2.4.22-6mdk/kernel/drivers/sound/emu10k1/emu10k1.o.gz failed > modprobe: insmod emu10k1 failed > > ... > > After a restart emu10k1 now shows up in lsmod as: > > emu10k1 62252 0 > ac97_codec 15668 0 [emu10k1] > sound 70984 0 [emu10k1] > snd-pcm-oss 43428 0 > snd-mixer-oss 14232 1 [snd-pcm-oss] > snd-via82xx 14816 1 > snd-pcm 78692 0 [snd-pcm-oss snd-via82xx] > snd-timer 18276 0 [snd-pcm] > snd-ac97-codec 44824 0 [snd-via82xx] > snd-mpu401-uart 4608 0 [snd-via82xx] > snd-rawmidi 17664 0 [snd-mpu401-uart] > snd-seq-device 5672 0 [snd-rawmidi] > snd 40836 0 [snd-pcm-oss snd-mixer-oss snd-via82xx snd-pcm > snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi snd-seq-device] > soundcore 6308 0 [emu10k1 sound snd] > snd-page-alloc 8948 0 [snd-via82xx snd-pcm] > > This should be fine (reminds a lot of the settings I can get to work manually) > BUT there's no sound. XMMS plays but there's no sound from the sound-blaster - I > HAVE turned everything up in the mixer - both for the sb and the onboard. If I > plug in to the onboard board sound is fine.
argh, we do not nicely handle service faillures :-(
