Kernel panic (customizing kernel 2.6.6)

From: Marvin Gerardo Aguero Salazar (maguero_at_racsa.co.cr)
Date: 08/15/04

  • Next message: Will Trillich: ""screen" saves life, all in a day's work" 
    Date: Sun, 15 Aug 2004 15:13:39 -0600
To: debian-user@lists.debian.org

    Guys,

    I am trying to customize my kernel 2.6.6 but it fails to boot. I have a
    theory of why it is not booting, but I don't know how to fix it.

    Let's see, I first downloaded and installed kernel-2.6.6-1-386 and
    installed it just fine. I have a directory called /lib/modules/2.6.6-1-386.

    Then I downloaded the kernel source for kernel version "2.6.6", check
    out the difference in the version as compared to "2.6.6-1-386".

    I then issued the following commands:

       make menuconfig
       make
       make modules_install
       make install

    This created a directory called "/lib/modules/2.6.6". So far, so good.

    Then I customized grub's menu.lst to include an option for the new kernel.

    While booting with the new kernel it fails because the directory
    /lib/modules/2.6.6 does not exist.

    My theory is that the problem relies in the file called
    initrd.img-2.6.6-1-386. Since the make process didn't create a
    initrd.img-2.6.6 I kept the same one.

    Last night I realized that this file is a "ram disk" and there is a
    directory called /lib/modules/2.6.6-1-386.

    So, when the kernel says that it doesn't find the directory
    /lib/modules/2.6.6 means that it doesn't find it the ram disk, not in my
    hard drive.

    Am I on the right track here?

    Now, I created a copy of it and mounted it. My idea was to rename the
    directory /lib/modules/2.6.6-1-386 to /lib/modules/3.6.6 in the ram
    disk, but it says that it is a readonly device.

    The mount command clearly displays it as "rw". I mounted it with the "-o
    loop" option.

    I also tried to create a ram drive myself. I tried different sizes. The
    last one I tried was twice in size, but when I was copying everything
    from one ram drive to the other, it was running out of space.

    So, any ideas about how to rename the directory in the ram disk?

    TIA,

    -Marvin 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Will Trillich: ""screen" saves life, all in a day's work"

    Relevant Pages

    • Re: Developing a Device Driver
      ... > be nice to present to users as a file system - the data that is produced ... > This is why I initially thought about a RAM disk type approach, ... Can I get access to the network through a driver? ... > the right term) kernel proxy, that would allow a user mode application to ...
      (microsoft.public.development.device.drivers)
    • Re: Kernel panic: initramfs problem? [SOLVED - mostly]
      ... initrd.img-2.6.18-6-686 is 4899969 bytes in size (generic kernel) ... Following up on the initrd idea.... ... with support for the initial RAM disk enabled. ... If RAM disk support is also included, ...
      (Debian-User)
    • Re: [PATCH 0/6] Sizing zones and holes in an architecture independent manner V9
      ... configurations and successfully built a kernel. ... If it fails on any machine, ... booting with loglevel=8 and the console log should tell me what went wrong. ... Are you intending the hot-add memory code path to call add_active_range or ??? ...
      (Linux-Kernel)
    • Re: Installing Debian on late 2008 MacBook Pro
      ... In case anyone cares, the problem was that the RAM disk was loaded by LILO, but not found by the kernel, so it might be a LILO bug, the starting address is given to the kernel by LILO). ... I'm trying to install Debian on a late 2008 MacBook Pro. ...
      (Debian-User)
    • Linux on RAM
      ... I have the Freescale BSP, based on 2.6.10 kernel, and an evaluation ... I have work with root filesystem on NFS or on Flash ... Default RAM disk size ... Virtual memory file system support ...
      (comp.arch.embedded)
    Loading