Hi all,

I recompiled my (Slackware 10) 2.4.26 kernel to include some support for an ASDL USB modem. After installing it, I no longer had sound, and alsaconf could not find my soundcard.

However, I reinstalled the alsa driver, libs, utills and oss support from the distro cd (v10) and now alsaconf does actually find my card, but on attempting to configure it, I get the following output:

Loading driver...
Loading ALSA kernel modules.
/lib/modules/2.4.26/kernel/sound/acore/snd.o.gz: unresolved symbol unregister_sound_special
/lib/modules/2.4.26/kernel/sound/acore/snd.o.gz: unresolved symbol register_sound_special
/lib/modules/2.4.26/kernel/sound/acore/snd.o.gz: insmod /lib/modules/2.4.26/kernel/sound/acore/snd.o.gz failed
/lib/modules/2.4.26/kernel/sound/acore/snd.o.gz: insmod snd-emu10k1 failed
Setting default volumes...
Saving the mixer setup used for this in /etc/asound.state.
/usr/sbin/alsactl: save_state:1061: No soundcards found...

It would appear that some component is missing. Can anyone advise me as to what it may be?

Many thanks.

When you recompiled the kernel did you give it a new name or anything, like 2.4.26-adsl or something?

When I recompiled my kernel I just went ahead and d/l'd the alsa files from the alsa site and recompiled them.

This might be a dumb question, but did you enable all the sound stuff you needed in the kernel when you recompiled it?

Hi, yes:

I backed everything up, gave the new kernel a new name, and updated all of the symbolic links.

(I did a make modules_install too). Regarding the dumb question, I was so intent on seeking what I needed for the adsl usb modem that I didn't pay any attention to the sound settings - I presumed that if I didn't consciously disable something, it would remain in the kernel build - is that not so?

Either way, It would seem that I will have to go back and rebuild another kernel, paying close attention to what I do.

If I may ask, what kernel options would you recommend then, regarding the sound system?

Thanks

For my sound support I pretty much left everything at the module setting. If you used a pre-existing .config to configure your kernel I bet whatever settings that were there before would still be with you when you rebuilt it.

Hrmm, if the kernel has a new name like lets say 2.4.26-alsa, it shouldn't be looking in /lib/modules/2.4.26/kernel for the modules, it should be looking at /lib/modules/2.4.26-alsa/.
I think it would cause problems if it was loading the modules from the wrong spot.
I forget how that gets set up though.

Your /usr/src/linux should also be pointing to the latest kernel. Like in my example it should point to /usr/src/linux-2.4.26-alsa.

Could the files from the distro cd have been put into the wrong directory?