Taupter wrote: > Mark Constable wrote: > >> One thing that can happen is that when you compile the modules you >> may have a completely different set of include files onboard that >> do not reflect your current kernel. I have no idea how Mandrake does >> things but you did not mention using any kernel _source_ tarball or >> package so that means you (probably) have the kernel include files >> for the 2.4.18-8.1mdk kernel in /usr/include/linux and /usr/include/asm >> but if they are NOT the right include files for this kernel, you can >> build a set of ALSA modules cleanly but end up not being able to load >> them. > > > Uh... Well, making some symlink magic here... Compiling... Thanks for > remembering me this detail... If I don't complain anymore assume I got > it right. Thanks alot...
Well, I made symlinks in /usr/include : linux -> /usr/src/linux/include/linux asm -> /usr/src/linux/include/asm (that points itself to asm-i386) asm-generic -> /usr/src/linux/include/asm-generic /usr/src/linux poins to /usr/src/linux-2.4.18-8.1mdk removed ALSA related modules from /lib/modules depmod -a ldconfig removed alsa-driver sources unpacked them again, cd alsadriver-0.9.0rc2 ./configure --with-sequencer=yes --with-oss=yes make make install ldconfig depmod -a service alsa start Same problem: Starting ALSA version none:/lib/modules/2.4.18-8.1mdk/kernel/sound/acore/snd.o: unresolved symbol register_sound_special_R69a88294 /lib/modules/2.4.18-8.1mdk/kernel/sound/acore/snd.o: unresolved symbol unregister_sound_special_R99c95fa5 modprobe: insmod /lib/modules/2.4.18-8.1mdk/kernel/sound/acore/snd.o failed modprobe: insmod snd failed Ouch... I still need help. Taupter ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
