How to tell if SATA-I or SATA-II settings?

  • Thread starter Thread starter Frodo
  • Start date Start date
F

Frodo

I've installed a Seagate 7200.9 300GB SATA-II on my Asus motherboard with
the nForce 4 ultra chipset.
I've heard that some SATA-II drives come preset to run at SATA-I setting.
How do I tell if the drive/controller is running at SATA-II or SATA-I
setting?
 
Previously Frodo said:
I've installed a Seagate 7200.9 300GB SATA-II on my Asus motherboard with
the nForce 4 ultra chipset.
I've heard that some SATA-II drives come preset to run at SATA-I setting.
How do I tell if the drive/controller is running at SATA-II or SATA-I
setting?
Click to expand...

For Samsungs there is a jumper on the drive, which is documented
on the top label. I expect other manufacturers do the same.
Samsung ships them set to SATA II. This causes problems at
least with my nForce chipset, so I had to set it to SATA I.
Not an issue speed-wise.

Arno
 
Arno said:
For Samsungs there is a jumper on the drive, which is documented
on the top label. I expect other manufacturers do the same.
Samsung ships them set to SATA II. This causes problems at
least with my nForce chipset, so I had to set it to SATA I.
Not an issue speed-wise.

Arno
Click to expand...
What is the issue it causes on Nforce? I just installed that Samsung
SataII I asked about in here on my Asrock Dual939 Uli chipset mb and it
works fine.
 
Previously Garrot said:
Arno Wagner wrote:
Click to expand...
What is the issue it causes on Nforce? I just installed that Samsung
SataII I asked about in here on my Asrock Dual939 Uli chipset mb and it
works fine.
Click to expand...

Then you need not be concerned.

I observed a very slow drive detection by the BIOS (a minute or more)
and then again by Linux, were I got a message along the lines
"drive yyyyyy is slow to respond, please be patient". In the end it
was not successfully detected and got disabled by the kernel. Since
the kernel has its own driver for the chipset and does not use
the BIOS, this really is an issue with the chipset.

After setting the jumper to limit it to SATA-I, it now works
without problem. This is on an ASUS A8N-SLI Premium.

Arno
 
Arno said:
Then you need not be concerned.

I observed a very slow drive detection by the BIOS (a minute or more)
and then again by Linux, were I got a message along the lines
"drive yyyyyy is slow to respond, please be patient". In the end it
was not successfully detected and got disabled by the kernel. Since
the kernel has its own driver for the chipset and does not use
the BIOS, this really is an issue with the chipset.

After setting the jumper to limit it to SATA-I, it now works
without problem. This is on an ASUS A8N-SLI Premium.

Arno
Click to expand...

OK, good to keep in mind if I change mb's and get the same issue, thx.
 
Arno Wagner said:
Then you need not be concerned.

I observed a very slow drive detection by the BIOS (a minute or more)
and then again by Linux, were I got a message along the lines
"drive yyyyyy is slow to respond, please be patient". In the end it
was not successfully detected and got disabled by the kernel.
Click to expand...
Since the kernel has its own driver for the chipset and does not use
the BIOS, this really is an issue with the chipset.
Click to expand...

Yup, obviously can't be the driver.
 
Back
Top