Solved: GA-890GPA-UD3H and F3 Compatibility

Edit: The problem has been solved. Those interested in the solutions it's simple really you disable SATA3 in the BIOS. Go into the "Integrated Peripherals" menu. Next to "OnChip SATA3.0 Support" change it from "Enabled" to "Disabled." Save the changes and exit. Now the motherboard should be able to see any Samsung hard drives.

My new Gigabyte GA-890GPA-UD3H doesn't recognize my F3 1TB when it's plugged into a blue SATA 6Gb/s port. It recognizes it fine if it's plugged into a white SATA 3Gb/s port. Everything else I've tried in the SATA 6Gb/s ports work fine (Samsung DVD Burner and WD 640GB AAKS) and that's using the same SATA II cable I tried with the F3. The main problem is I have two F3s and want to do RAID-0. I know they support it but I there is only one RAID driver on Gigabyte's site and it's for the 6Gb/s ports.
Edited by Ben the OCer - 9/2/10 at 10:09pm

I'm wondering if it's a compatibility problem with all Samsung hard drives on SATA 6Gb/s ports or just this board?

I've never looked at SMART data before. I downloaded SpeedFan but there is nothing in the SMART tab (the drop down box next to Hard disk doesn't have any drives listed). I don't have a eSATA enclosure. I might as well just plug it inside to the white ports. There is no built-in eSATA port on the I/O panel, and using an eSATA port on the front of a case wouldn't change anything because it would be plugged into the white port anyway. The problem is there are no RAID drivers for the white ports. At least the ones on Gigabyte's site didn't work so I assume they are for the 6Gb/s ports. The blue ports are controlled by the SB850 Southbridge and the white ports are controlled by a separate chip that Gigabyte added, that's why they need separate RAID drivers.

Here are all the BIOS settings I changed and what I change them to:

Menu: MB Intelligent Tweaker(M.I.T.)
CPU Clock Ratio: [x12.5] 3800MHz
CPU NorthBridge Freq: [x7] 2128MHz
CPU Host Clock Control: [Manual]
CPU Frequency(MHz): [304]
PCIE Clock (MHZ): [100]
HT Link Width: [Auto]
HT Link Frequency: [x7] 2128MHz
Memory Clock: [x5.33] 1620MHz
CPU PLL Voltage Control: [2.5v]
DRAM Voltage Control: [1.65v]
NB Voltage Control: [1.3v]
SidePort Voltage: [1.6v]
NB/PCIe/PLL Voltage Control: [1.8v]
CPU Voltage Control: [+0.05v] 1.475v

Anything I didn't mention I left at Auto. Realize my motherboard chipset voltages might be sightly different than yours if you have a different motherboard. I turned off Turbo CORE but left Cool'N'Quiet on. After finding the max overclock for the processor I manually changed the RAM timings and found the perfect clock for it. It's better to only overclock one thing at a time so you know what is cause instability if you run into it.

I would highly suggest turning off Turbo CORE. Only in the case of a light overclocking could you possibly leave it on. Another problem is it increases the voltage too, which can be a problem if you already raised the voltage to stabilize an overclock.

That is correct with the 1055T you have to overclock the base clock and with the 1090T you can both overclock the base clock and raise the multiplier. Losing money due to overclockers is really a non-issue for AMD and Intel because so few people do it. Think about it, how many people build their own computers, how many of those people have motherboards that can overclock, and then how many of those people actually overclock their computers? That's a very small group compared to how many people buy OEM computers. Most OEM computers have a locked BIOS that can't overclock. If they locked the base clock in the CPU itself that would make us enthusiast really mad and would give a competitive advantage to their competitor if they don't do the same.
Edited by Ben the OCer - 5/8/10 at 11:17am

I'm pretty sure I installed the chipset drivers. I'll have to get back with you about the SMART stuff. My fan controller is being stupid. I'll have to fix that first because it randomly shuts off all the fans connected to it (not cool at all when the CPU and GPU fans are connected to it). I'm going to connect the CPU and GPU fans to the motherboard instead.

I know it's pretty strange. It could be BIOS related. Hopefully a future BIOS release will fix this issue. A member on here contacted me who has a rev.2 board and he said his F3 1TB worked fine connected to the blue ports. Though mine is a rev.1 board. Which one do you have? I think it says it on the board somewhere but you can also see the USB headers are in slightly different spots.