From: Vojtech Pavlik <vojtech@suse.cz>
To: raptor <raptor@antifork.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible bug in hd geometry detect code?
Date: Wed, 1 Nov 2000 17:36:32 +0100 [thread overview]
Message-ID: <20001101173632.A387@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.20.0011011436350.516-100000@hacaro.rewt.mil>
In-Reply-To: <Pine.LNX.4.20.0011011436350.516-100000@hacaro.rewt.mil>; from raptor@antifork.org on Wed, Nov 01, 2000 at 02:37:00PM +0100
On Wed, Nov 01, 2000 at 02:37:00PM +0100, raptor wrote:
> Hello,
> I've recently experienced a problem with hd geometry on Linux kernel
> 2.2.17. I've got 2 identical hard drives, set up as LBA on BIOS. BIOS sees
> them both with geometry 1245/255/63, while Linux sees the second one as
> 19857/16/63. I know i can force the kernel to recognize the right geometry
> using lilo's append=... feature, but I cannot realize why this is
> happening. I've tested it ONLY on Asus motherboards (p2bf and p2b with
> latest BIOS version), so maybe this can be a simple hardware problem...
> Anyway here's a snip from the dmesg:
>
> hda: FUJITSU MPF3102AH, ATA DISK drive
> hdc: FUJITSU MPF3102AH, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: FUJITSU MPF3102AH, 9773MB w/2048kB Cache, CHS=1245/255/63, UDMA
> hdc: FUJITSU MPF3102AH, 9773MB w/2048kB Cache, CHS=19857/16/63, UDMA
>
> Now the OS version:
> seti:~# cat /proc/version
> Linux version 2.2.17 (root@seti) (gcc version 2.95.2 20000220 (Debian
> GNU/Linux)) #2 Fri Oct 20
>
> If I switch the 2 hard disks the one put on the secondary IDE channel has
> CHS=19857/16/63, no matter which one is, while the first one remains with
> 1245/255/63.
> Let me know...
This is because BIOS only provides info about how it sees the first two
drives (hda and hdb). For hdc and subsequent drives, without the help of
a command line option Linux only can use the untranslated geometry.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-01 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 13:37 possible bug in hd geometry detect code? raptor
2000-11-01 15:42 ` Andre Hedrick
2000-11-01 16:36 ` Vojtech Pavlik [this message]
2000-11-02 0:12 ` Andries Brouwer
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=20001101173632.A387@suse.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=raptor@antifork.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.