Very Computer

     I have installed RH8.0 with Grub boot loader. I download the src for
linux-kernel 2.4.20. I have successful build the bzImage and System.map into
the /boot directory.

     Then I go to the /etc/grub.conf and modify the file as follow:

default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.18-14)
        root (hd0,0)
        kernel /vmlinuz-2.4.18-14 ro root=LABEL=/ hdc=ide-scsi
        initrd /initrd-2.4.18-14.img
title Red Hat Linux (2.4.20)
        root (hd0,0)
        kernel /vmlinuz-2.4.20 ro root=LABEL=/ hdc=ide-scsi

Then I try to boot from the new kernel, but fail to work. This is because I
misc the thrid line start with initrd.

I wonder how can I create a initrd-2.4.20.img file from the new kernel
build. Also I have to re-link the System.map to point to the
System.map-2.4.20 file.

Any help or point will be greatly apperciated.

Thanks,
Kevin

Quote:

> Then I try to boot from the new kernel, but fail to work. This is because I
> misc the thrid line start with initrd.

  /sbin/mkinitrd initrd-img kernel_modules_name

You need to use the name of the modules directory in /lib/modules rather
than the kernel name. In your case it would be something like:
   mkinitrd initrd-2.4.20.img 2.4.20

BTW, I find it's usually easier to build the necessary boot modules directly
into the kernel rather than using an initrd. Except in unusual
circumstances, the modules will never be unloaded so you don't gain
anything by using initrd. Of course, you can (and should) keep other
modules such as sound, usb, video as loadable modules.

Quote:

> I wonder how can I create a initrd-2.4.20.img file from the new kernel
> build. Also I have to re-link the System.map to point to the
> System.map-2.4.20 file.

> Any help or point will be greatly apperciated.

> Thanks,
> Kevin

Why don't you just issue a 'make install' after compiling your kernel
and modules? It will take care of everything, including the necessary
lines in grub.conf if necessary.

By the way, on RH 8.0, the grub.conf is usually located in
/boot/grub/grub.conf

This is what I do when compiling a new kernel, and it never fails (now
that I got it that you can't compile a kernel under RH 8.0 if your
current language is French :/, but thats another story, so I just change
the language and it works):

copy my old .config
make xconfig (or make menuconfig)
make dep
make bzImage
make modules
make modules_install
make install

I reboot, and there is a new entry in the GRUB menu.

The kernels 2.5.* seem to have a simpler compiling process (no 'make
dep'...), but I haven't succeeded in booting properly with them.
But 2.4.20 works like a charm.

/ ...

Quote:> This is what I do when compiling a new kernel, and it never fails (now
> that I got it that you can't compile a kernel under RH 8.0 if your
> current language is French :/, but thats another story, so I just change
> the language and it works):

> copy my old .config
> make xconfig (or make menuconfig)
> make dep

Quote:> make bzImage
> make modules
> make modules_install
> make install

Quote:> I don't get it.

> Why don't you just issue a 'make install' after compiling your kernel
> and modules? It will take care of everything, including the necessary
> lines in grub.conf if necessary.

> By the way, on RH 8.0, the grub.conf is usually located in
> /boot/grub/grub.conf

But anyway thanks for your advise.

Quote:

> This is what I do when compiling a new kernel, and it never fails (now
> that I got it that you can't compile a kernel under RH 8.0 if your
> current language is French :/, but thats another story, so I just change
> the language and it works):

> copy my old .config
> make xconfig (or make menuconfig)
> make dep
> make bzImage
> make modules
> make modules_install
> make install

> I reboot, and there is a new entry in the GRUB menu.

> The kernels 2.5.* seem to have a simpler compiling process (no 'make
> dep'...), but I haven't succeeded in booting properly with them.
> But 2.4.20 works like a charm.