From: Christopher Chan <cchan@outblaze.com>
To: linux-ide@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: linux 2.6.9 controller order reordered. was: [Re: linux 2.6.9 still having network code problems]
Date: Tue, 02 Nov 2004 17:04:19 +0800 [thread overview]
Message-ID: <41874D93.9000008@outblaze.com> (raw)
In-Reply-To: <20041102014119.1a6096cc.akpm@osdl.org>
Andrew Morton wrote:
> Christopher Chan <cchan@outblaze.com> wrote:
>
>>DOH. the kernel swapped the controller order on me...fstab entries
>> referred to the wrong device names...
>
>
> Eh? That shouldn't happen. Could you please generate a full report of
> this, send it to the appropriate list and cc myself?
>
> Although if that's the 2.6.9 behaviour it's probably a bit late to fix it
> up.
>
Hardware: Tyan mb with Serverworks chipset and onboard Promise controller.
The two disks on promise channel since Serverworks does not support ATA100
FC2 Installation will recognise the disks as hde and hdg
fstab is accordingly setup as so for swap (everything else are md)
Changing to a 2.6.9 kernel that has the promise driver compiled in will
change the disks to hda and hdc.
next parent reply other threads:[~2004-11-02 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <418741EB.3080701@outblaze.com>
[not found] ` <20041102011918.2b453e21.akpm@osdl.org>
[not found] ` <4187478A.1040002@outblaze.com>
[not found] ` <20041102014119.1a6096cc.akpm@osdl.org>
2004-11-02 9:04 ` Christopher Chan [this message]
2004-11-02 10:07 ` linux 2.6.9 controller order reordered. was: [Re: linux 2.6.9 still having network code problems] Andrew Morton
2004-11-02 9:21 ` Christopher Chan
2004-11-02 10:26 ` Andrew Morton
2004-11-02 16:40 ` Alan Cox
2004-11-03 6:57 ` Christopher Chan
2004-11-03 13:00 ` Bartlomiej Zolnierkiewicz
2004-11-03 15:51 ` Christopher Chan
2004-11-03 17:01 ` Bartlomiej Zolnierkiewicz
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=41874D93.9000008@outblaze.com \
--to=cchan@outblaze.com \
--cc=akpm@osdl.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).