From: <me@heyjay.com>
To: Duncan Hill <dhill@cricalix.net>, linux-raid@vger.kernel.org
Subject: Re: Gigabyte GA-7N400 Pro2 and raid
Date: Thu, 29 Apr 2004 00:48:41 -0500 [thread overview]
Message-ID: <000d01c42dad$a2073530$6705a8c0@a30> (raw)
In-Reply-To: 200404290638.44608.dhill@cricalix.net
Duncan,
It is ITE 8212 (I'm not sure if it is an "F" though). The driver for RedHat
and Mandrake are available on giga-byte.com. When you say I'm out of luck,
what exactly does that mean?
- I have to wait until linux boots before I can see those drives as plain
old IDE drives (which means I can boot off those drives)
- I have to wait until the kernel is loaded (and subsequently the raid
driver) in order to see the raid device (ie. after I've configured a raid
device during the bios raid config util)?
- I'll never be able to see those drives regardless if they are raid or
plain?
- Maybe something completely different
Thanks
Jay
----- Original Message -----
From: "Duncan Hill" <dhill@cricalix.net>
To: <me@heyjay.com>
Sent: Thursday, April 29, 2004 12:38 AM
Subject: Re: Gigabyte GA-7N400 Pro2 and raid
> On Thursday 29 April 2004 05:19, me@heyjay.com wrote:
> > This is sorta a pre-software-raid question.
> >
> > I just bought and built a box around the Gigabyte GA-7N400 Pro2 Mobo.
It
> > has 4 IDE ports, 2 normal, and 2 upon a raid controller. I figured I
could
> > avoid using Gigabyte's raid, and do software raid upon the 2 extra
ports.
>
> If the chipset is the ITE 8212F, you're probably up a creek. However,
> www.ite.com.tw do have a driver you can download - I have an exact URL if
> their site doesn't work for you.
>
>
next prev parent reply other threads:[~2004-04-29 5:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 4:19 Gigabyte GA-7N400 Pro2 and raid me
[not found] ` <200404290638.44608.dhill@cricalix.net>
2004-04-29 5:48 ` me [this message]
2004-04-29 6:18 ` Duncan Hill
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='000d01c42dad$a2073530$6705a8c0@a30' \
--to=me@heyjay.com \
--cc=dhill@cricalix.net \
--cc=linux-raid@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