From: Samuel Flory <sflory@rackable.com>
To: Bruce Lowekamp <lowekamp@CS.WM.EDU>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-pre8 swaps ide controller order on A7V266-E
Date: Wed, 02 Oct 2002 13:48:15 -0700 [thread overview]
Message-ID: <3D9B5B8F.1060409@rackable.com> (raw)
In-Reply-To: 15570000.1033586626@chorus.cs.wm.edu
Bruce Lowekamp wrote:
>
> Starting with 2.4.19 and continuing in 2.4.20-pre8, the order the
> kernel associates with the two IDE controllers (one VIA vt8233 and one
> PDC20265 intended for RAID use) on the A7V266-E has been reversed.
> The BIOS and GRUB consider the VIA to be first, so root(hd0,0) loads
> the kernel from the first device on the VIA controller. Prior to
> 2.4.19, the OS then booted with that drive identified as hda.
> Beginning with 2.4.19, however, the kernel instead identifies the PDC
> as ide0 and ide1, and puts the VIA at ide2 and ide3, resulting in the
> boot drive being hde.
>
> I found an earlier mention of this on the mailing list, but no
> solution or workaround was suggested. We are using a workaround where
> 2.4.19 and later kernels are booted with root=/dev/hde1 and earlier
> with hda1, and fstab lists both hda2 and hde2 as swap partitions,
> simply failing to insert one. This works, but the general ugliness and
> maintenance headaches since this is different than the typical machine
> config we use around here make it difficult to use in the long run.
>
> I'm not sure what the process of identifying order of controllers
> involves, but the discrepancy between the BIOS, older kernels, and
> newer kernels seems like something that should be fixed if possible.
I'm not sure what the kernel issue is, but there is a simple work
around. Enable CONFIG_BLK_DEV_OFFBOARD (aka boot off-board chipsets
first) in the ide section. You can also produce the same effect via
ide=reverse on the kernel command line (or an append statement in lilo).
This will reverse the order in which the chipsets are seen.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2002-10-02 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 19:23 2.4.20-pre8 swaps ide controller order on A7V266-E Bruce Lowekamp
2002-10-02 20:48 ` Samuel Flory [this message]
2002-10-08 2:30 ` Nick Orlov
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 12:24 David Balazic
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=3D9B5B8F.1060409@rackable.com \
--to=sflory@rackable.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lowekamp@CS.WM.EDU \
/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