Thats all well and fine. The problem happens later on when modules don't
get installed. it seems to be related to a new module-info, how is that
made? saving a new kernel is not it, the issue is whats happening that
when i mkinitrd and ln -s to the new image, it still is attempting to load
modules from the old image, failing.
thanks, anyone? if i find this out i'll write a new howto that
specifically covers since initrd.img became standard. thats a redhat /
mandrake thing afaik. severely under documented i have spent hours
looking at sites with initrd.img, ramdisk, kernel rebuild, modules,
module-info as keywords.
Did you know most linux help sites just index automated links out to
usenet archives, most of those of which were questions and not answers,
i.e. just some lone loser such as myself asking a question and no reply?
sucks. and this is the great and powerful mandrake. HA! But it *was* a
pretty desktop til i cocked it up running rpm -Uvh on
kernel-2.2.17mdk-21.i586.rpm .
On Fri, 26 Jan 2001, Chris Spencer wrote:
> Date: Fri, 26 Jan 2001 15:41:24 -0600 (CST)
> From: Chris Spencer <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] rebuild kernel (2nd request)
>
> What I did to find out that information was just run 'make xconfig' in
> /usr/src/linux and look at the configuration. I saved my newly downloaded
> kernel in /usr/local/src/linux, ran make xconfig in there, and then just
> switched between the two windows making sure that the new kernel had the
> same configuration as the old.
>
> -Chris
>
>
> On Fri, 26 Jan 2001, David Dennis wrote:
>
> >
> > Is there a howto that reflects the current mandrake config (ramdisk use,
> > module rebuild included) on howto rebuild the kernel?. I have only seen
> > kernel HOWTO that make little use of ramdisk / module
> > rebuilding. installing kernel-2.2.17-21mdk.i586.rpm did not work. i get
> > *** Unresolved symbols in /lib/modules/2.2.16/(everything) .. this was
> > with make modules and make modules_install .
> >
> > help!
> >
> >
> >
> >
> >
>
>
>
