[ILUG] Debian 2.2 Module problems

[Leo Talbot]

On Sat, Sep 09, 2000 at 12:23:52AM +0100, gary at netsoc.tcd.ie wrote:
> On Sat, Sep 09, 2000 at 12:01:18AM +0100, Leo Talbot wrote:
> > Just updated a Debian box from slink to  potato, and also compiled a nice 
> > shiny 2.2 kernel (previously used 2.0.34). When I rebooted I got a flood of
> > unresolved symbol errors. I've rerun update-modules, and the same result 
> > occurs. Any Debian wizards out there that know what the heck is going on?
> 
> Well, you can try 'depmod -a' but I doubt that's the problem...
> IMVHO it might be a problem from the 2.2 compilation. You could try the
> stock potato kernel
> apt-get install kernel-image-2.2.17
> Or just try recompiling the kernel - something went wrong I'd say, but I
> don't know what. Maybe grep the kernel sources for the missing functions,
> work out what modules they'd go into, and make sure those modules are
> compiled... something like that?

Hmmm...don't think I explained myself properly the first time.

I pulled down the kernel-source package (2.2.17), and used the Debian method
(make-kpkg) to compile it. Installed the resulting .deb, ran lilo and 
rebooted. The previous kernel (2.0.34) used loads of modules, but the new one
uses practically none. Upon bootup, when the module dependencies are being
determined, I get a load load of unresolved symbol errors, but _they're from
older kernels_, e.g.
depmod: *** Unresolved symbols in /lib/modules/2.0.34/block/raid0.o

I've run update-modules, but that hasn't fixed the problem, it just gives the
same messages, as does depmod -a. The machine is working fine, and isn't
giving any trouble.

I suppose the real question is, why is it trying to load all those old 
modules?

Leo
-- 
I've got green eyes, red hair, and I'm left handed. A hundred
years ago, I'd have been considered in league with the Devil.
            http://www.cs.tcd.ie/Leo.Talbot
PGP: 0xD4225B61 fp=141B83BE A6F44EEF 8E379887 F6338DE7 D4225B61