sata controller

[Majki Majk]

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 controller...so 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
works)

 

[Paul]

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 controller...so 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
works)

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.)

http://www.kouwell.com.tw/allpage6.htm

http://www.siliconimage.com/products/product.aspx?id=29

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.

http://en.wikipedia.org/wiki/INT_13

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=15&ctid=2&osid=0&

Paul

 

[Majki Majk]

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.)

Hi PAul! I flashed the controller with the newer bios and via windows
utility. On the sole controller on the chip which you mentioned is
written 'Sil3112' but the page where you lead me is for SIL3512...the
manual is for sata controllers, it's valid though. But the things are
different, now i flashed the card controller with the newer 3512 bios,
and when turning on computer is sees the controller and the disks on it
but blocks itself. Restarting, removing the disks it works, it goes
straight forward to XP. In xp, after switching to newer bios, it
doesn't recognize it, nor the various drivers, moreover in windows
installation cd after pressing F6 for installation of Raid controllers
and pressing S for source of drivers. It can't install drivers from A:
cause it says that drivers are corupted, (the drivers names are: AMD64
and IA64...)....i think that it has something to do with the
motherboard, it's old pchips M830LR for Sdr and Ddr Ram, oldsmobile but
it works like a plane...hmm... the processor is Duron800, which is in
bios presented as 100/133 (previously was 100/100), the upgrades are to
1.4 Athlon and 950mhz Duron. I tried things in bios too, but haven't
find anything what would make things go!

http://www.kouwell.com.tw/allpage6.htm

http://www.siliconimage.com/products/product.aspx?id=29

Yeah! There is a page for 3112 drivers also on kouwell but the bios page
leads to this too!

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.

How would i do that for IN 0x13 capture? There's no option for that
through bios. What do you suggest ?

http://en.wikipedia.org/wiki/INT_13

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.

Disks don't work anymore through windows too now!

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=15&ctid=2&osid=0&


Paul

Yeah, i think i have worse the things so now i don't know where i stand
with this controller.. !??!

 

[Majki Majk]

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 controller...so 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
works)

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.)

http://www.kouwell.com.tw/allpage6.htm

http://www.siliconimage.com/products/product.aspx?id=29

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.

http://en.wikipedia.org/wiki/INT_13

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=15&ctid=2&osid=0&


Paul

One more thing important or not, before flashing the windows flash
utilitx couldn't discern the version of controller and after it could.
Now it even doesn't see the controller through WindowsXp Sp2.

Uff, nice talking too you, thanks for previous answer-help!

 

[Paul]

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.)

Hi PAul! I flashed the controller with the newer bios and via windows
utility. On the sole controller on the chip which you mentioned is
written 'Sil3112' but the page where you lead me is for SIL3512...the
manual is for sata controllers, it's valid though. But the things are
different, now i flashed the card controller with the newer 3512 bios,
and when turning on computer is sees the controller and the disks on it
but blocks itself. Restarting, removing the disks it works, it goes
straight forward to XP. In xp, after switching to newer bios, it
doesn't recognize it, nor the various drivers, moreover in windows
installation cd after pressing F6 for installation of Raid controllers
and pressing S for source of drivers. It can't install drivers from A:
cause it says that drivers are corupted, (the drivers names are: AMD64
and IA64...)....i think that it has something to do with the
motherboard, it's old pchips M830LR for Sdr and Ddr Ram, oldsmobile but
it works like a plane...hmm... the processor is Duron800, which is in
bios presented as 100/133 (previously was 100/100), the upgrades are to
1.4 Athlon and 950mhz Duron. I tried things in bios too, but haven't
find anything what would make things go!

http://www.kouwell.com.tw/allpage6.htm

http://www.siliconimage.com/products/product.aspx?id=29

Yeah! There is a page for 3112 drivers also on kouwell but the bios page
leads to this too!

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.

How would i do that for IN 0x13 capture? There's no option for that
through bios. What do you suggest ?

http://en.wikipedia.org/wiki/INT_13

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.

Disks don't work anymore through windows too now!

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=15&ctid=2&osid=0&


Paul

Yeah, i think i have worse the things so now i don't know where i stand
with this controller.. !??!

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.

http://img.xcomputer.cz/ImgW.asp?cd=AF926&fd=f3

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 "DevicesCI".

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.

http://pciids.sourceforge.net/pci.ids

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=63&cid=15&ctid=2&osid=0&

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
present.

On this page, are drivers.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=63&cid=3&ctid=2&osid=4&

SiI3x12 32-bit Windows BASE Driver 1.3.68.2 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 1.0.60.0 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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=11&ctid=2&osid=4&

Good luck in recovering the operation of your card.

Paul

 

[Majki Majk]

Majki Majk wrote:
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 controller...so 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 works)


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.)

