Very Computer

by **Sony Anton** » Sun, 09 Feb 2003 00:00:26

Yesterday I downloaded the latest redhat kernel ( 2.4.18-24.8.0 ). But
unlike the earlier ones, it didn t update grub.conf. Then I tried to do
that manually. But I found out that there is no corresponding initrd.
I didn t get any errors while up2date ing. So what I downloaded cannot be
corrupt.
Any suggestions.
--sony

by **Sony Anton** » Sun, 09 Feb 2003 12:18:09

> Yesterday I downloaded the latest redhat kernel ( 2.4.18-24.8.0 ). But
> unlike the earlier ones, it didn t update grub.conf. Then I tried to do
> that manually. But I found out that there is no corresponding initrd.
> I didn t get any errors while up2date ing. So what I downloaded cannot be
> corrupt.
> Any suggestions.

I solved this by
1. manually editing grub.conf and
2. creating a new initrd-2.4.18-24.8.0.img

The first one is easy. For the second one I started from the existing
initrd-XX.img. gunzip d it and mounted it on a directory with the -oloop
option. Then I overwrote the 2 lib/*.o files from the corresponding ones
from the new kernel's /lib/modules directory. Then I unmounted it gzip d it
and renamed it as initrd-2.4.18-24.8.0.img and copied it to boot directory.
Then I booted the new kernel and ran depmod -a.
Finally I uninstalled the old kernel.

I believe this is an overlooked part from RedHat.

--sony

Quote:> --sony

by **Allen Kistle** » Sun, 09 Feb 2003 16:12:44

>>Yesterday I downloaded the latest redhat kernel ( 2.4.18-24.8.0 ). But
>>unlike the earlier ones, it didn t update grub.conf. Then I tried to do
>>that manually. But I found out that there is no corresponding initrd.
>>I didn t get any errors while up2date ing. So what I downloaded cannot be
>>corrupt.
>>Any suggestions.

> I solved this by
> 1. manually editing grub.conf and
> 2. creating a new initrd-2.4.18-24.8.0.img

> The first one is easy. For the second one I started from the existing
> initrd-XX.img. gunzip d it and mounted it on a directory with the -oloop
> option. Then I overwrote the 2 lib/*.o files from the corresponding ones
> from the new kernel's /lib/modules directory. Then I unmounted it gzip d it
> and renamed it as initrd-2.4.18-24.8.0.img and copied it to boot directory.
> Then I booted the new kernel and ran depmod -a.
> Finally I uninstalled the old kernel.

> I believe this is an overlooked part from RedHat.

This is a familiar process to me because I've got a RH7.0 box on which
the kernel rpms and mkinitrd just won't make a good initrd. (Funky
setup. Long story. Maybe later.) I know the described process works,
but ...

I haven't done the newest-kernel thing yet this week with 2.4.18-24.x.x
(different box), but I think mkinitrd would be easier as long as
mkinitrd works on your system. (Works on all my others.) Less
gunzipping, gzipping, mounting, umounting, cp'ing files, etc. mkinitrd
does it all for you.

mkinitrd is one of those nice extras you get with RH. It's not a
"standard" Linux thing.

Very Computer

Missing initrd in RH 2.4.18-24.8.0 ??

Missing initrd in RH 2.4.18-24.8.0 ??

Missing initrd in RH 2.4.18-24.8.0 ??

Missing initrd in RH 2.4.18-24.8.0 ??