From: "Jon Hedlund" <JH_ML@invtools.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4 bootdisk kernel panic
Date: Thu, 30 May 2002 20:11:16 -0500 [thread overview]
Message-ID: <3CF68764.12104.BBA8F3A@localhost> (raw)
I have been trying to update a 1.44 floppy based linux system to a
2.4.18 kernel from 2.4.4. However whenever I try to boot the
updated floppy I get the following kernel panic:
RAMDISK: Compressed image found at block 501
VFS: Mounted root (ext2 filesystem)
Freeing unused kernel memory: 64K freed
Kernel panic: no init found. Try passing init= option to the kernel.
I have tried it with a bunch of kernels, 2.4.4, 2.4.7 and 2.4.9 boot
fine, 2.4.12, 2.4.13, 2.4.17, and 2.4.18 all give the panic.
I create the bootdisk with the following script:
rdev bzImage /dev/fd0
rdev -R bzImage 0
rdev -r bzImage 16885
# 16885= Don't prompt, Load ramdisk, offset = 501
dd if=bzImage of=tempfi bs=1k conv=sync
cat rootfs.gz >> tempfi
dd if=tempfi of=/dev/fd0 bs=1k
I manually edit the 16885 for whatever the size of the kernel is, just
over 500KB in this case.
The kernel doesn't use loadable modules.
Modules are compiled into the kernel for the tulip network card,
iptables, ext2, floppy drive, etc. I can post my config file if more info
is needed.
JonH
reply other threads:[~2002-05-31 1:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CF68764.12104.BBA8F3A@localhost \
--to=jh_ml@invtools.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox