On Thu, Apr 05, 2001 at 07:26:46PM -0500, John R. Sheets wrote: > On Apr 04, 2001, Peter Cordes <[EMAIL PROTECTED]> wrote: > > > Another issue I have with the maestro3 driver is that depmod -a keeps > > > complaining about unresolved symbols. I suppose I may have compiled > > > it against the wrong kernel source tree or something. However, since > > > it loads and runs, I haven't been motivated enough to dig any deeper. > > > > The unresolved symbols must be in a module you haven't tried to load yet. > > When you try, insmod will refuse to load it.
(I should have read your message more carefully, I didn't notice that you said the module with the broken syms did actually load.) > > The maestro3 module does successfully load, though. Does that make sense? > > <[EMAIL PROTECTED] ~># lsmod | grep maestro > maestro3 25232 1 > ac97_codec 7152 0 [maestro3] > soundcore 2384 2 [maestro3] > <[EMAIL PROTECTED] ~># depmod -a > depmod: *** Unresolved symbols in /lib/modules/2.2.18/misc/maestro3.o > AFAIK, that doesn't make sense. Maybe I wrongly assumed that depmod would check against the currently running kernel. Could depmod be checking symbols against a wrong System.map or something? (I think there are options to do so, but I didn't think that was default.) -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , ns.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BCE
