public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Joy Almacen <joy@empexis.com>,
	wa@almesberger.net, linux-kernel@vger.kernel.org
Cc: "Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: pivot_root and initrd kernel panic woes
Date: Thu, 13 Dec 2001 08:09:59 -0200	[thread overview]
Message-ID: <01121308095901.01849@manta> (raw)
In-Reply-To: <3C165586.457A26F0@empexis.com>
In-Reply-To: <3C165586.457A26F0@empexis.com>

Boy, what a detailed report!

I never used lilo, but:

> After which I added this line  my  /etc/lilo.conf file:
>
> image=/boot/vmlinuz-2.4.9-12smp
>         label=2.4.9smp
>         append="initrd=/boot/initrd-2.4.9-12smp.img root=/dev/ram0
> init=/linuxrc rw"
>
> Reran lilo
>
> [root@tinkerbell /root]# lilo -v
>
> LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
> 'lba32' extensions Copyright (C) 1999,2000 John Coffman
>
> Reading boot sector from /dev/sda
> Merging with /boot/boot.b
> Mapping message file /boot/message
> Boot image: /boot/vmlinuz-2.4.2-2smp
> Mapping RAM disk /boot/initrd-2.4.2-2smp.img
> Added linux
> Boot image: /boot/vmlinuz-2.4.2-2
> Mapping RAM disk /boot/initrd-2.4.2-2.img
> Added linux-up *
> Boot image: /boot/vmlinuz-2.4.9-12smp    ## Entry for SMP kernel
> Added 2.4.9smp
> Boot image: /boot/vmlinuz-2.4.9-12-smp-4th
> Added custom
> /boot/boot.0800 exists - no backup copy made.
> Writing boot sector.

"Mapping RAM disk" seems to be missing for 2.4.9-12, so you'll get:

> "VFS: Cannot open root device "ram0" or 01:00
> Please append a correct "root=" boot option
> Kernel panic: VFS:  unable to mount root fs on 01:00 "

Check your lilo conf. Include it in your reply.

BTW, don't go for 2.4x, x>10. initrd is broken there and is still unfixed.
--
vda

  parent reply	other threads:[~2001-12-13  8:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 18:50 pivot_root and initrd kernel panic woes Joy Almacen
2001-12-11 21:00 ` Marcel J.E. Mol
2001-12-13 10:09 ` vda [this message]
2001-12-13  8:19   ` Alexander Viro
2001-12-13 13:22     ` vda
2001-12-13 14:53       ` vda
2001-12-15 12:14       ` Mike Galbraith
2001-12-15 16:51         ` vda
2001-12-15 17:59           ` Mike Galbraith
2001-12-16  2:32             ` vda
2001-12-16  9:02               ` Mike Galbraith
2001-12-15 16:55         ` vda
2001-12-15 18:03           ` Mike Galbraith
2001-12-13 19:07 ` Stephen C. Tweedie
2001-12-13 18:35   ` Joy Almacen
  -- strict thread matches above, loose matches on Subject: below --
2001-12-17 18:38 Torrey Hoffman
2001-12-17 18:44 ` Alexander Viro
2001-12-17 19:02 ` Erik Andersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01121308095901.01849@manta \
    --to=vda@port.imtp.ilyichevsk.odessa.ua \
    --cc=joy@empexis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=wa@almesberger.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox