problem while booting the new kernel...

[shariefbe]

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....

[_madman_]

This may be a shot in the dark, did you format your boot or root partition as VFS?! That seems kind of weird that you would want to use a remote filesystem for your primary partition. Anyway, you don't have "VFS" filesytem support compiled into your kernel. You may have compiled it into a module, but the kernel can't access those until the file system is mounted, unless you use an initrd (short for "initial root device" i believe).

NEWBIES! Always use "ext2" or "ext3" filesystems. It amazes me that so many install docs give people these runarounds about different partitioning and filesystem schemes. Come on, just give the basics; if more advanced settings are needed - the installer probably already knows that.

I also recommend one big / partition only. No seperate /boot, /usr, /home, etc. That is for intermediate to advanced users only.

Anyway, double check your GRUB settings ("e" to edit at the boot menu). Mine is:

default 0
timeout 30

title Gentoo Linux 2.6
root (hd0,2)
kernel /boot/bzImage01 root=/dev/hda3

title Windows ME
rootnoverify (hd0,0)
makeactive
chainloader +1

...yah, believe it or not, I still have an old copy of Win9x on a partition, even though "wine" practically runs everything now.

Notice the difference between the "root(hd0,2)" and "root=/dev/hda3". Both represent the same partition; one the grub way, the other, the linux way.

It's a great idea to leave an entry for your previous kernel too. You never know what might happen.

[shariefbe]

Actually i will tell my status....i am using ubuntu 7.10 distro....in that the default kernel is "linux-2.6.22-14-generic"...in that i planned to install another kernel...its version us "linux-2.6.22.14"..so i downloaded that kernel rom kernel.org and compiled....after compilation i changed the /boot/grub/menu.lst file...i will post the lines of that file below...

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 My Custom Kernel
root (hd0,0)
kernel /boot/vmlinuz-2.6.22.14 root=/dev/hda1 ro

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

so after that when i reboot the system i am getting the previous post error....kindly help me what to do...i am new to linux

[_madman_]

Remember that "initrd" thing I was talking about? One option when running Linux is to make drivers or other features available as modules. This means that instead of the driver(s) being compiled (built) directly inside the kernel (the thing that separates your hardware and software), you can instead have them load dynamically when needed. For example if you have a sound card that you rarely use, you might choose the <m> option to compile it as a separate module that is loaded/unloaded in memory as needed.

The downside to modules is that they are not stored inside of the kernel. So in order for the kernel to access them it must access (usually) the harddisk. This is where you hit the catch 22, double edge sword - the module you are trying to access is the module that would allow you to read from the drive it is stored on.

This is where the initrd (initial ramdisk or rootdisk) comes into play. It is basically a miniature filesystem that can hold modules like this, that are essential for bootup. Put the same initrd line under your custom kernel that you have under your others.

title My Custom Kernel
root (hd0,0)
kernel /boot/vmlinuz-2.6.22.14 root=/dev/hda1 ro
initrd /boot/initrd.img-2.6.22-14-generic

and if it still doesn't work , try changing the "root=" option on the "kernel" line to:

root=UUID=7ef4f8ec-7dd3-4c02-9f24-c9438e6b8bce

[shariefbe]

yes i done this...but even i am getting error as...

Begin :waiting for root file system

what to do?

[shariefbe]

Dear GNU-Fan i done the compilation for the kernel version accourding to the steps given in linux kernel in nushell book...even i am getting the same problem...i posted the problem in the following thread...please refer that error and find me solution...

http://www.linuxforums.org/forum/ubu...-kernel-3.html

post number 22