From: "Gregg Lloyd" <gregg_99@lycos.com>
To: linux-kernel@vger.kernel.org
Subject: LILO wont boot my kernel image: More details...
Date: Mon, 22 Jan 2001 23:52:24 -0500 [thread overview]
Message-ID: <PFMKNGGAANDBKAAA@mailcity.com> (raw)
Hi,
I have a 2.2.5-15 kernel linux system (red Hat 6.0) that is installed on /dev/hdc2. I boot it from a floppy.
Recently, I did compile my new kernel 2.4 on my Linux System.
On the boot floppy, I have LILO (On the hard drive, there's also LILO).
For booting my new kernel (/boot/vmlinuz-2.4.0), I added following stanza to /etc/lilo.conf (the one on the hard drive):
image=/boot/vmlinuz-2.4.0
label=linux2.4
root=/dev/hdc2
read-only.
Lilo was correctly saved (/sbin/lilo..or lilo would display "Added linux2.2 *
Added linux2.4, Added dos).
But when I rebooted the system
with the boot floppy, LILO wont display linux2.4 so that I can boot with it!
LILO would only show up the old linux.
I went adding the same stanza (as previously mentionned) to /etc/lilo.conf
that is on the floppy. But the problem is still the same: I do not have the choice to boot with linux2.4!
I tried "lilo -b /dev/fd0" (after /dev/fd0
have been correctly mounted), but system
weirdly complained that "open /boot/message: No such file or directory" (which is wrong!).
I got same error message when trying "lilo -C /mnt/floppy/etc/lilo.conf"!
******Here is my /etc/lilo.conf on hard drive*********
boot=/dev/hdc2
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz-2.2.5-15
label=linux2.2
root=/dev/hdc2
read-only
image=/boot/vmlinuz-2.4.0
label=linux2.4
root=/dev/hdc2
read-only
other=/dev/hda1
label=dos
table=/dev/hda
*******Here's lilo.conf on boot floppy*****
boot=/dev/fd0
timeout=100
message=/boot/message
prompt
image=/vmlinuz-2.2.5-15
label=linux2.2
root=/dev/hdc2
image=/vmlinuz-2.2.5-15
label=rescue
append="load_ramdisk=2 prompt_ramdisk=1"
root=/dev/fd0
image=/vmlinuz-2.4.0
label=linux2.4
root=/dev/hdc2
other=/dev/hda1
label=dos
table=/dev/hda
Get your small business started at Lycos Small Business at http://www.lycos.com/business/mail.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-23 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 4:52 Gregg Lloyd [this message]
2001-01-23 5:40 ` Probably Off-topic Question Alan Olsen
2001-01-23 20:32 ` Adam Fritzler
2001-01-24 17:14 ` Steve Underwood
2001-01-24 17:30 ` Mark Smith
2001-01-24 19:40 ` Steven Ellmore
2001-01-24 22:38 ` Mark Smith
2001-01-24 22:51 ` alex
2001-01-24 23:04 ` mirabilos
2001-01-25 1:26 ` Alan Cox
2001-01-25 2:22 ` Steve Underwood
2001-01-25 3:04 ` Alan Cox
2001-01-25 18:36 ` Thunder from the hill
2001-01-27 0:38 ` [OT] Vaio Brightness [WAS: Probably Off-topic Question...] Drew Bertola
[not found] ` <20010125155809.26969@winksmith.com>
[not found] ` <3A71BB9D.9B0BAA5C@ngforever.de>
[not found] ` <20010126223246.34429@winksmith.com>
2001-01-27 23:17 ` Probably Off-topic Question Thunder from the hill
2001-01-25 18:26 ` Thunder from the hill
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=PFMKNGGAANDBKAAA@mailcity.com \
--to=gregg_99@lycos.com \
--cc=gregg_99@mailcity.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