From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problems booting PDC20276 with new IDE setup code.
Date: Mon, 07 Apr 2003 16:28:35 +0200 [thread overview]
Message-ID: <3E918B13.4080805@gmx.net> (raw)
In-Reply-To: <5.2.0.9.0.20030407141330.00b346c0@mailhost.ivimey.org>
Ruth Ivimey-Cook wrote:
> At 03:34 07/04/2003, Carl-Daniel Hailfinger wrote:
>
>> Could you please try 2.4.21-pre7 (this has another batch of IDE
>> updates) and enable the option
>> "Special FastTrak Feature"?
>> In your .config, the option would be
>> CONFIG_PDC202XX_FORCE=y
>> and report back to the list?
>
> For reasons reported in another mail (ac97 fails to build) my attempt at
> pre7 failed. Also, as far as I know, the FastTrak feature enables the
> Promise RAID mode: I am not using that. Instead, I just want 4 IDE disks
> which will be bound using Linux raid5.
No, without the "Special FastTrak Feature" you cannot see the disks at
all, regardless if you want RAID or plain IDE.
> Are you saying you want to know if the Promise mode works (independent
> of whether I wish to use it?)
I'm currently trying to find out if enabling the "Special FastTrak
Feature" is hurting anyone. So far, it seems that enabling it only
conflicts with the binary only driver from Promise.
If you want to see your disks, please enable the feature.
Regards,
Carl-Daniel
--
http://www.hailfinger.org
next prev parent reply other threads:[~2003-04-07 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 1:13 Problems booting PDC20276 with new IDE setup code Ruth Ivimey-Cook
2003-04-07 2:34 ` Carl-Daniel Hailfinger
2003-04-07 13:16 ` Ruth Ivimey-Cook
2003-04-07 14:28 ` Carl-Daniel Hailfinger [this message]
2003-04-07 20:43 ` Ruth Ivimey-Cook
2003-04-07 21:20 ` Carl-Daniel Hailfinger
2003-04-07 21:44 ` Ruth Ivimey-Cook
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=3E918B13.4080805@gmx.net \
--to=c-d.hailfinger.kernel.2003@gmx.net \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=linux-kernel@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