From: vda <vda@port.imtp.ilyichevsk.odessa.ua>
To: Bob Poortinga <bobp@savemail.com>, linux-kernel@vger.kernel.org
Subject: Re: Upgrade to 2.4.16 produces "Kernel panic: No init found"
Date: Tue, 11 Dec 2001 11:41:02 -0200 [thread overview]
Message-ID: <01121111410200.01012@manta> (raw)
In-Reply-To: <3C150FD8.290BCBEC@savemail.com>
In-Reply-To: <3C150FD8.290BCBEC@savemail.com>
On Monday 10 December 2001 17:41, Bob Poortinga wrote:
> Hello kernel gurus,
>
> I have searched the list archives and google'd myself silly, but I
> can't seem to find a solution to my problem.
>
> I am trying to update my 2.4.3 kernel (Mandrake 8.0 distro) to 2.4.16.
> I did a 'make oldconfig' with my old .config file and added ext3 kernel
> support in addition to ext2. My root fs is ext2 (as are all my fs).
> The new kernel boots but panics when it tries to mount the root fs.
> Here is the error:
> --------------------------------------------------------------------
> Mounting /proc filesystem
> Creating root device
> Mounting root filesystem
> pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
> Freeing unused kernel memory: 216k freed
> Kernel panic: No init found. Try passing init= option to kernel.
Using initrd I guess?
Please describe your boot process.
Initrd support broke between 2.4.10 and 2.4.12, it does not like romfs and
minix initrds anymore. I have a testcase.
--
vda
next prev parent reply other threads:[~2001-12-11 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 19:41 Upgrade to 2.4.16 produces "Kernel panic: No init found" Bob Poortinga
2001-12-11 13:41 ` vda [this message]
2001-12-11 13:10 ` Joy Almacen
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 16:07 Tyler BIRD
2001-12-11 15:47 ` Joy Almacen
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=01121111410200.01012@manta \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=bobp@savemail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.