From: Marcin Dalecki <dalecki@evision.ag>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: mingo@elte.hu, alan@lxorguk.ukuu.org.uk, Andries.Brouwer@cwi.nl,
johninsd@san.rr.com, linux-kernel@vger.kernel.org
Subject: Re: [bug, 2.5.29, IDE] partition table corruption?
Date: Thu, 08 Aug 2002 11:24:10 +0200 [thread overview]
Message-ID: <3D5238BA.7070307@evision.ag> (raw)
In-Reply-To: 200208080908.CAA10230@adam.yggdrasil.com
Użytkownik Adam J. Richter napisał:
>
> | The head/sector mismatch check (fn 8h/fn 48h) has actually been in LILO
> | since last year (22.0), and the (kernel/bios) check since 22.2. It has
> | only been seriously visible since the introduction of the 2.4.18 kernel.
> | The IDE disk drivers are now reporting actual IDE disk geometry, rather
> | than the mapped BIOS geometry, which was reported by all previous kernels.
> | This change in the results returned by the IOCTL used to get the disk
> | geometry has been extremely annoying. It also leads to complaints about
> | the format of the partition table.
>
> Earlier in that seem email, he indicated that he was
> thinking about giving precedence to the BIOS geometry in future
> versions of lilo (this was 22.3, and I believe the current version is
> now 22.3.1):
How did he think DOS does disk access during dos fdisk time before?
As far as I can see lilo is relying on the BIOS during the "dot printing
phase" anyway so this should have been this way since day one of lilo.
*Not* the other way around.
> | Actually, on serious reflection on the issue, there is no choice: the
> | value returned by (int 13h/fn 8h) should be used, if it is available. This
> | is the value used by the conversion routine (linear/lba32 -> geometric) in
> | the boot loader (read.S). Currently, the kernel value is given precedence;
> | I am seriously reviewing this issue.
>
> I just wonder if this is the problem that you are experiencing
> rather than anything that was new in 2.5.29.
Yes.
next prev parent reply other threads:[~2002-08-08 9:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 9:08 [bug, 2.5.29, IDE] partition table corruption? Adam J. Richter
2002-08-08 9:24 ` Marcin Dalecki [this message]
2002-08-08 9:31 ` Ingo Molnar
2002-08-08 9:34 ` Marcin Dalecki
2002-08-08 10:01 ` Ingo Molnar
2002-08-08 11:45 ` Andries Brouwer
2002-08-08 12:30 ` Alan Cox
2002-08-08 11:22 ` Marcin Dalecki
2002-08-08 13:23 ` Alan Cox
2002-08-08 12:18 ` Marcin Dalecki
2002-08-08 18:11 ` Alan Cox
2002-08-09 0:11 ` Thunder from the hill
2002-08-09 6:27 ` Marcin Dalecki
[not found] ` <3D523B25.5 <20020808181100Z315277-685+26763@vger.kernel.org>
2002-08-09 6:25 ` Marcin Dalecki
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:22 Andries.Brouwer
2002-08-08 22:36 ` John Coffman
2002-08-09 6:06 ` H. Peter Anvin
2002-08-08 12:29 Andries.Brouwer
2002-08-07 18:43 Andries.Brouwer
2002-08-08 7:46 ` Marcin Dalecki
2002-08-06 22:27 Andries.Brouwer
2002-08-07 17:46 ` Ingo Molnar
2002-08-07 17:51 ` Ingo Molnar
2002-08-01 13:45 Ingo Molnar
2002-08-01 13:48 ` Marcin Dalecki
2002-08-01 16:16 ` Alan Cox
2002-08-01 15:02 ` Marcin Dalecki
2002-08-01 15:12 ` Alan Cox
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=3D5238BA.7070307@evision.ag \
--to=dalecki@evision.ag \
--cc=Andries.Brouwer@cwi.nl \
--cc=adam@yggdrasil.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=johninsd@san.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=mingo@elte.hu \
/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