mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>, martin@dalecki.de
Subject: Re: [PATCH] 2.5.30 IDE 112
Date: Tue, 6 Aug 2002 16:10:42 +0200	[thread overview]
Message-ID: <20020806141042.GA29807@win.tue.nl> (raw)
In-Reply-To: <13C83160220@vcnet.vc.cvut.cz>

On Tue, Aug 06, 2002 at 02:19:29PM +0200, Petr Vandrovec wrote:

> FYI I had to use hda=cyls,255,63 to repartition my HDD.

(Or set H=255 S=63 in *fdisk.)

> BIOS refused to report proper size (120GB) when partition table
> was empty, or when it contained partitions created for xxx/16/63
> geometry. It reported size ~600MB, and actively refused to allow
> access above this limit...

Funny. Do you mean that your BIOS used SETMAX ?

> please talk to [cs]fdisk maintainer (and other) to print big fat
> warning and to allow specify BIOS heads/sectors, otherwise partitioning
> of empty disk in the way compatible with non-Linux OSes (Netware, Windows)
> is not an easy task.

Yes. I already advised this maintainer to add -C,-H,-S options to fdisk
(cfdisk and sfdisk already have them), and he did so immediately.
Visible one of these weeks in util-linux-2.11v.

> # lilo
> Warning: Int 0x13 function 8 and function 0x48 return different
> head/sector geometries for BIOS drive 0x81
>     fn 08: 788 cylinders, 255 heads, 63 sectors
>     fn 48: 13424 cylinders, 15 heads, 63 sectors
> Warning: Kernel & BIOS return differing head/sector geometries for device 0x80
>     Kernel: 35973 cylinders, 16 heads, 63 sectors
>       BIOS: 1023 cylinders, 255 heads, 63 sectors

Since geometry does not exist, it is not surprising that everybody
invents something else. Not only do kernel and BIOS differ, but
BIOS is not consistent internally.

For a while, with disk sizes between 500 MB and 8 GB, maximum DOS-accessible
capacity was obtained by H=255 S=63. But IDE accepts at most 16 heads, so
H=255 requires a translating BIOS. For sizes above 8 GB the translation
is useless and will only take some small amount of time.
Setting the disk to Normal (instead of Large / LBA / Extended or so)
works best.

So, I have two questions:
1. What precisely do you mean with "actively refused" ?
2. Is there a Windows or Netware reason to prefer extended translation
above no translation?

Andries

  parent reply	other threads:[~2002-08-06 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 12:19 Petr Vandrovec
2002-08-06 12:23 ` Marcin Dalecki
2002-08-06 18:17   ` Andre Hedrick
2002-08-06 14:10 ` Andries Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-06 16:06 Petr Vandrovec
2002-08-06  8:50 Marcin Dalecki
2002-08-06 10:27 ` Andries Brouwer
2002-08-06 19:22 ` Linus Torvalds

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=20020806141042.GA29807@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    /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®