From: Andrew Morton <akpm@osdl.org>
To: Christopher Chan <cchan@outblaze.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: linux 2.6.9 controller order reordered. was: [Re: linux 2.6.9 still having network code problems]
Date: Tue, 2 Nov 2004 02:07:12 -0800 [thread overview]
Message-ID: <20041102020712.18218d47.akpm@osdl.org> (raw)
In-Reply-To: <41874D93.9000008@outblaze.com>
Christopher Chan <cchan@outblaze.com> wrote:
>
> 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.
Could you send the dmesg output so we can see the probing activity?
next prev parent reply other threads:[~2004-11-02 9:09 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 ` linux 2.6.9 controller order reordered. was: [Re: linux 2.6.9 still having network code problems] Christopher Chan
2004-11-02 10:07 ` Andrew Morton [this message]
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=20041102020712.18218d47.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cchan@outblaze.com \
--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 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.