* SY-KT880 DRAGON 2 (VT8237 and ALi 5281 SATA Chipset Conflict?)
@ 2004-09-20 22:51 Matt D. Robinson
2004-09-20 23:46 ` Matt D. Robinson
2004-09-21 2:45 ` J. Ryan Earl
0 siblings, 2 replies; 3+ messages in thread
From: Matt D. Robinson @ 2004-09-20 22:51 UTC (permalink / raw)
To: linux-ide; +Cc: Matt D. Robinson
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.
Just looking for a pointer before I go spending a couple of days
digging into this. It's a test system at this point so I can trash
it as needed.
I've tried all Fedora Core 2 kernels as a starting point (base
2.6.5 and latest sata_via in 2.6.8-1). I can load up top of tree
kernels if needed for testing.
Thanks for any thoughts you have,
--Matt
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: SY-KT880 DRAGON 2 (VT8237 and ALi 5281 SATA Chipset Conflict?)
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
1 sibling, 0 replies; 3+ messages in thread
From: Matt D. Robinson @ 2004-09-20 23:46 UTC (permalink / raw)
To: linux-ide
Please ignore this post. It looks like ALi 5281 SATA support doesn't
exist yet.
--Matt
On Mon, 20 Sep 2004, 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.
|>
|>Just looking for a pointer before I go spending a couple of days
|>digging into this. It's a test system at this point so I can trash
|>it as needed.
|>
|>I've tried all Fedora Core 2 kernels as a starting point (base
|>2.6.5 and latest sata_via in 2.6.8-1). I can load up top of tree
|>kernels if needed for testing.
|>
|>Thanks for any thoughts you have,
|>
|>--Matt
|>
--
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: SY-KT880 DRAGON 2 (VT8237 and ALi 5281 SATA Chipset Conflict?)
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
1 sibling, 0 replies; 3+ messages in thread
From: J. Ryan Earl @ 2004-09-21 2:45 UTC (permalink / raw)
To: Matt D. Robinson; +Cc: linux-ide
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-09-21 2:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).