compiled kernel - modules mess (was:kernel doesn't compile?)

[Andre Costa]

On Fri, 23 Jan 2004 16:35:19 +0100
Emiliano Brunetti <emiliano_brunetti at idg.it> wrote:

[...]
> > If you have built a particular kernel, say:
> > 
> > 2.4.22-1.2129.nptl
> > 
> > and want to build a ramdisk image for it you would invoke mkinitrd
> > as follows:
> > 
> > mkinitrd initrd-2.4.22-1.2129.ntpl.img 2.4.22-1.2129.ntpl
> 
> Thanks a lot. It helped indeed.
> 
> But i'd like to add a few comments:
> 
> - the system i am using right now runs a custom kernel and now
> apprently works well, after a manual mkinitrd command;
> 
> - another system where i did the very same things is not working yet.
> Still failing to generate the correct initrd. Apparently there is no
> /lib/modules tree on that system. Strange, isn't it?
> 
> Any idea on how to proceed now with the missing /lib/modules thing?

You can try to reinstall the pre-compiled kernel (or install a new one);
anyway, this wouldn't explain why modules haven't been installed on the
1st place.

... or, you can try to compile your own kernel, as you already did on
one of the boxes. Both approaches should generate a kernel with its
respective /lib/modules dir.

HTH

Andre

-- 
Andre Oliveira da Costa