kernel panic, init related, found cause, but cant fix...help :)
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
reboot computer, kernel panic, cant mount this and that.... unable to load init, pass option....
then i try the other method: 1) make dep, 2) make bzImage 3) make modules 4)make modules_install, 5) make install
and i got the follower error msg at the end of compile:
Root device is (3, 65)
Boot sector 512 bytes.
Setup is 4794 bytes.
System is 858 kB
sh -x ./install.sh 2.4.19-36mdkcustom bzImage /usr/src/linux-2.4.19-36mdk/System.map ""
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ exec /sbin/installkernel 2.4.19-36mdkcustom bzImage /usr/src/linux-2.4.19-36mdk/System.map ''
mke2fs 1.32 (09-Nov-2002)
mke2fs 1.32 (09-Nov-2002)
look like there was a problem, the default vmlinuz version is not the same
of the initrd
which mean you have a mdk kernel and not a mdk initrd you may go in trouble
make: Leaving directory `/usr/src/linux-2.4.19-36mdk/arch/i386/boot'
looks like compiling kernel is quite an art. one must really know whats going on.
thanks for ur help
p.s: there was no compile error, when i was doing make dep and bzImage
Last edited by sirpelidor; 12-10-2003 at 05:10 AM.
Did you leave out make modules and make modules_install from your first attempt? Maybe that's all that was missing.
The second message might not be an actual error, just do a mkinitrd to match your new kernel and update your lilo.conf. I think you can even leave out initrd support on most systems now. But get a second opinion on that!
I never do make install, I prefer to just copy over the bzImage, and edit lilo.conf/grub.conf myself.
Doing a make mproper at the start of the compilation process means you're starting with a clean sheet and not carrying anything over from your previous compilation. Make sure to back-up your .config file first though so you don't have to go through everything in xconfig every time.
Also, if you change the EXTRAVERSION= line in Makefile, you can keep each of your compilations separate. You can put in anything you like, e.g. the date/time, a keyword to remind you about a major change, and it really helps in keeping track of what you've tried.
instead of make install, I usually copy the files manually myself, but that's a different question
however, this seams to be related an initrd issue. I'm not familliar with mandrake, but does it use an initrd image? this is a ramdisk image, it can be used by the kernel to load certain files before it can access the hard drive. I've used initrd once to store a nice console background image there, gentoo linux also seams to use it to store a complete root partition structure, I guess because devfs needs some special treatment before it can be used (gentoo uses devfs)
I see you have a devfs line in your lilo.conf. I find this a little confusing, did you try to use devfs, or was that line already there? Did you add another image= entry to lino? please post your entire lilo.conf where, inside a code block.
thanks for ur reply jkobrien and yapp. sorry i couldn't reply last night cause for some weird reason, my box magically lost internet access !? i was unable to check msg til i arrive from work today heh.
this is what i did after i login under failed safe mode: i go back to /etc/lilo.conf, i put default=linux back, then i put image=/boot/vmlinuz back just like before it was modified. lilo -v, lilo -q, reboot system, now my system reboot again but it won't connect to internet anymore.... due to the fact that i was able to boot the system again with my old vmlinuz, i think it has to do with image problem? i don't know...
ok, jkobrien, i didn't do make modules and make modules_install when i first try, because kernel-HOWTO didn't say so. i didn't know if it has a impact on it? what does make modules and make modules_install really doing?
would u plz explain a little about "make mproper" what does it do ? (can't check man page now heheh)
as i said, i clean re-install mdk just try to learn how compile kernel work, i fugred this is the final exame i need to take for me to pass my linux newbie level heh.
yapp, thanks for ur reply. since u and jkobrien both agree not to use "make install", i will make sure i cross that outta my list and according to the research i've been looking through google, i think it maybe a initrd problem, because i was able to boot system again after i put default=linux and /boot/vmlinuz back to my lilo.conf
as for devfs, i didn't know exactly what it does. it got it from mandrake-update, it was 1 of those optional update packages i got, ... i didn't have it before, as for if mdk uses initrd image? i don't know, are there ways to check? when i go into /initrd, there's nothing in there .....
i will go ahead and get my lilo.conf post tonight, thanks for ur help, learning how to compile kernel seems more fun then learn how to compile software from source heheh
There's a good thread on this board about how to recompile. Probably worth checking out, as the LDP HOW-TO is under review at the moment.
You can have certain parts of your kernel as modules, which means they're only loaded up when they're needed. My understanding of it is that this makes your kernel that bit smaller and faster. So "make module" compiles all the code you need for that and "make modules_install" copies all the files over to /lib/modules/<kernel_version>, and probably does some other stuff that I'm not aware of. You can disable modules (first or second step of make xconfig), in which case neither of these two steps apply.
"make mrproper" cleans up _all_ the files generated from your last compilation. "make clean" just cleans up most of them. mrproper is named after some kind of cleaning product - more geek humour!
It seems to me, looking back at your orginal post, that you left out, or didn't put into your lilo.conf, an updated initrd. Again, this is something that can be left out during compilation, but it might be that your system requires it. You can check this under "man mkinitrd" but it's something like...
mkinitrd <image_name> <kernel_version>
The kernel version is the name of the directory under /lib/modules (actually it's the name from the first few lines of the file /usr/src/linux/Makefile) and the image name is whatever you want, but it makes sense to name it something like initrd_<version>.img. When you update your lilo.conf, update the line about the initrd file.
Anyway, hope that helps (and makes some kind of sense!). Well done on sticking with this. You're right that learning how to compile your kernel advances you up a grade towards guru-hood . I think just about everyone has difficulties with their first attempt the difference is whether they see it through or not.