-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Ray dared to utter,
>> The sound options in 2.4 are all for OSS. If you want to use ALSA you have
>> to leave them out, or at least have them as modules, and then compile
>> alsa-driver yourself with your new kernel.
>
> oh... does this mean that by recompiling my kernel I broke ALSA and have
> to recompile it as well and that's why it's not working?

Most likely, yes.

> would this be a shared library thing or kernel interface or ??? - I'm
> still confused how ALSA actually loads if it's not loaded in any rc
> scripts and not compiled into the kernel.

Because it's a kernel module, just not one included with the kernel
itself. Look at it this way. I make a piece of software (kernel) and
you want to extend it. However, I don't want for whatever reasons to
include your extension in my software, but my software was built with a
plugin (modular) architecture. So, you make a plugin (module) and just
load it directly into my software (kernel).

> (trying to both fix the problem and understand how it all works at the
> same time.)

That is the path to much slack.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFDNF/KzLTO1iU1uO4RAlYPAKCNFw/Ws5xZLuciwjJ9ObkyKNahjACfX3b0
QqdP973Z4w8kie1Fwc/u4/M=
=IIbO
-----END PGP SIGNATURE-----