Find the answer to your Linux question:
Results 1 to 6 of 6
I had RH9 with kernel 2.4.? and I downloaded the .rpm for the 2.6.1 kernel. I ran it, it ran without any errors but a few module dependency problems, which ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jan 2004
    Location
    Upper Peninsula, Michigan, US
    Posts
    4

    Upgrade to 2.6.0 kernel ext3 problem


    I had RH9 with kernel 2.4.? and I downloaded the .rpm for the 2.6.1 kernel. I ran it, it ran without any errors but a few module dependency problems, which were easily fixed, and then I rebooted. Now, I get this when I try to boot up.

    I have put in bold the lines I think might be important.

    ERROR: /bin/insmod exited abnormally!
    Mounting /proc filesystem
    Creating block devices
    Creating root device
    Mounting root filesystem
    mount: error 19 mounting ext3
    pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
    umount /initrd/proc failed: 2
    Freeing unused kernel memory: 236k freed
    Kernel Panic: No init found. Try passing init= option to kernel.

  2. #2
    Just Joined!
    Join Date
    Jan 2004
    Location
    Upper Peninsula, Michigan, US
    Posts
    4
    Oh, and one other thing that may be of interest. I have only this kernel. When I ran the .rpm, I typed "rpm -Uvh filename.x.x.x.rpm" so I no longer have the original 2.4.x kernel.

  3. #3
    Linux Newbie
    Join Date
    Jan 2004
    Location
    Istanbul,Turkey
    Posts
    151
    i think installing a kernel rpm is useless. You cannot configure it according to your needs.
    Download the source and compile it! (do not forget selecting ext3 support)

  4. #4
    Linux User
    Join Date
    May 2003
    Location
    CA
    Posts
    370
    googling says that the errors you encounter might be due to the fact that linux cannot find an /initrd directory under root...
    also are you sure you have ext3 file systme support in your kernel?

    there was an earlier post in this same section regarding the same problem...you might want to check that out.
    Fixing Unix is better than working with Windows.
    http://nikhilk.homedns.org/projects/index.html

  5. #5
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    The problem is that the device driver doesn't exist, which leads me to believe that you either have a faulty initrd, or your root device is configured incorrectly. Can you post your GRUB config?

  6. #6
    Linux Engineer
    Join Date
    Dec 2002
    Location
    New Zealand
    Posts
    766
    u should be able to create new initrd's with rpm kernels, just run mkinitrd /boot/initrd-2.6.1-0.img 2.6.1-0

    actually, looking a ur error message again, can u post about 2-3 lines before that, ie what caused insmod to fail.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •