public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.33: modular ide breaks lilo ...
Date: Mon, 2 Sep 2002 19:37:48 +0200	[thread overview]
Message-ID: <20020902173748.GA9328@win.tue.nl> (raw)
In-Reply-To: <20020902162707.GA22182@bytesex.org>

On Mon, Sep 02, 2002 at 06:27:07PM +0200, Gerd Knorr wrote:

> I've tried building the ide driver modular and insmod it using an
> initrd.  The kernel boots just fine, but lilo complains:
> 
> bogomips root ~# lilo
> Device 0x0300: Invalid partition table, 2nd entry
>   3D address:     1/0/262 (264096)
>   Linear address: 1/10/4175 (4209030)

What LILO version?
For many versions it will suffice to give LILO the linear or lba32 option.

> I've also noticed that the fdisk output looks different depending on
> modular vs. static ide, I suspect this is related.  With a modular IDE
> driver it looks like this:
> 
> bogomips root ~# fdisk -l /dev/hda
> 
> Disk /dev/hda: 16 heads, 63 sectors, 79780 cylinders
> Units = cylinders of 1008 * 512 bytes
> 
> With ide built-in statically fdisk prints this:
> 
> bogomips root ~# fdisk -l
> 
> Disk /dev/hda: 255 heads, 63 sectors, 5005 cylinders
> Units = cylinders of 16065 * 512 bytes

What fdisk version? Make sure you have a recent one.
Clearly, the rest of the fdisk output is a consequence of the different
geometries. The kernel boot messages will probably tell what happened.
I must still read this part of the kernel source again to see what the
current status is.

Andries


  reply	other threads:[~2002-09-02 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 16:27 2.5.33: modular ide breaks lilo Gerd Knorr
2002-09-02 17:37 ` Andries Brouwer [this message]
2002-09-03 10:08   ` Gerd Knorr

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=20020902173748.GA9328@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=kraxel@bytesex.org \
    --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