Hello,
I am new to linux...i tried to compile the kernel version 2.6.22.14....i compiled all the things and i installed all the modules...after typing "make install" i am getting this following things...

root@sharief-desktop:/usr/src/linux-2.6.22.14# make install
sh /usr/src/linux-2.6.22.14/arch/i386/boot/install.sh 2.6.22.14 arch/i386/boot/bzImage System.map "/boot"
In order to use the new kernel image you have just installed, you
will need to reboot the machine. First, however, you will need to
either make a bootable floppy diskette, re-run LILO, or have GRUB
installed.

Checking for ELILO...No

GRUB is installed. To automatically switch to new kernels, point your
default entry in menu.lst to /boot/vmlinuz-2.6.22.14
root@sharief-desktop:/usr/src/linux-2.6.22.14# cd /boot
root@sharief-desktop:/boot# ls
abi-2.6.22-14-generic grub System.map vmlinuz-2.6.22.14
config initrd.img-2.6.22-14-generic System.map-2.6.22.14 vmlinuz-2.6.22-14-generic
config-2.6.22.14 initrd.img-2.6.22-14-generic.bak System.map-2.6.22-14-generic
config-2.6.22-14-generic memtest86+.bin vmlinuz


i dont what to do next...how to change the boot file....please help me....

Right, so you have installed the modules and the kernel is in place on /boot.

From root open /boot/grub/grub.conf in an editor. You should already find the new entry for vmlinuz-2.6.22.14.
You should formally also find an entry like "default=0" in there towards the top. Assuming it says 0, you can either move the new entry to the top, or change the default to the new one (remember the entries, each starting with "title", is counted from 0).
Third alternative is to reboot and choose your new entry in the menu before Linux starts booting (you might have to press ESC to see the menu at the start).

Mons
PS! If you get problems, post your grub.conf file and we'll have a look

no..there is nothing in /boot/grub/grub.conf.....when i give this command "vi /boot/grub/grub.conf" the file is opening......nothing is there...help me

i am not having any lilo.conf and grub.conf in my system...i dont know what to do...help me....

Strange. So whats the content of the /boot/grub folder (post "ls -l" preferably)? Do you have a menu.lst by any chance?

Maybe the grub configuration file is /boot/grub/menu.lst

This is the content of the /boot/grub/menu.lst


title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=7ef4f8ec-7dd3-4c02-9f24-c9438e6b8bce ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet

title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=7ef4f8ec-7dd3-4c02-9f24-c9438e6b8bce ro single
initrd /boot/initrd.img-2.6.22-14-generic

title Ubuntu 7.10, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

when i type "ls -l" i found the below things

root@sharief-desktop:/boot/grub# ls -l
total 204
-rw-r--r-- 1 root root 197 2008-09-28 14:08 default
-rw-r--r-- 1 root root 15 2008-09-28 14:08 device.map
-rw-r--r-- 1 root root 8660 2008-09-28 14:08 e2fs_stage1_5
-rw-r--r-- 1 root root 8452 2008-09-28 14:08 fat_stage1_5
-rw-r--r-- 1 root root 15 2008-09-28 14:09 installed-version
-rw-r--r-- 1 root root 9152 2008-09-28 14:08 jfs_stage1_5
-rw-r--r-- 1 root root 4265 2008-11-21 18:37 menu.lst
-rw-r--r-- 1 root root 7860 2008-09-28 14:08 minix_stage1_5
-rw-r--r-- 1 root root 10132 2008-09-28 14:08 reiserfs_stage1_5
-rw-r--r-- 1 root root 512 2008-09-28 14:08 stage1
-rw-r--r-- 1 root root 110292 2008-09-28 14:09 stage2
-rw-r--r-- 1 root root 9980 2008-09-28 14:08 xfs_stage1_5

yes...i edited in the /boot/grub/menu.lst.....
then i got the newly compiled kernel in the menu while i reboot the system....but when i enter into that i am getting this following error........

starting up.....
uncompressing linux...ok,booting the kernel
[ 53.987716]kernel panic - not syncing: VFS : unable to mount root fs on unknown -block(0.0)


wher will be the root fs...how to mount that....

how to boot the new kernel please do favour for me.....i dont know what to do....when i boot from new kernel i am getting the error message..i mean in the last post.....somebody help me to clear this

That error message is almost always because you compiled file system support for the file system type support of your linux partition as a module. If the root fs type support is a module then you _must_ use an initrd with that module included. Since making an initrd is rather complicated, the best solution for a beginner is to simply compile it into the kernel, not as a module. Recompile your kernel, this time selecting compiled in for the root fs type. In fact, to make things simpler just compile in any fs type support you intend to use.

Actually i didnt select the kernel as module..in fact i dont know too...but you told that the kernel is selected as module....how to clear this..and how to remove the compiled kernel and please can you give the correct step by step procedure to compile the kernel?Thanks for your patience

If you're not sure whether you selected it as a module, then probably you shouldn't be messing around in your kernel. Just fire up your distro with your "normal" (working) kernel and from there change the dysfunctional kernel as you did before (making the necessary changes) and then recompile it.

thats what how to fire up that kernel...whats the procedure....and please send me steps by step procedure to compile the kernel...so that i can easily compil it...cause i was confused by searching in net..Thanks

When GRUB comes up, hit ESC and then select the usual kernel, i.e. the one you did not compile yourself. Then you should be able to go into linux with the right kernel.

Regarding the compilation question: google is your friend!

If you have deleted you old kernel entry in the menu.lst file, you will have to boot with a DVD, mount the hard drive there and then put in the old kernel line again. You might find the old entry in the backup file (menu.lst~ or menu.bak).
Also when you get into the harddrive again, check the /etc/fstab file. You should at least have a root there (with the'/' character). It should either use the same UUID or the device itself (e.g. /dev/sda1 or /dev/hda1).

Also are you sure the UUID is exactly the same as it was? If you notice during boot, before the kernel panic try to see what the hard drive is recognised as, or whether you have other error messages before the panic.

If you haven't got the old kernel and you have compiled in the correct file system in the kernel, you can try to replace the root=UUID=7ef4f8ec-7dd3-4c02-9f24-c9438e6b8bce from grub with the root=/dev/xxxx. To find the correct name you can try fdisk -l /dev/sda (or again with hda instead of sda). If you have only got one hard-drive its mostly likely one of the two. In addition to the hda/sda you will need to add the partition number to it. Let us know how it goes.

Mons