Hello,

I charged into compiling the 2.6.17.6 kernel, updating from my initial kernel 2.4.27 for sarge 3.1r2 on my IBM thinkpad 600x - but have been getting a consistent initramfs kernel panic error. I have recompiled 5 times looking for possible fixes in the menuconfig, with no success. I am a newbie to linux, although had some success figuring out the initial install and playing with the basics.

Here is the error (occurs very early during the boot):
"Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers"

of course, I set initramfs = () per the help, since i don't know where else to send it. I've also looked all over the web for initramfs and kernel 2.6.* compiling info. I may have been overzealous in my cleaning out "unecessary" modules and options during my 5 successive attempts, but I'm following the help recommendations as much as possible.

I haven't found other questions that address this error. I'm still learning the ropes, although I'm sadly getting used to recompiling again and again... Please help!

I used this guide to get my 2.6.17.* kernels working: http://www.digitalhermit.com/linux/K...ild-HOWTO.html The only thing you'll need to change is to add the -o switch when building the initrd file. 'Cause mkinitrd nowadays defaults to writing to /dev/null (e.i. the digital wastebasket) unless an outputfile is specified. Good luck!

Thanks Dutch Master.
I'm not entirely sure how to add in the -o switch for the initrd build. I'm still in the need for very verbose descriptions...

I'm checking out the link.

Give up on an initrd and compile support for your file system, chipset on the motherboard .... directly into the kernel then the problem is solved.

Look in the section "Create Initial RAMDisk", there is a command "$ mkinitrd /boot/initrd-2.6.0.img 2.6.0" You'll need to change that command to "mkinitrd -o /path/to/initrd.img-<kernel-version>" Make sure you've got all modules you want to include into the Ramdisk in the proper directory, /lib/modules/<version>/initrd is the best option (but may clash with your current kernel)

<edit>HappyTux gives a good alternative, but for most users perhaps a bit too much geeky (read as: complicated)</edit>

Thnx

am recompiling and adjusting the mkinitrd.

RE: skipping initrd and compiling fs and chipset into kernel - this is what I have been attempting for the past 5 tries.

currently I have ext3, ext2, and reiserfs all loading, although i hadn't included reiserfs before. Or are you refering to something else?

I'm not clear on how else to do this, almost everything is loaded into the kernel and i have only a few modules. my chipset (PIII coppermine) is already highlighted. Once this latest compile is complete per the mkinitrd suggestions, I'll report back.

Thanks again

Well,
after some initial pain I am successfully into 2.6.17.6!!!
Yea Thank you VERY MUCH!!

I voted for 6.9. You really are looking toward the future

Is there a kernel 2.8.* and 6.9.* ???? The latest stable version is 2.6.17.7 !!!

No. 2.8 is still in alpha and 6.9 is an obvious sexual reference.

I'll try that guide out. I've been having some problems of my own when it comes to recent kernel compilation.

Oh, now I see the light.

What did you change? I tried both the options -

and

Also, note that "/lib/modules/<version>/initrd" was not found in my system after compilation. How to get it? I am in learning/falling mode. Pls help!

My system is Debian 3.1 R3 and trying the latest 2.6.19 kernel.

~kernelyogi

What is your problem exactly? What happens if you compile everything you need into the kernel and boot without an initrd?

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