From: Ken Zalewski <kennyz@nycap.rr.com>
To: linux-kernel@vger.kernel.org
Cc: kennyz@nycap.rr.com, zalewski@docdev.com
Subject: linux kernel 2.4.10 possibly breaks LILO
Date: Wed, 26 Sep 2001 23:48:45 -0400 [thread overview]
Message-ID: <3BB2A19D.1FB6D91A@nycap.rr.com> (raw)
Summary:
Modifying /etc/lilo.conf and running "lilo" when using kernel version
2.4.10 does not appear to modify the boot sector accordingly, even
though I receive no errors or warnings. On next reboot, LILO is
configured as it was previous to my changes. I am therefore unable to
modify LILO configuration in any way while using 2.4.10.
Machine summary:
AMD Athlon 1 GHz
VIA 686b southbridge
512 MB PC133 SDRAM
/dev/hda = 30 GB Western Digital ATA-100 drive
/dev/hda1 is root partition and active partition
Linux 2.4.10
LILO 21.7-5
Details:
I recently built the latest 2.4.10 kernel from source and installed it
(upgraded from 2.4.7). Ran "lilo", and the new image booted and I was
happily running 2.4.10. I then made some changes to /etc/lilo.conf,
re-ran "lilo", and rebooted. On reboot, the my changes were not
apparent, and the previous configuration was used.
I began experimenting more, making drastic changes to /etc/lilo.conf.
No matter what I did to lilo.conf (even changing from "linear" to
"lba32" and back), running "lilo" produced no change to the startup.
I used a floppy to boot into 2.4.7, ran "lilo", rebooted, and noticed
that my changes had registered.
I then built kernel version 2.4.9, and did the same experiment. My
change to /etc/lilo.conf registered fine on the next reboot.
As a result, I have concluded that something has changed between 2.4.9
and 2.4.10 that causes LILO to be unable to overwrite the boot sector of
the active partition. I also tried using LILO 22.0-beta, and the
problem persisted.
My kernel configurations for both 2.4.9 and 2.4.10 are almost identical.
I do not know if this is something specific to my own machine, but it is
consistently reproducible. I have used versions 2.4.5, 2.4.7, 2.4.9,
and 2.4.10, and LILO fails to work ONLY on 2.4.10. No errors are
printed by LILO, and doing "lilo -q -v" before rebooting seems to
indicate that everything happened properly (though I think that only
reads the map file, not the actual boot sector).
I would appreciate a response regarding this issue. I have not seen
anything posted about this yet, so it could be something specific to my
machine - it's just strange that it just started happening on 2.4.10.
Thanks for any assistance you can provide.
--
Ken Zalewski -- Director of Information Technology
Document Development Corporation
1223 Peoples Avenue, Troy, NY 12180
kennyz@nycap.rr.com http://www.cs.rpi.edu/~kennyz/
next reply other threads:[~2001-09-27 3:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 3:48 Ken Zalewski [this message]
2001-09-27 5:01 ` linux kernel 2.4.10 possibly breaks LILO Andreas Dilger
2001-09-27 5:10 ` Steve Kieu
2001-10-02 17:54 Rui Ribeiro
2001-10-02 18:10 ` Petr Titera
2001-10-02 19:09 ` Andreas Dilger
2001-10-02 17:55 Petr Titera
2001-10-02 23:55 ` David Ford
2001-10-02 23:45 ` Jonathan Walther
2001-10-03 14:36 ` Dave Cinege
2001-10-03 20:46 ` Petr Titera
2001-10-02 18:03 Rui Ribeiro
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=3BB2A19D.1FB6D91A@nycap.rr.com \
--to=kennyz@nycap.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zalewski@docdev.com \
/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;
as well as URLs for NNTP newsgroup(s).