Hello All,
I just compiled the latest kernel 2.6.16.11 from source and its created a vmlinuz-2.6.16.11 file along with a link vmlinux in the /boot folder. Since 'make bzImage' only creates a kernel image, the 'make install' was used finally to get it into the boot folder for grub. In grub's menu.lst, I configured the kernel as /boot/vmlinuz and root=/dev/hdan where n is my partition and its the same entry as in my existing kernel entry. The image entry is #shed as there was no img created. When I boot into the new kernel, after a series of initial text, it gives a kernel panic at the root= entry. Its the same as before so why can't it mount the VFS on that partition? It cannot recognise hdan. (n is a number)
Any clues?
Regards,
Rony.
___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
On Monday 01 May 2006 20:54, Rony wrote:
I just compiled the latest kernel 2.6.16.11 from source and its created a vmlinuz-2.6.16.11 file along with a link vmlinux in the /boot folder. Since 'make bzImage' only creates a kernel image, the 'make install' was used finally to get it into the boot folder for grub. In grub's menu.lst, I configured the kernel as /boot/vmlinuz and root=/dev/hdan where n is my partition and its the same entry as in my existing kernel entry. The image entry is #shed as there was no img created. When I boot into the new kernel, after a series of initial text, it gives a kernel panic at the root= entry. Its the same as before so why can't it mount the VFS on that partition? It cannot recognise hdan. (n is a number)
which distro?
On Tue, May 02, 2006 at 03:04:09AM +0000, Dinesh Joshi wrote:
On Monday 01 May 2006 20:54, Rony wrote:
I just compiled the latest kernel 2.6.16.11 from source and its created a vmlinuz-2.6.16.11 file along with a link vmlinux in the /boot folder.
In grub's menu.lst, I configured the kernel as /boot/vmlinuz and root=/dev/hdan where n is my partition and its the same entry as in my existing kernel entry. The image entry is #shed as there was no img created.
which distro?
Kubuntu 5.10. Does it make a difference? I thought kernels were independent of distros. What about the initrd.img files, what does one do about that when using a new kernel?
Regards,
Rony.
Send instant messages to your online friends http://uk.messenger.yahoo.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Rony,
Kubuntu 5.10. Does it make a difference? I thought kernels were independent of distros. What about the initrd.img files, what does one do about that when using a new kernel?
Installing the kernel by hand is really not recommended as it's prone to errors. Build a package and install it. First install `kernel-package' which is a set of helper scripts to create a Debian/Ubuntu package. $ sudo apt-get install kernel-package Then from the Linux kernel source tree, do this (after doing `make menuconfig`) $ make-kpkg --revision 1.0 kernel_image This will create a .deb called kernel-image-2.6.16.11_1.0_i386.deb just outside the directory. Install it as $ sudo dpkg -i kernel-image-2.6.16.11_1.0_i386.deb And you are done. Enjoy the new kernel.
Regards, BG
- -- Baishampayan Ghose b.ghose@ubuntu.com Ubuntu -- Linux for Human Beings http://www.ubuntu.com/
1024D/86361B74 BB2C E244 15AD 05C5 523A 90E7 4249 3494 8636 1B74
On 5/2/06, Rony ronbillypop@yahoo.co.uk wrote:
What about the initrd.img files, what does one do about that when using a new kernel?
You need to re-create the initrd image for the new kernel. Refer to the kernel compilation manual that you've been referring to so far for that.
Siddhesh
On 5/2/06, Siddhesh Poyarekar siddhesh.poyarekar@gmail.com wrote:
On 5/2/06, Rony ronbillypop@yahoo.co.uk wrote:
What about the initrd.img files, what does one do about that when using a new kernel?
You need to re-create the initrd image for the new kernel. Refer to the kernel compilation manual that you've been referring to so far for that.
Siddhesh
--
Hi Ubuntu comes with mkinitramfs to create ramdisks instead of mkinitrd on other distros (which ?). It creates the ramdisk as a cpio archive instead of gzip.
Regards, Mohan S N -- There will be plenty of time to rest in the grave. - Paul Erdos
On Tuesday 02 May 2006 03:55, Rony wrote: *snip*
which distro?
Kubuntu 5.10. Does it make a difference? I thought kernels were independent of distros. What about the initrd.img files, what does one do about that when using a new kernel?
Yes. It makes a difference. Some vendors (eg. Redhat) apply too many patches so compiling and installing a decent vanilla kernel becomes very difficult.
On 5/2/06, Rony ronbillypop@yahoo.co.uk wrote:
Hello All,
I just compiled the latest kernel 2.6.16.11 from source and its created a vmlinuz-2.6.16.11 file along with a link vmlinux in the /boot folder. Since 'make bzImage' only creates a kernel image, the 'make install' was used finally to get it into the boot folder for grub.
You'll need to do 'make modules_install' to install the new kernel modules too.
In grub's menu.lst, I configured the kernel as /boot/vmlinuz and root=/dev/hdan where n is my partition and its the same entry as in my existing kernel entry. The image entry is #shed as there was no img created. When I boot into the new kernel, after a series of initial text, it gives a kernel panic at the root= entry. Its the same as before so why can't it mount the VFS on that partition? It cannot recognise hdan. (n is a number)
Are you sure you compiled ide-disk into the kernel? If not and if the earlier modules_install is also not done then its possible thatyour disk is not found.
Also, you need to compile your primary filesystem driver into the kernel. If your root filesystem is reiserfs for example then reiserfs should be compiled into the kernel.
And then you have a different set of problems if you're using a ramdisk (initrd).
You can still boot with your old kernel though. when faced with the grub menu press 'c' to go into grub shell. The execute the following commands (I've assumed you're using hda5 i.e. grub disk (hd0,4) and your old kernel is vmlinuz 2.6.1):
-------------- # Specify the root partition root (hd0,4)
# specify kernel location. TAB will give you an autocomplete list kernel /boot/vmlinuz-2.6.1 root=/dev/hda5 ro
#boot the kernel boot --------------------
Again, if your distro uses initrd then before 'boot' you need to specify the initrd image location with 'initrd <image location>'
Refer to the grub manual online to know more about the options.
Siddhesh
On Tue, 2006-05-02 at 09:26 +0530, Siddhesh Poyarekar wrote:
Also, you need to compile your primary filesystem driver into the kernel. If your root filesystem is reiserfs for example then reiserfs should be compiled into the kernel.
And then you have a different set of problems if you're using a ramdisk (initrd).
If the OP is going the ramdisk route, then the / filesystem module can be put in the initrd as well. SuSE and Fedora have mkinitrd tool to create the initrd.gz file.
-- Arun Khan (knura at yahoo dot com) Matter cannot be created or destroyed, nor can it be returned without a receipt.
On Tue, May 02, 2006 at 02:24:21AM +0530, rony wrote:
I just compiled the latest kernel 2.6.16.11 from source
I boot into the new kernel, after a series of initial text, it gives a kernel panic at the root= entry. Its the same as before so why can't it mount the VFS on that partition? It cannot recognise hdan. (n is a number)
Thanks to everyone who provided their inputs on this problem. It is not solved yet but now I created another problem so I guess the menuconfig will need a very detailed observation. Last time I had used the make menuconfig, clean, modules as well as modules_install so that was not a problem. The problem I feel is that by default the kernel supports ext3 journaling through module '<M>' instead of '<*>' so it gives an error of not recognising block (0,0) and cannot mount the fs on root=/dev/hdax. However even after setting it embedded, the new kernel now does not even go till the initial bootup messages. While repeating the process of 'make' I have got a lot of errors during compilation so I will do a clean retry and give feedback.
BG's suggestion of 'kernel-package' and the make-kpkg..... command was very usefull and I use that now. More feedback after some more results.
Regards,
Rony.
___________________________________________________________ Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. http://uk.mail.yahoo.com
Thanks to everyone who provided their inputs on this problem. It is not solved yet but now I created another problem so I guess the menuconfig will need a very detailed observation. Last time I had used the make menuconfig, clean, modules as well as modules_install so that was not a problem. The problem I feel is that by default the kernel supports ext3 journaling through module '<M>' instead of '<*>' so it gives an error of not recognising block (0,0) and cannot mount the fs on root=/dev/hdax. However even after setting it embedded, the new kernel now does not even go till the initial bootup messages. While repeating the process of 'make' I have got a lot of errors during compilation so I will do a clean retry and give feedback.
Are you sure you're not using an initrd? Because if you have an initrd.img in your directory tree then its quite likely that your stock kernel uses an initrd. If that is the case then you will need to build the ramdisk. Either that or run carefully through menuconfig and make sure that everything that you need (filesystem, critical drivers, etc.) are compiled in. ext2 and ext3 must be compiled into the kernel (with the [*] ). If your filesystem is anything else then you must cmpile that option into the kernel. For example I use reiserfs and have compiled reiserfs into the kernel.
Also, if you plan not to use the initrd, you must comment out that line from the menu.lst.
BG's suggestion of 'kernel-package' and the make-kpkg..... command was very usefull and I use that now. More feedback after some more results.
I think you have a 'make deb' option in the linux makefile that makes a debian package for your kernel. Never used it though. Always found the make install much more reliable, probably because I started with that approach and stuck with it all through. To find out all of the things you can do with the make command in the linux kernel source just do 'make help'.
Siddhesh
On Thursday 04 May 2006 00:50, Rony wrote: *snip*
so that was not a problem. The problem I feel is that by default the kernel supports ext3 journaling through module '<M>' instead of '<*>' so it gives an error of not recognising block (0,0) and cannot mount the fs on root=/dev/hdax. However even after setting it embedded, the
*snip*
But thats right. The kernel will not support EXT3 by default. It will support it via loadable modules. See EXT3 is just an extension to EXT2. They can be used interchangeably meaning if you have a partition formatted as EXT3 then you can still mount it as EXT2 and vice-versa. The problem you are facing must be because the FS on the partition is either EXT2 or something else which hasn't been included in the kernel by default.
My knowledge is rusty but the logic seems to be sound. Anyways wait for a second opinion.
On Thu, May 04, 2006 at 12:50:58AM +0530, rony wrote:
However even after setting it embedded, the new kernel now does not even go till the initial bootup messages. While repeating the process of 'make' I have got a lot of errors during compilation so I will do a clean retry and give feedback.
The new problem of the boot process hardly going further was due to the extra entries 'quiet' and 'splash'in the kernel line in menu.lst. Now It boots like last time and stops again like first time at this...
"VFS:Cannot open root device "hdax" or unknown-block(0,0) Please append a correct "root=" boot option Kernel Panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0)"
I am not using any initrd image and there is no entry for the same in menu.lst.
I had downloaded this kernel from www.kernel.org and it is from the 'F' link on the rhs of the first line that mentions this as the latest stable kernel. Do I need to patch it with the main link which leads to a patch file?
Regards,
Rony.
___________________________________________________________ Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. http://uk.mail.yahoo.com
On Thu, 2006-05-04 at 12:26 +0530, Rony wrote:
"VFS:Cannot open root device "hdax" or unknown-block(0,0) Please append a correct "root=" boot option Kernel Panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0)"
The kernel does not have the driver to detect the HDD and thus it is complaining that it cannot mount the root fs.
Did you select <*> for the IDE driver in menuconfig? Additionally, select the IDE/SATA controller chipset as <*> in menuconfig. Also, suggest do 'make mrproper' prior to 'make menuconfig.'
I am not using any initrd image and there is no entry for the same in menu.lst.
If you build a monolithic kernel then no need for initrd image.
-- Arun Khan (knura at yahoo dot com) Sattinger's Law: It works better if you plug it in.
On Thu, May 04, 2006 at 01:57:22PM +0530, Arun K. Khan wrote:
On Thu, 2006-05-04 at 12:26 +0530, Rony wrote:
"VFS:Cannot open root device "hdax" or unknown-block(0,0) Please append a correct "root=" boot option Kernel Panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0)"
The kernel does not have the driver to detect the HDD and thus it is complaining that it cannot mount the root fs.
Did you select <*> for the IDE driver in menuconfig? Additionally, select the IDE/SATA controller chipset as <*> in menuconfig. Also, suggest do 'make mrproper' prior to 'make menuconfig.'
I redid the configuration and the make mrproper was handy in cleaning up old mess along with make clean. Still the result is just the same. I get the feeling the kernel itself is buggy or is not meant for older computers. The IDE chipset option has only one entry for Intel called 'Intel PIIXn chipsets support'.
Regards,
Rony. Send instant messages to your online friends http://uk.messenger.yahoo.com
I redid the configuration and the make mrproper was handy in cleaning up old mess along with make clean. Still the result is just the same. I get the feeling the kernel itself is buggy or is not meant for older computers. The IDE chipset option has only one entry for Intel called 'Intel PIIXn chipsets support'.
hi,
I am facing the same problem exactly .It does not load my root partition after compiling the new kernel and there wasn't anything new that i used to do in prev kernels.my kernel version is 2.6.16 Will keep the list updated on any new progress.....
WIth warm regards, Pankaj
On Sat, May 06, 2006 at 11:11:37AM +0100, Pankaj Dekate wrote:
I am facing the same problem exactly .It does not load my root partition after compiling the new kernel and there wasn't anything new that i used to do in prev kernels.my kernel version is 2.6.16 Will keep the list updated on any new progress.....
Thank God, its the kernel problem, and not a compiling mistake. Looking forward to any workaround for this. This is what they must be calling 'bleeding edge' kernel, you get lots of cuts and briuses. :-D
Regards,
Rony.
___________________________________________________________ Yahoo! For Good - Sponsor a London Marathon runner - http://uk.promotions.yahoo.com/charity/london-marathon
Thank God, its the kernel problem, and not a compiling mistake. Looking
</snip>
I'm not sure if this is a kernel problem. I'm using a custom compiled 2.6.16 kernel on my old box. Its a Celeron 500MHz mendocino, 192 MB RAM and a 10 GB IDE disk. Boots alright without any issues.
Double check your configuration. You must have missed out on something.
Regards, Siddhesh
On Sat, May 06, 2006 at 10:35:43PM +0530, Siddhesh Poyarekar wrote:
I'm not sure if this is a kernel problem. I'm using a custom compiled 2.6.16 kernel on my old box. Its a Celeron 500MHz mendocino, 192 MB RAM and a 10 GB IDE disk. Boots alright without any issues.
Which is the tar file that you downloaded? Are you using 2.6.16.11 ?
Regards,
Rony.
___________________________________________________________ Switch an email account to Yahoo! Mail, you could win FIFA World Cup tickets. http://uk.mail.yahoo.com
On 5/7/06, ronbillypop@yahoo.co.uk ronbillypop@yahoo.co.uk wrote:
Which is the tar file that you downloaded? Are you using 2.6.16.11 ?
Nope. i had compiled 2.6.16. If you have 2.6.16.11 and you wanna install the 2.6.17 patch you have to reverse the patches from 2.6.16.1-11 and then apply that patch. Atleast that was the case earlier when I was in a habit once of downloading every new kernel patch and compiling just for fun ;-)
Try patching the kernel to the latest increment (2.6.16.14). If it doesn't work then there's something wrong with your configuration.
Siddhesh -- http://siddhesh.tk
On Thu, 2006-05-04 at 12:26 +0530, Rony wrote:
"VFS:Cannot open root device "hdax" or unknown-block(0,0) Please append a correct "root=" boot option Kernel Panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0)"
you need to append the root="" option in your grub like below
-- kernel /boot/vmlinuz-2.6.15 root=/dev/hda1 -- obviously, replace hda1 with your hard disk partition (root partition /)
and like earlier suggesitons, make sure your filesystem and IDE driver is compiled in
-Erle
-
Arun K. Khan -
Baishampayan Ghose -
Dinesh Joshi -
Erle Pereira -
Mohan Nayaka -
None -
Pankaj Dekate -
ronbillypop＠yahoo.co.uk -
Siddhesh Poyarekar