sata controller

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
This is a multi-part message in MIME format.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Kw-571s Kouwell,
After booting several times alright, then suddenly it reads its bios  
after the computer bios, it sees the sata disks Primary channel 1: disk  
name 1 Secondary... but now it doesn't want to load the computer afterwards?

It says it's a hot-plug i tried to plug powered sata  
disks through windows which i made successfuly and there they work, so  
it's the issue something about the booting(i changed the places on the  
pci slots, but didn't help it).

WOuld pluging power to sata disks into/through windows be harmfull to  
computer or the disk? (because pluging sata data cable through windows  

Content-Type: text/x-vcard; charset=utf-8;
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;

fn:Majki Majk
n:;Majki Majk
note;quoted-printable:Cijenjena ponuda na e-mail kontakt!=0D=0A=
    Ozbiljne ponude molim!=0D=0A=
    Mo=C5=BEe i sms-om!


Re: sata controller

Majki Majk wrote:
Quoted text here. Click to load it

The 571S uses the SIL3512 PCI to dual SATA chip, which appears to be
functionally very similar to the SIL3112. (The chip has a different number
of pins, but the block diagram of its operation seems identical.)

The PCI card will have at least two chips on it. The SIL3512 should be
the largest chip. There will also be a BIOS chip soldered to the card,
perhaps a PLCC type. That chip holds the add-in BIOS.

When the computer starts, it loads the add-in BIOS from the card. The
add-in BIOS supports INT 0x13 calls, which is how the computer would be
able to boot from the card. If you set the motherboard BIOS to
"INT 0x13 capture" [Disabled], that would prevent the 571S BIOS
from loading, but it would also prevent other add-in BIOS modules
from loading, ones which you may need.

If the add-in BIOS is not loaded during POST, that should not affect
the ability to install a driver in Windows, and use the disks
connected to the SIL3512, as "data-only" disks. INT 0x13 (hexidecimal)
is there, to support "boot" disks.

The add-in BIOS chip can be reprogrammed, but the card designers (Kouwell)
have to use the correct flash chip, to allow the standard Silicon Image
flasher tool to work. This capability is not going to help you, in this
case, but if you even need to switch between RAID and non-RAID behavior,
this is how you do it.


Re: sata controller

Majki Majk wrote:
Quoted text here. Click to load it

You're right. I see the manual doesn't agree with the actual card. I see
a SIL3112 on this one. That should not change the nature of the problem
though, except to use the correct BIOS file for the board.

So, some questions -

1) Is the file you flashed the board with, the correct one ?
    Did you get the file from Kouwell, or from Silicon Image ?

2) The driver you installed via F6, should match the OS you are
    using. If the OS is 32 bit, then the driver should be a 32
    bit version as well. The 571-S driver has Si3112r.inf in it,
    implying it is for a SIL3112 chip with RAID BIOS installed.
    Note that there is a RAID BIOS for the PCI card, and also
    and IDE BIOS. And the IDE BIOS would need a different driver.

If you can get into Windows again, you could use Everest, to
see what the enumeration for the card is. It would be
under "Devices:PCI".

According to this, SIL3112 is "1095 3112" and SIL3512 is "1095 3512".
An important value as well, would be the next entry listed, which
would be the subsystem value. If the subsystem value was corrupted,
perhaps that has something to do with the driver not installing.
It really depends on what is in the .inf file of the driver package.

What files are you using right now ? The ones from the Kouwell site ?

On the Silicon Image site, this page has BIOS for a SIL3112 based card. &

   The latest I see, is dated from 2007.

   SiI3112 IDE, SATARAID and system BIOS   4.2.84   12/3/2007   120 KB

   If you want to run in IDE mode, that would be "b4284.bin". For
   RAID mode, the "r4284.bin" would be used. IDE mode should support
   the detection of a single disk connected to the board. As far as
   I remember, if you use the RAID BIOS, then two hard drives should be

On this page, are drivers. &

    SiI3x12 32-bit Windows BASE Driver  6/25/2007  130 KB
    The description says this one is for IDE mode on WinXP, for 4284 BIOS.

    SiI3x12 32-bit Windows SATARAID Driver  3/14/2007  159 KB
    the description says this one is for RAID mode on WinXP, for 4284 BIOS.

There is a separate tool for the SATARAID management. This would be for
setting up an array, from the comfort of Windows. You can check array
status (failed, degraded, critical or whatever), with a utility like
this. In the past, this tool used Java, which is a nuisance, as you
have to install Java in order to run it. And I consider Java to be
a security risk, because you should always be using the latest version
while it is on your computer. &

Good luck in recovering the operation of your card.


Re: sata controller

Majki Majk wrote:
Quoted text here. Click to load it

You should use a BIOS that is consistent with the marking on the top of
the chip.

I wasn't aware the enumeration could be changed via the firmware,
but on checking the datasheet for both the 3112 and the 3512, I see
that the enumeration *is* loaded from the firmware. So flashing the
wrong BIOS will change what you see in Everest.

As far as I can remember, if you use the RAID BIOS, you need two
hard drives connected to the board. If you use the IDE BIOS, then
one may be sufficient, to install and boot Windows. I say this,
because I can remember someone having a problem getting the
RAID BIOS during POST, to do anything when one drive was connected.

And if you want to boot from the card, the equivalent of
"INT 0x13 capture" or the like, has to be enabled in the
BIOS. If the card is only being used for "data" drives and
not "boot" drives, then the BIOS module doesn't have to
be loaded for Windows to be able to access a drive. But
based on your experiment, I see that since the firmware
does control the enumeration, then loading the correct
firmware is needed, in order for the right drivers
to be accepted in Windows.


Re: sata controller

Majki Majk wrote:

Quoted text here. Click to load it

OK, so with the drive connected to the Kouwell board, you
boot into Windows from another drive, and the SATA drive
on the SIL3112 can be seen in Explorer ? So it works for
a short time, and then suddenly the drive is no longer
seen ?

What about the jumper on the SATA drive ? SATA drives may have
a jumper position on the back, a "force 150" jumper. It sets
the transfer rate on the cable to 150MB/sec. Sometimes the
jumper is needed, if connecting to a VIA Southbridge. Perhaps
you could check the documentation for the drive, and see what
jumper is needed, to force the drive to stay at the lower
cable transfer rate of 150MB/sec.

Does the hard drive test OK on another SATA-equipped computer ?
Connect the drive to another computer, and download a diagnostic
program from the hard drive manufacturer web site, and test the


Site Timeline