> I am getting 20+ 'unresolved symbol' errors after installing a custom kernel > and modules under the potato freeze of Debian. Actually, now that I look at > it, I get a lot more than 20, and the majority of them (I loose a lot from > scrolling past the console buffer) are in /lib/modules/2.2.14/misc/. I have > applied two kernel patches (ppDev and ppSCSI), which both worked (after some > tweaking). My HP 5100 scanjet parallel port scanner works very well through > the Gimp now! The only other thing I have done to the kernel is to install > (or try to) the Soundblaster Live module. It does not work. The errors I > get from it are like this: > > Using /lib/modules/2.2.14/misc/sound.o > /lib/modules/2.2.14/misc/sound.o: unresolved symbol > sound_preinit_lowlevel_drivers_Rebdfb792 > /lib/modules/2.2.14/misc/sound.o: unresolved symbol > isa_dma_bridge_buggy_Rf82abc1d > /lib/modules/2.2.14/misc/sound.o: unresolved symbol > sound_unload_lowlevel_drivers_Ra675fda1 > /lib/modules/2.2.14/misc/sound.o: unresolved symbol > sound_init_lowlevel_drivers_Rec0251af
first idea: if you make a modular kernel, you must be consequent, i.e., if you build you soundcard drivers as modules, you have to make soundcore, etc. and everything it depends on as modules, too. alternatively you can pathch the kernel sources and export the symbols by hand, but that requires experience. second idea: the patches were for a newer kernel, which uses other symbol names than yours. in that case you would have to modify the patches. third idea: your modules.conf (or conf.modules) is incorrect. fourth: did you make a 'depmod' after the "make modules modules_install"? (i'm wondering, why modules_install does not do that automatically?)
