From: "Dan Egli" <dan@shortcircuit.dyndns.org>
To: "Stefano Biella" <sbiella@hal9001.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: kernel panic: no init found with 2.5.32
Date: Fri, 30 Aug 2002 13:38:57 -0600 [thread overview]
Message-ID: <001701c2505c$e32ebea0$9600a8c0@yamatto> (raw)
In-Reply-To: 3D6FC85D.67286B32@hal9001.net
What are you passing as the init= arg? What is your boot manager? (Grub?
Lilo? 3rd Party?)
no init means that when the kernel boot sequence tries to spawn off
/sbin/init, it cannot find the file.The fault could be any one of multiple.
It would help in the future if for problems like this you pasted your boot
loader config file.
----- Original Message -----
From: "Stefano Biella" <sbiella@hal9001.net>
To: <linux-kernel@vger.kernel.org>
Sent: Friday, August 30, 2002 1:32 PM
Subject: kernel panic: no init found with 2.5.32
> I have a slackware 8.1 machine that works fine with 2.4.18/19 kernels,
> but,when I reboot with the 2.5.31/32 kernels, the system have a "kernel
> panic: no init found. try passing init= option to kernel" The fs is a
> reisersfs v.3.6 on Intel PIIX4 chipset with udma33 disk.
> The disk is not corrupted because if I back to 2.4.X the machine boot
> fine.
>
> what's wrong?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-08-30 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 19:32 kernel panic: no init found with 2.5.32 Stefano Biella
2002-08-30 19:38 ` Dan Egli [this message]
2002-08-30 19:51 ` Stefano Biella
2002-08-30 20:18 ` Richard B. Johnson
2002-08-30 21:13 ` Stefano Biella
2002-08-31 9:41 ` Stefano Biella
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='001701c2505c$e32ebea0$9600a8c0@yamatto' \
--to=dan@shortcircuit.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sbiella@hal9001.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 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.