Kernel 2.6.17.6 - kernel panic on initramfs

jlinkels · 12-16-2006, 03:09 AM

As a matter of fact, if you do not have initrd, you should remove the reference to it from you grub or lilo config. That is the line starting with initrd or initrd=

As a matter of fact, if you look in the description for initrd, it is almost never needed to use initrd as opposed to compile IDE and ext3 support into the kernel. I don't understand why Debian (other distro's as well?) insists on using it.

I am not using initrd for years whenever I recompile my kernel.

jlinkels

gkiagia · 12-16-2006, 05:37 AM

Quote:

Originally Posted by kernelyogi

I am getting the same error as OP - Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers.
I have not tried booting without initrd. Can that be done?
TIA,
~kernelyogi

Yes, it can be done. Just compile some basics like IDE/SATA support and ext3 or reiserfs (whatever you use) into the kernel (not as modules) and then boot without the initrd.

kernelyogi · 12-17-2006, 10:31 PM

Thank you very much, gkiagia and jlinkels. I will try this out. May be I missed adding ide and ext3 support in-kernel

. Will do that and post again.
~kernelyogi

sbarthelmess · 01-31-2007, 12:33 PM

The issue is, you haven't compiled ramdisk support into your kernel. I don't know if it is faster or more efficient to use the ramdisk/initrd support or no ramdisk/initrd and just boot the entire compiled kernel. I know for most purposes, it is best to compile into the kernel for things you use EVERY boot. For example if your root filesystem is EXT3, then compile it into the kernel. If you only mount EXT3 occasionally, then compile it as a module to conserve memory when your not using it.

Good luck booting!

-Seb

dracuss · 08-09-2008, 07:36 AM

Kernelyogi, the point is that you must put into the kernel the access to the filesystems you are going to work with, for example ext3, reiserfs and a couple other filesystems. After that you should be able to boot your kernel without initrd.

brianL · 08-09-2008, 09:08 AM

Another thread has risen from the dead. Look at the dates before posting.