DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
View Poll Results: Recommended kernel:
Multiple Choice Poll. Voters: 2. You may not vote on this poll
I charged into compiling the 188.8.131.52 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!
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>
Last edited by Dutch Master; 07-27-2006 at 10:59 AM.
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.
after some initial pain I am successfully into 184.108.40.206!!!
Yea Thank you VERY MUCH!!
What did you change? I tried both the options -
Originally Posted by HappyTux
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.
Originally Posted by Dutch Master
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)
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.