Hi PAul! I flashed the controller with the newer bios and via windows
utility. On the sole controller on the chip which you mentioned is
written 'Sil3112' but the page where you lead me is for SIL3512...the
manual is for sata controllers, it's valid though. But the things are
different, now i flashed the card controller with the newer 3512 bios,
and when turning on computer is sees the controller and the disks on
it but blocks itself. Restarting, removing the disks it works, it goes
straight forward to XP. In xp, after switching to newer bios, it
doesn't recognize it, nor the various drivers, moreover in windows
installation cd after pressing F6 for installation of Raid controllers
and pressing S for source of drivers. It can't install drivers from A:
cause it says that drivers are corupted, (the drivers names are: AMD64
and IA64...)....i think that it has something to do with the
motherboard, it's old pchips M830LR for Sdr and Ddr Ram, oldsmobile
but it works like a plane...hmm... the processor is Duron800, which is
in bios presented as 100/133 (previously was 100/100), the upgrades
are to 1.4 Athlon and 950mhz Duron. I tried things in bios too, but
haven't find anything what would make things go!

http://www.kouwell.com.tw/allpage6.htm

http://www.siliconimage.com/products/product.aspx?id=29

Yeah! There is a page for 3112 drivers also on kouwell but the bios
page leads to this too!

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.

How would i do that for IN 0x13 capture? There's no option for that
through bios. What do you suggest ?

http://en.wikipedia.org/wiki/INT_13

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.

Disks don't work anymore through windows too now!

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=15&ctid=2&osid=0&


Paul

Yeah, i think i have worse the things so now i don't know where i
stand with this controller.. !??!

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.

http://img.xcomputer.cz/ImgW.asp?cd=AF926&fd=f3

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 ?

Really...i don't know now anymore. I used two verisons .70 and 4.2.84.
I installed both to check up both versions and their behaviors...i
concluded that 2.84 is a better solution, regarding the date of publishing.

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.

I think WinPro is 64bit, my motherboard fsb is 64bit too as everest is
showing.

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

According to this, SIL3112 is "1095 3112" and SIL3512 is "1095 3512".

It'sIL3512 enumeration, the thinhg which is confusing me a lot is, is
this number written there just because i flashed the divice or...if so,
than before was written 1095-3112-i presume !?

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.

The same number as previous i.e. 1095-3512.

It really depends on what is in the .inf file of the driver package.

http://pciids.sourceforge.net/pci.ids

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

No, no the ones from the silicon which you directed me to...The once fro
m Kouwell are corrupted when i tried to install them.

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

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=63&cid=15&ctid=2&osid=0&

DOwnloaded. The catch is that

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
present.

On this page, are drivers.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=63&cid=3&ctid=2&osid=4&


SiI3x12 32-bit Windows BASE Driver 1.3.68.2 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 1.0.60.0 3/14/2007 159 KB
the description says this one is for RAID mode on WinXP, for 4284 BIOS.

Yeah, right...that's all okej, but things get a bit coplicated, cos on
the chip on the card the chip is 3112, but in the everset pci ID is 3512
so the subsystem id is 3512...that's the confused part.

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=11&ctid=2&osid=4&


Good luck in recovering the operation of your card.

Thanks for the Luck, good luck youu tooo

Krešo

 

[Majki Majk]

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.

http://www.siliconimage.com/support/supportsearchresults.aspx?pid=29&cid=11&ctid=2&osid=4&


Good luck in recovering the operation of your card.

Paul

I made controller to see the disks in windows, but booting fails.

This is the info through siflashtool.exe :

Controller Type PCI Location Flash Part BIOS Ver. BIOS Date
=============================================================================
Sil 3512 Bus:00 Dev:0d AMD Am29F010B 4.3.84
01-19-2007


I went into silicon sata raid controller management and flashed
about10times with different bioses, but null, nothing...but it works
from windows interface

Thanks on your time Paul!
mm

 

[Paul]

I made controller to see the disks in windows, but booting fails.

This is the info through siflashtool.exe :

Controller Type PCI Location Flash Part BIOS Ver. BIOS
Date
=============================================================================

Sil 3512 Bus:00 Dev:0d AMD Am29F010B 4.3.84 01-19-2007


I went into silicon sata raid controller management and flashed
about10times with different bioses, but null, nothing...but it works
from windows interface

Thanks on your time Paul!
mm

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.

Paul

 

[Majki Majk]

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.

Tried both, and single, the same thing, reads them...reading...stops!
Hmm...something maybe with the IDE drivers, i'll give it a shoot again.

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.

Paul

Haven't found INT 0x13 capture in my bios, seems it's and old mobo.
Yes, their purpose would only be as data harddisks, so they can stay
connected through several boots...that's all. Will try to deal with the
bioses again, if it worked when i first installed it then the heck, it
must work again...what lesser touching it- IT works better.

Can you teleport in my room ?

 

[Paul]

Tried both, and single, the same thing, reads them...reading...stops!
Hmm...something maybe with the IDE drivers, i'll give it a shoot again.


Haven't found INT 0x13 capture in my bios, seems it's and old mobo.
Yes, their purpose would only be as data harddisks, so they can stay
connected through several boots...that's all. Will try to deal with the
bioses again, if it worked when i first installed it then the heck, it
must work again...what lesser touching it- IT works better.

Can you teleport in my room ?

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
drive.

Paul