mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Flavio Bruno Leitner <fbl@conectiva.com.br>,
	<linux-kernel@vger.kernel.org>
Subject: Re: IDE disk information changed from 2.4 to 2.6
Date: Tue, 11 Nov 2003 19:29:08 +0100	[thread overview]
Message-ID: <200311111929.08487.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20031111115316.GB16163@win.tue.nl>

On Tuesday 11 of November 2003 12:53, Andries Brouwer wrote:
> On Wed, Nov 05, 2003 at 08:41:58PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > In 2.6.x it doesn't even read BIOS info (which is wrong IMO, it should
> > do this but only as last resort - if partition can't be mounted).
>
> How can reading information that is not used by any kernel
> help in mounting a partition?

You are of course right, only ibm.c and nec98.c use HDIO_GETGEO.

> > Difference in CHS translation should matter only if you have some old DOS
> > partitions created using CHS information.  Then you can force geometry
> > using boot parameter "hd?=".  Unfortunately I've seen recently bugreport
> > when 2.4.20 (?) works and 2.6.x fails even with forced geometry.
>
> Fails? What do you mean?

Sorry, it was "hd.c instead of ide.c" problem.

> (Are you referring to the problem of finding the last cylinder?)


  reply	other threads:[~2003-11-11 18:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031105184203.GG5304@conectiva.com.br>
2003-11-05 19:41 ` Bartlomiej Zolnierkiewicz
2003-11-11 11:53   ` Andries Brouwer
2003-11-11 18:29     ` Bartlomiej Zolnierkiewicz [this message]
2003-11-05 17:23 Flavio Bruno Leitner
2003-11-05 17:29 ` Bartlomiej Zolnierkiewicz
2003-11-05 17:57   ` Flavio Bruno Leitner
2003-11-11 11:46 ` Andries Brouwer
2003-11-11 12:13   ` Flavio Bruno Leitner
2003-11-11 16:21   ` bill davidsen

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=200311111929.08487.bzolnier@elka.pw.edu.pl \
    --to=b.zolnierkiewicz@elka.pw.edu.pl \
    --cc=aebr@win.tue.nl \
    --cc=fbl@conectiva.com.br \
    --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

all inboxes | Powered by JetHome®