Here is what I did: 1. Untarred the kernel source (2.2.14) 2. Applied ppDev patch (for 2.2.14) 3. Applied ppSCSI patch (not for 2.2.14, for 2.2.10, I think.) 4. make xconfig; make dep; make clean; make bzImage; make modules; make modules_install 5. untarred the Soundblaster Live! source 6. made the sb live modules; installed the sb live modules (this done with script from source of sb live module - also sb live module not for 2.2.14 kernel, probably also for 2.2.10.) 7. ran update-modules 8. moved the kernel into place, edited lilo.conf, rebooted.
A new thing I just noticed: the sb live module claims to load correctly upon boot (I put it in /etc/modules. I still get no sound, but it IS loading correctly. Question: 1. How can I check to see if the module is loaded correctly (sb live)? Is there a test I can run? 2. Should I have run depmod after installing new modules? I think the problem may lie in old modules that I no longer need as modules. Would running depmod clean the dependencies for old modules? As for your ideas: 1. I did not directly make soundcore or anything else, only make modules and install, should I have to make them each separately? I don't have the experience of exporting symbols out by hand (I don't really know what the term symbols referrs to), but I would love to learn; where can I find a howto or any documentation about this? There does not appear to be a modules howto. 2. The patches in question were either for the correct kernel (2.2.14), or an older one (2.2.10) 3. It is possible that my modules.conf is wrong. Debian uses /etc/modutils/aliases and other files in /etc/modutils to change modules.conf. I could not find good documentation about how to use this, but I did find some into in the sb live sources - make a files called emu10k1 in /etc/modutils with the alias info. It reads that file and uses it when I ran update-modules. 4. I did not run depmod after building the modules and installing them. Thank you, Benjamin On Fri, Mar 17, 2000 at 11:24:03AM +0100, Oswald Buddenhagen wrote: > > 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?) > > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
