Re: Fwd: Re: [Alsa-user] modules insertion miserably failing

[Nicolas V. <nv...@ne...>]

mis...@gm... wrote:

> On Tue, 22 Jun 2004 21:38:53 +0200
> dp <dad...@ya...> wrote:
> 
> 
>>Well, I closed all apps using sound. I killed artsd. I disabled the sound in
>>KDE. I went to the kernel (with Linux Kernel KDE utility) and I turned off
>>all sound support, every single module. Then I "make bzImage" in the
>>reconfigured kernel source, and rebooted the system. Now I receive msgs from
>>KDE saying that it can't find sound device and will redirect to null ecc...
>>No sound is working, no sound device can be found by any app. And this is
>>good.
>>Less good is:
>>
>>debian:~# modprobe -r sound
>>sound: Device or resource busy
>>
>>Why??? I turned off all sound modules in the kernel! The shell should answer
>>"no module found" or something similar, not "busy"! Anyway, that was the same
>>answer i received while sound was working! (10 minutes ago)

No, definitively no ! Keep in mind the autoload kernel process !
When you try to access a device or a module, kernel try to load the 
corresponding dependencies before you access it.

you wanna remove a module in the sound tree, then sound module depends 
on soundcore, and at soundcore load, kernel will load devices and so 
on... this is defined in /etc/modules.conf in 2.4.x

This is normal, "sound" is the second module, soundcore the base one. it 
can't remove unless all modules using it are all removed... and not only 
emu10k1, oss ones too, and midi/synth too. Some depends on soundcore and 
sound and so will only remove only when explicitely asked to.

so that modprobe -r sound .... loads it if it was not. and as your 
system config is broken, it fails to unload.

Please send lsmod before, lsmod after,
your /etc/modules.conf is the only way to see what's wrong

to test, temporary remove all your oss modules from /lib/...

>>And same answer when i command:
>>
>>modprobe snd-emu10k1
>>
>>/lib/modules/2.4.25-1-386/alsa/snd-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.25-1-386/alsa/snd-emu10k1.o:
>>insmod /lib/modules/2.4.25-1-386/alsa/snd-emu10k1.o failed
>>/lib/modules/2.4.25-1-386/alsa/snd-emu10k1.o: insmod snd-emu10k1 failed
>>debian:~# modprobe snd-emu10k1
>>/lib/modules/2.4.25-1-386/alsa/snd-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.25-1-386/alsa/snd-emu10k1.o:
>>insmod /lib/modules/2.4.25-1-386/alsa/snd-emu10k1.o failed
>>/lib/modules/2.4.25-1-386/alsa/snd-emu10k1.o: insmod snd-emu10k1 failed
>>debian:~# modprobe -r sound
>>
>>Nothing new. It seems i just turned off all kind of sounds, without changing
>>the situation.

I wrote an unsend paper about this. This is normal.

In fast, all you can read about emu10k and Alsa is totaly wrong.
The module tree for emu10k1 was not created for such a use, but hacked 
to get audio only for those not needing a emu10k1 board but have one!!!

snd-emu10k1 only works fine in synth mode, (the only module correctly 
loading alsa is snd-emu10k1-synth).

If everybody experiment problems with them, this is because nothing is 
really working the way it's explain. There is no way to fully install 
ALSA correctly for emu10k.

First, the module to load is NOT emu10k1 AT ALL this is WRONG.
The module to load is .... snd-emu10k1-synth.
the snd-emu10k1 is Alsa audio part of emu10k1 boards, and so only loads 
audio (no mixer, no synth, no seq, no ....)

this fixes about 99.95% of the loading problems.

Still one, this is Alsa autoload4 and ossemul and devfs... totaly broken
and unsupported...

This was working when a snd-mixer module was present.

N.VIGNOT