From: Alistair John Strachan <alistair@devzero.co.uk>
To: a.ledvinka@promon.cz
Cc: linux-kernel@vger.kernel.org
Subject: Re: promise (105a:3319) unattended boot
Date: Fri, 15 Oct 2004 21:12:18 +0100 [thread overview]
Message-ID: <200410152112.18691.alistair@devzero.co.uk> (raw)
In-Reply-To: <OF77D5B4E1.A38CC6EC-ONC1256F2E.004E78A5-C1256F2E.0050B72C@promon.cz>
On Friday 15 Oct 2004 15:41, you wrote:
> Hello.
>
> Got here http://pciids.sourceforge.net/iii/?i=105a3319
> As http://linux.yyz.us/sata/faq-sata-raid.html#tx4 calls it
> soft/accelerator raid version
> Going to use latest kernel from /pub/linux/kernel/v2.4/
>
> But bios even with keyboard unplugged requires me to press one of 2 keys
> to either define array OR continue booting in case no array is defined.
>
> What would you recommend me to do?
> - stay with ft3xx module from promise and 10 level RAID array and not use
> sata_promise?
> - define some array in bios and completely ignore that fact and use
> sata_promise, bypass bios and define custom linux soft raid arrays?
If you define an array, AFAIK the controller doesn't do anything physically to
the discs. It's just the settings it tells the promise driver (thus software
RAID). If you define ANY array, the drives should still be detected by Linux
individually and you can use linux/md to RAID them.
This is how I'm doing it on my older PATA promise card.
> - anything else (no bios flashing and no hw hacking)?
>
--
Cheers,
Alistair.
personal: alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student: CS/AI Undergraduate
contact: 1F2 55 South Clerk Street,
Edinburgh. EH8 9PP.
next prev parent reply other threads:[~2004-10-15 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 14:41 promise (105a:3319) unattended boot a.ledvinka
2004-10-15 17:09 ` Jeff Garzik
2004-10-15 17:27 ` Bartlomiej Zolnierkiewicz
2004-10-15 20:12 ` Alistair John Strachan [this message]
2004-10-15 20:27 ` Joel Jaeggli
-- strict thread matches above, loose matches on Subject: below --
2004-10-15 17:06 Chuck Ebbert
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=200410152112.18691.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=a.ledvinka@promon.cz \
--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