Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I got an easy question for you. I'm trying to update my Linux kernel and I want to use the same configuration as my current working kernel. I need this because during compilation of the kernel, I get the following messages:
Warning: Unable to open on initial console.
Kernel Panic: No init found Try passing init = option to kernel.
Note, I have lilo configured with a new initrd .img for the new kernel. I know that it has to do with the menuconfig stuff because I added ext3 fs support (apparently was disabled by default) and when I recompiled and restarted, it got a little farther than it previously did, though it still panicked later. Thanks for the help!
if you are compiling the same kernel subset (2.4.xx to 2.4.yy or 2.6.xx to 2.6.yy), then u can use the same .config file. you cant use it if you are jumping from 2.x to 2.y
also, you do not need the initrd. plus did u run lilo after kernel compile? why dont u post here all the steps u did (it will be in ur bash history, so just copy them out here), and we can see whatsup. also post ur relevant lilo lines, and output of 'df'.
I'm pretty sure it's the configuration that's messing it up. I assumed at first that running menuconfig would show the settings for the running kernel, which was, of course, wrong. The problem is, I don't know what to enable in order to get the system to boot. I even looked at the messages log to see what gets booted after the panic, and enabled those, but it didn't work.