From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "a.ledvinka@promon.cz" <a.ledvinka@promon.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: promise (105a:3319) unattended boot
Date: Fri, 15 Oct 2004 19:27:10 +0200 [thread overview]
Message-ID: <58cb370e0410151027687d204f@mail.gmail.com> (raw)
In-Reply-To: <OF77D5B4E1.A38CC6EC-ONC1256F2E.004E78A5-C1256F2E.0050B72C@promon.cz>
Try to define 0 level RAID consisting of one disk only.
This works with Promise PATA, I dunno about SATA.
On Fri, 15 Oct 2004 16:41:37 +0200, a.ledvinka@promon.cz
<a.ledvinka@promon.cz> 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?
> - anything else (no bios flashing and no hw hacking)?
>
> AlL.
>
> please CC me... but anyway if you forget i will have a look into archive.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-10-15 17:32 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 [this message]
2004-10-15 20:12 ` Alistair John Strachan
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=58cb370e0410151027687d204f@mail.gmail.com \
--to=bzolnier@gmail.com \
--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