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

[Emiliano Brunetti]

On Fri, 2004-01-23 at 15:06, Mike Klinke wrote:
> On Friday 23 January 2004 07:09, Emiliano Brunetti wrote:
>  
> > Yes i checked. The problem is not limited to LABEL support however.
> > I can see from compile time logs that 'make install' fails when
> > trying to generate a correct initrd.
> >
> > And i have no idea of how to fix it manually. man mkinitrd didn't
> > help much either.
> >
> > Maybe there are also some more problems, but indeed the initrd
> > image is not generated correctly.
> >
> > Could you explain me how to do it manually or link to me some
> > useful docs?
>  
> 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?

Thanks a lot

E.