From: Bob Wirka <bobwirka@rtcworks.com>
To: linux-mtd@lists.infradead.org
Subject: lilo-22.1 works with 2.4.19 kernel MTD
Date: Sun, 22 Sep 2002 13:23:06 -0500 [thread overview]
Message-ID: <3D8E0A8A.E657084A@rtcworks.com> (raw)
Hello,
I've been trying to use LILO with a Disk on Chip with no success. I've
got a 2.4.19 kernel, and have been trying to use lilo-21.4. When booted
from a kernel on floppy disk, the Disk on Chip was recognized; I could
fdisk, mke2fs, mount, etc., all normally. LILO would not work, however.
I tried the M-Systems lilo with no success (though I have used their
lilo successfully with a 2.2.12 kernel and disk on chip).
A colleague had apparently used lilo-22.1 successfully. I tried it, and
it works. It's available as an rpm (you'll need gfxboot.rpm, also).
You'll find these rpms through 'rpm.bone.net'. Search for 'lilo-22*i386'
with 'SuSE other' checked. Use the new boot.b and chain.b.
There have been a number of posts on this list regarding the use of lilo
with the MTD drivers; I thought some of you might be intereseted.
Best regards,
Bob Wirka
reply other threads:[~2002-09-22 18:23 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=3D8E0A8A.E657084A@rtcworks.com \
--to=bobwirka@rtcworks.com \
--cc=linux-mtd@lists.infradead.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