David Dennis wrote:
> Problem:
>
> initrd.img and module-info point at the original mandrake
> install version files in /boot from a year ago (initrd.img
> -> initrd-2.2.14-15mdk.img and module-info ->
> module-info-2.2.14-15mdk even after a make bzImage in
> /usr/src/linux, a make modules and make modules_install,
> and a make bzlilo. running lilo didn't fix things either.
> So what happens now is my System.map and vmlinuz in /boot
> point at 2.2.17 files but initrd.img and module-info point
> at original install (2.2.14) files. I am not sure but this
> is probably leading to a host of module errors received
> upon bootup, and several important modules (sound card,
> scsi support) are now failing to load.
>
> Forgive this post if it belongs on newbie, I am a old style
> kernel compile person with limited experience with rpm.
> The problem is now that I have a system with 2.2.17 (the
> kernel version I compiled successfully using linus' tools)
> but in /boot there is still the initrd.img and module-info
> from when the system was installed.
>
> I don't want to have to reinstall to fix this, what must be
> done instead? (note I do not have an install CD, this was a
> from-the-net install.
>
>
> -Dave Dennis
> -Seattle WA
> [EMAIL PROTECTED]
Dave....check out 'man mkinitrd'.
--
Alan
