public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Vlasov <vsu@altlinux.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 kernels misdetect harddisk geometry, 2.4 kernels are fine
Date: Thu, 1 Apr 2004 19:22:46 +0400	[thread overview]
Message-ID: <20040401192246.00719d71.vsu@altlinux.ru> (raw)
In-Reply-To: 406C2AFB.1030101@gmx.net

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

On Thu, 01 Apr 2004 16:45:15 +0200 Carl-Daniel Hailfinger wrote:

> the harddisk geometry recognized by 2.6 kernels differs from the geometry
> recognized by 2.4 kernels. The 2.4 kernel version agrees with the BIOS and
> fdisk/parted. The 2.6 kernel version seems senseless to me. Here is a diff
> between bootup messages: (more info available if you need it)
[skip]

In fact, this did not work correctly even in 2.4, except in some very
limited circumstances: either hda only, or hda+hdb.  Even hda+hdc
configuration was broken (hda was getting parameters from BIOS, but
hdc was not).

> You can see that both share the same sector count, but differing Megabytes
> and differing CHS. This breaks nearly every partitioning program I know
> and it makes supporting old ATARAID configurations a nightmare. (Some of
> the RAID superblock locations depend on the BIOS idea of CHS.)

Again, this was broken in 2.4.x too, except for the first IDE drive.
Difference in Megabytes is probably due to rounding and should not
matter (this is output only).

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-01 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 14:45 2.6 kernels misdetect harddisk geometry, 2.4 kernels are fine Carl-Daniel Hailfinger
2004-04-01 15:22 ` Sergey Vlasov [this message]
2004-04-01 16:49   ` Jamie Lokier
2004-04-01 22:44 ` Patrick J. LoPresti

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=20040401192246.00719d71.vsu@altlinux.ru \
    --to=vsu@altlinux.ru \
    --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