mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: "Keith Owens" <kaos@ocs.com.au>, <sjhill@cotw.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: LILO error with 2.4.3-pre1...
Date: Sat, 3 Mar 2001 21:27:15 -0500	[thread overview]
Message-ID: <003001c0a452$ac242f60$1601a8c0@zeusinc.com> (raw)
In-Reply-To: <22634.983669972@ocs3.ocs-net>


----- Original Message -----
From: "Keith Owens" <kaos@ocs.com.au>
To: <sjhill@cotw.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, March 03, 2001 8:39 PM
Subject: Re: LILO error with 2.4.3-pre1...


> On Sat, 03 Mar 2001 19:19:28 -0600,
> "Steven J. Hill" <sjhill@cotw.com> wrote:
> >I have no idea why the 1023 limit is coming up considering 2.4.2 and
> >LILO were working just fine together and I have a newer BIOS that has
> >not problems detecting the driver properly. Go ahead, call me idiot :).
>
> OK, you're an idiot :).  It only worked before because all the files
> that lilo used just happened to be below cylinder 1024.  Your partition
> goes past cyl 1024 and your new kernel is using space above 1024.

I would agree with this explanation.

> Find a version of lilo that can cope with cyl >= 1024 (is there one?)

Uh, the version he has can cope with this, see the following:

>    LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
>    'lba32' extensions Copyright (C) 1999,2000 John Coffman

The lba32 extensions should take care of this, of course you have to add
'lba32' as a line in your lilo.conf before lilo actually uses them (and, I
assume, the BIOS must support the LBA extensions, but it seems most modern
ones do).

Give that a try.  Works for me.

Later,
Tom



  reply	other threads:[~2001-03-04  2:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-24 23:25 New net features for added performance Jeff Garzik
2001-02-24 23:48 ` Andi Kleen
2001-02-25  0:03   ` Jeff Garzik
2001-02-25  0:12     ` Andi Kleen
2000-01-01  0:19       ` Pavel Machek
2001-03-04  1:19         ` LILO error with 2.4.3-pre1 Steven J. Hill
2001-03-04  1:39           ` Keith Owens
2001-03-04  2:27             ` Tom Sightler [this message]
2001-03-04 21:32             ` Mircea Damian
2001-03-04 23:05               ` Guest section DW
2001-03-04  2:39           ` Andre Tomt
2001-03-04  3:32             ` Steven J. Hill
2001-03-04 13:35           ` Alan Cox
2001-02-25  0:13     ` New net features for added performance Jeff Garzik
2001-02-25  0:16       ` Andi Kleen
2001-02-25 11:49   ` Rusty Russell
2001-02-25  1:55 ` Michael Richardson
2001-02-25  2:32 ` Jeremy Jackson
2001-02-25  3:23   ` Chris Wedgwood
2001-02-25 12:41     ` Werner Almesberger
2001-02-25 13:57       ` Chris Wedgwood
2001-02-25  2:38 ` Noah Romer
2001-03-03 23:32   ` Jes Sorensen
2001-02-25 12:01 ` Andrew Morton
2001-02-25 15:11   ` Jeremy Jackson
2001-02-25 12:22 ` Werner Almesberger
2001-03-12 15:08   ` Jes Sorensen
2001-02-25 13:08 ` Jonathan Morton
2001-02-26 23:46 ` David S. Miller
2001-02-27  0:07   ` Jeff Garzik
2001-02-27  0:10   ` David S. Miller
2001-02-26 23:48 ` David S. Miller
2001-02-27  0:03   ` Andi Kleen
2001-02-27 19:59     ` kuznet
2001-02-27  0:08   ` David S. Miller
2001-02-27  2:53     ` Jeremy Jackson
2001-03-01 21:06 ` Jes Sorensen

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='003001c0a452$ac242f60$1601a8c0@zeusinc.com' \
    --to=ttsig@tuxyturvy.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sjhill@cotw.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

all inboxes | Powered by JetHome®