From: "J. Ryan Earl" <heretic@clanhk.org>
To: "Matt D. Robinson" <matt@aparity.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: SY-KT880 DRAGON 2 (VT8237 and ALi 5281 SATA Chipset Conflict?)
Date: Mon, 20 Sep 2004 21:45:30 -0500 [thread overview]
Message-ID: <414F95CA.5070306@clanhk.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0409201545500.3505-100000@nakedeye.aparity.com>
Matt D. Robinson wrote:
>Hi, all. The new Soyo SY-KT880 DRAGON 2 uses two separate SATA
>RAID chipsets on the motherboard, the VIA8237 and ALi 5281.
>I'm still testing this, but it looks like only one function is
>loaded at any given time. Is there a conflict between utilizing
>both devices simultaneously? I'm trying to use them in non-RAID
>(just SATA) mode so there isn't anything special going on here.
>sata_via.ko doesn't find the ALi 5281 devices (SATA3/4), and the
>VIA8237 (SATA1/2) are recognized just fine.
>
>
sata_via isn't going to work for an ALi chipset.
-ryan
prev parent reply other threads:[~2004-09-21 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 22:51 SY-KT880 DRAGON 2 (VT8237 and ALi 5281 SATA Chipset Conflict?) Matt D. Robinson
2004-09-20 23:46 ` Matt D. Robinson
2004-09-21 2:45 ` J. Ryan Earl [this message]
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=414F95CA.5070306@clanhk.org \
--to=heretic@clanhk.org \
--cc=linux-ide@vger.kernel.org \
--cc=matt@aparity.com \
/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;
as well as URLs for NNTP newsgroup(s).