I upgraded kernel,

and then booted the system with new kernel and got following message

kernel panic-no init fount try passing init to kernel

=====================
for ref, grub.conf file

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,6)
# kernel /boot/vmlinuz-version ro root=/dev/hda7
# initrd /boot/initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,6)/boot/grub/splash.xpm.gz
title Red Hat Linux 9 (2.4.20-8)
root (hd0,6)
kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/
initrd /boot/initrd-2.4.20-8.img

title RH Linux 9 2.6.7
root(hd0,6)
kernel /boot/bzImage ro root=/dev/hda6
initrd /boot/initrd-2.6.7.img

title Windows
rootnoverify (hd0,0)
chainloader +1

Hi akshatyadav,

Have a look in your /boot directory. You'll notice a file ending with extension .img. This is an initrd file which is a ram disk loader thingy. Your first kernel would have loaded this but when you made your own, a new initrd file is not made for you automatically.

You can make one by going to your /boot directory using the mkinitrd command:

cd /boot
mkinitrd initrd-2.6.7.img 2.6.7

This means to create an initrd file called initrd-2.6.7.img in the boot directory using kernel verion 2.6.7.

I notice in your grub.config file you have the line "initrd /boot/initrd-2.6.7.img". Therefore you do not need to change your grub file again because this was the file the system was looking for and hence gave you the error.

Your alternative is to simply not create a initrd file, and then just comment out the line in the grub.conf file. The side effect of this is that all ext3 partitions will be mounted as ext2.

I have already created initrd image.

try using root (hd0,5) instead of root (hd0,6). Grub numbers the partition from zero. In your case, it doesnt match so it might be the reason.
so /dev/hda6 is actually root (hd0,5).

Tux,

Edit:
you will have to update /etc/fstab to reflect the correct root fs entries. Your earlier entry says while the latest entry says
. I think both these entries should be identical. But I may be wrong