public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Patrick J. LoPresti" <patl@users.sourceforge.net>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.x partition breakage and dual booting
Date: 30 May 2004 15:35:12 -0400	[thread overview]
Message-ID: <s5gwu2tlo97.fsf@patl=users.sf.net> (raw)
In-Reply-To: <40BA2213.1090209@pobox.com>

Jeff Garzik <jgarzik@pobox.com> writes:

> So it seems that the 2.6.x geometry code breaks dual booting, since
> Windows wants "sane" CHS values.  See the thread on slashdot, or
> http://www.redhat.com/archives/fedora-devel-list/2004-May/msg00908.html
> 
> Although Fedora Core is current taking grief for this, it's really a
> 2.6.x kernel problem AFAICT.
> 
> Has anybody taken the time to hunt down the csets that cause this
> massive partition table breakage?  If so, it will save me some time
> tracking this down.

Here are my contributions to the discussion:

    http://groups.google.com/groups?selm=1xXh2-850-17%40gated-at.bofh.it

    http://groups.google.com/groups?selm=1Gjko-6Y1-5%40gated-at.bofh.it

    http://groups.google.com/groups?selm=1Gju8-7bd-29%40gated-at.bofh.it

In short, starting with kernel 2.6.5, Linux invokes the real-mode
"legacy INT13" interface (INT13/AH=08) at boot time and stashes the
results away.  The EDD module exports them via sysfs.

Userspace can read these values and issue a command to
/proc/ide/hda/settings to "fix" the kernel's concept of the geometry
before running partitioning tools.

Because the legacy geometry is purely a BIOS concept, there is no way
to obtain it by talking to the disk directly.  (Sure, there may be
hints in the existing partition table.  I believe 2.4.x would use such
hints.  But this is unreliable, since it does not work if the disk is
blank or if it has been moved from a different machine.)

The reason to do this work in userspace is that there is no certain
way to map between BIOS disk numbers (80h etc.) and Linux devices.
You can make a pretty good guess, but such guessing probably does not
belong in the kernel.

I first encountered this problem while trying to install Windows using
Linux.  I contributed the "legacy geometry" support to the EDD module
specifically to deal with this issue, and it is working fine for me.

 - Pat
   http://unattended.sourceforge.net/

      parent reply	other threads:[~2004-05-30 19:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30 18:04 2.6.x partition breakage and dual booting Jeff Garzik
2004-05-30 18:36 ` Andries Brouwer
2004-05-30 18:56   ` Jeff Garzik
2004-05-30 20:03     ` Andries Brouwer
2004-05-30 20:47       ` viro
2004-05-30 21:06         ` Andries Brouwer
2004-05-30 21:08         ` Andreas Schwab
2004-05-30 21:14           ` viro
2004-05-30 21:02       ` Patrick J. LoPresti
2004-05-30 22:20         ` Andries Brouwer
     [not found]           ` <mit.lcs.mail.linux-kernel/20040530222001.GD4681@apps.cwi.nl>
2004-05-30 22:54             ` Patrick J. LoPresti
2004-05-31 18:08         ` Tomas Szepe
2004-05-31 19:19           ` Frediano Ziglio
2004-05-31 20:06           ` Patrick J. LoPresti
2004-05-31 21:03             ` Sean Estabrooks
2004-06-01 15:10               ` Patrick J. LoPresti
2004-06-01 23:55                 ` Andries Brouwer
2004-06-02 13:02                   ` Patrick J. LoPresti
2004-06-02 15:00                     ` Matt Domsch
2004-06-02 21:22                       ` [PATCH] Better names for EDD legacy_* fields Patrick J. LoPresti
2004-06-02 23:03                         ` Andries Brouwer
2004-06-02 23:38                           ` Patrick J. LoPresti
2004-06-02 23:53                       ` [PATCH] Use decimal instead of hex for EDD values Patrick J. LoPresti
2004-06-01 16:28           ` 2.6.x partition breakage and dual booting Stephen Hemminger
2004-06-03  6:51           ` Frediano Ziglio
2004-06-03 10:39             ` Andries Brouwer
2004-06-03 12:30               ` Frediano Ziglio
2004-06-03 14:35                 ` Bartlomiej Zolnierkiewicz
2004-06-03 15:11                   ` Andries Brouwer
2004-06-03 14:46               ` Patrick J. LoPresti
2004-06-03 15:32                 ` Bartlomiej Zolnierkiewicz
2004-06-03 15:55                   ` Patrick J. LoPresti
2004-05-30 19:35 ` Patrick J. LoPresti [this message]

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='s5gwu2tlo97.fsf@patl=users.sf.net' \
    --to=patl@users.sourceforge.net \
    --cc=jgarzik@pobox.com \
    --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