I have a slight variation on the whole "I can't get ALSA to work under 2.6.0 with the built-in drivers".
I've attempted about a half-dozen kernel 2.6.0 recompiles in order to get ALSA to work under 2.6.0. No dice. I even tried installing the ALSA 1.0.0rc2 drivers and libs afterwards. Again, no dice. The thing is driving me a little batty.
I've noticed a couple of things...
1) When dropline-gnome installed ALSA 0.9.8 under the 2.4.22 kernel, sound stopped working. I uninstalled 0.9.8 and reinstalled the 0.9.6 version that came with my Slack disks and the world was again a pleasant place to be
2) If I do compile ALSA support into the 2.6.0 kernel, when I boot I am told that the version is 0.9.7. Of course, no sound. In fact, it doesn't even detect my audio card.
3) I know ALSA does work, because I have version 0.9.6 (the one that comes with Slack 9.1) working under the 2.4.22 kernel I have installed on the same machine.
To my question: If I were to configure the .config file to build sound support into the kernel (the top level option under Sound), but not choose to build either ALSA or OSS into the kernel or as modules, and then after building and installing the new kernel, then actually build and install the drivers, libs, tools, etc. that come with ALSA 1.0.0rc2, theoretically, should that work?
I noticed on the ALSA site that if "soundcore" isn't loaded (via "modprobe soundcore") before attempting to install the ALSA packages, then you are instructed to go back and compile it into the kernel.
What do you all think?