Menu ▾ ▴

Kernel panic ... Try passing init= option to

2004-10-05
2013-04-08
  • David Horton

    David Horton - 2004-10-05

    (This message was originally sent to the mailing list by Philippe Ney --Dave)

    Subject: Kernel panic ... Try passing init= option to kernel.    A solution

    Hi all,

    First of all, many thanks to David Horton for this great job.

    I have a some year knowing of linux. But to have a deeper understood of
    the init stage, I started playing with Pocket Linux.

    And then "bravo" for the documentation which is really clever.

    I spent all the afternoon long to make the chapter 2 working, reading many
    of the message from this list. And as now it works, I want to give some
    useful tips hoping this could help other people having the same problem.

    My system is Debian testing, kernel 2.4.18

    The package I decided to use are : bash-3.0, linux-2.6.8.1, lilo

    1) bash

    No problem with compilation. The final footprint after the strip is 721628

    2) lilo

    The last version of lilo doesn't need boot.b or any other boot.0X00.
    Also, don't try to copy some map file you founded somewhere.
    But don't forget to run :

    # lilo -r /mnt

    And the needed files will be created (/mnt/boot/boot.0200 and
    /mnt/boot/map)

    3) The kernel

    The problem of the "Kernel panic:..." is solved by adding configuration
    for

      * Kernel support for ELF binaries

    Otherwise the kernel wouldn't be able to run bash.

    Hope this help,
    Philippe

     
    • Nobody/Anonymous

      I had the same problem in Chapter 3.
      In my case I discovered that once I umounted /dev/ram7 all files were lost.  So, my compressed root disk was empty.
      My workaround was to use a loopback device instead.
      I don't know yet the reason why the files are lost in the ramdisk. I'm building the floppies in Fedora Core 2 running on an Athlon 2500.

      Sergio.

       
    • William Branch

      William Branch - 2004-10-31

      I'm having the same problem. My kernel has been elf compatible from the beginning however. Bash compiles just fine statically. I run an ldd on bash and it returns that it is not dynamic, so I know bash works. I've followed the kernel compile instructions in version 3.0.

      I will now try to use the floppies from the web site and test those to see if I get different results.

      Regards,
      Bill

       
    • Nobody/Anonymous

      I received this error message because I forgot to
      include all the libraries listed by running the
      'ldd /bin/bash' command. Once all the libraries were included on the root filesystem, it booted fine. Duh.

       
    • Nobody/Anonymous

        I am facing problem in chapter-3.

          The error occuring is " kernel panic.... Try passing init=option".

                I recompiled my kernel with ELF binary support as suggested above by MR. Dhorton. Still same error is comming. I did successfully chaptger-2 but facing this type of problem in chapter-3.
              I also tried by passing "init= option" and also tried with the option " root= 02:00" but still I could not get rid of that problem
        
      Help!

       
    • Nobody/Anonymous

      I am facing problem in chapter-3.

          The error occuring is " kernel panic.... Try passing init=option".

                I recompiled my kernel with ELF binary support as suggested above by MR. Dhorton. Still same error is comming. I did successfully chaptger-2 but facing this type of problem in chapter-3.
              I also tried by passing "init= option" and also tried with the option " root= 02:00" but still I could not get rid of that problem
        
      Help!

       
    • inverse_cow

      inverse_cow - 2005-03-26

      Hello,

        I've been having this problem as well, from the get go in Chapter 1.  I've yet to get the first system beyond the Root Disk stage due to the Init issue.  What progress I made on this delima involved placing the INIT program from my Slackware-Current distro into the /bin directory.  So now it gets as far as asking me for a Run Level, and thusly leaves me stumpted.

        Am I on the right track or off on a tangent?  If so, where should I go from here?

        I am using the 2.4.29 kernel compiled with all the mentioned options in the project pages.

       
    • inverse_cow

      inverse_cow - 2005-03-30

      Hello,

        Well, I got the 1st system running now.  I ended up having to write an inittab file, and that did the trick.

        If anyone else is having this problem, I found the following link to be helpful:

      http://www.tldp.org/LDP/sag/html/init.html

       
    • Nobody/Anonymous

      Hello,

      I had the same problem in chapter 2/phase 1.
      I solved it by installing the glibc-static-devel package mentioned somewhere on the mailing list
      on my host before compiling bash again.

      Used: bash 3.0
      Kernel 2.4.20
      grub 0.95

      Host: distribution Mandrake 10.1

      Ellen

       
    • Nobody/Anonymous

      I have successfully came out from chapter 2. while implementing  saving space i am facing difficulty and i am getting the following messages.
      warning:unable  to initialise  the initial console
      kernel panic   try passing init =option

      i have checked  my bzImage for elf support  and if  i am facing this problem with ramdisk then give me suggesstions regarding that.
      now i am in a urgent help from everybody !!!!!!!!!!!!!!!!
      help!!!!!!!!!!!

       
    • Nobody/Anonymous

      greetings!

      Chapter 3's implementation failed for me too, lots of times, then i realized that file permissions on those libs aren't okay.

      I use debian testing/unstable as host, with kernel 2.6.12.

      In the Pocket Linux Guide section 3.3.4 i used strip to strip and copy the libraries named by ldd. I didn't keep in mind that those names are the names of symlinks pointing to the shared libraries, respectively..

      So copying with strip resulted in losing the necessary file permissions. After i chmodded them as they are on the host system, everything went fine, I could go forward to Chapter 4.

      You can find it ridiculous, and it can be, it's just my first run.

      Hope could help, best wishes!

       

Log in to post a comment.