From: Chuck Gelm <nc8q@gelm.net>
To: linux-newbie@vger.kernel.org
Subject: Re: LI -lilo booting problem
Date: Fri, 26 Jul 2002 17:19:55 -0400 [thread overview]
Message-ID: <3D41BCFB.390F2750@gelm.net> (raw)
In-Reply-To: 02072606105100.00370@unix.pa3gcu
Hi, Ray, Richard, & Ramzez:
I use
/usr/src/linux/# make install
and
# lilo
(/sbin/lilo ?) to try to install a bootable system.
Thanks. I found the mention of adding lba32
to lilo.conf, although README.common.problems
does NOT show the syntax of the line. :-|
However, I'll plug 'lba32' & 'lilo' into google
or whatever and see if I can find an example.
I can install Slackware8.0, compile a new kernel,
and boot from floppies, either lilo or bzdisk,
yet I cannot boot from either of two hard drives.
:-|
Here is the partition structure of the last two
HDs that I've tried to boot.
Device Boot Start End Blocks Id System
/dev/hda1 * 1 240 1927768 83 Linux system
/dev/hda2 241 256 128520 82 Linux swap
/dev/hda3 257 2491 179526378 83 Linux system
I tried this one in Primary master also:
Device Boot Start End Blocks Id System
/dev/hda1 * 1 128 1028128 83 Linux system
/dev/hda2 129 131 24097 82 Linux swap
/dev/hda3 132 1048 7365802 83 Linux system
In all cases(2) system was:
(1) /dev/hda1 mounted as /
/dev/hda3 mounted as /usr
(2) /dev/hda1 mounted as /
/dev/hda3 mounted as /share
So, / (/boot) was always within the first 1024 cylinders.
:-|
I'm off to find "lba32".
Thanks again, Chuck
pa3gcu wrote:
>
> On Thursday 25 July 2002 21:20, Chuck Gelm wrote:
> > Howdy, Y'all:
> >
> > Where can I find help with 'lilo'.
>
> /usr/doc/lilo-21.7.5 (slackware-8.0)
>
> > When I try to boot from hard disk, I get:
> >
> > LI
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2002-07-26 21:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 15:24 Question about "find -exec" Oliver Ob
2002-07-19 5:52 ` James Mohr
2002-07-24 7:07 ` Mike Castle
2002-07-24 16:07 ` James Mohr
2002-07-24 21:24 ` Partitioning problem Anshuman Rawat
2002-07-25 6:22 ` pa3gcu
2002-07-25 21:20 ` LI -lilo booting problem Chuck Gelm
2002-07-26 1:38 ` No Boot Problem Frank Roberts - SOTL
2002-07-26 3:53 ` Ray Olszewski
2002-07-26 12:44 ` Frank Roberts - SOTL
2002-07-26 16:57 ` Ray Olszewski
2002-07-27 1:23 ` Frank Roberts - SOTL
2002-07-26 20:28 ` Chuck Gelm
2002-07-26 6:10 ` LI -lilo booting problem pa3gcu
2002-07-26 21:19 ` Chuck Gelm [this message]
2002-07-27 8:08 ` pa3gcu
2002-07-26 21:21 ` Chuck Gelm
2002-07-26 23:57 ` Ray Olszewski
[not found] ` <3D444FC2.354744E5@gelm.net>
2002-07-28 21:15 ` Ray Olszewski
2002-07-29 1:21 ` Chuck Gelm
2002-07-29 21:01 ` Chuck Gelm
2002-07-29 23:11 ` Frank Roberts - SOTL
2002-08-02 10:07 ` ntp - how? Chuck Gelm
2002-08-02 15:31 ` pa3gcu
2002-08-02 16:36 ` Ray Olszewski
2002-08-02 20:28 ` Chuck Gelm
2002-08-02 21:42 ` Ray Olszewski
2002-08-02 22:25 ` Chuck Gelm
2002-07-26 6:28 ` LI -lilo booting problem Ray Olszewski
2002-07-26 17:04 ` ichi
2002-07-26 8:26 ` Ramzez
2002-07-19 9:16 ` Question about "find -exec" szonyi calin
-- strict thread matches above, loose matches on Subject: below --
2002-07-30 20:55 LI -lilo booting problem Jay Maass
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=3D41BCFB.390F2750@gelm.net \
--to=nc8q@gelm.net \
--cc=linux-newbie@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