ga-7n400 pro 2 (rev 2.0) problems and solutions
I'm new here, but I've noticed on many forums different common problems, some that I've been able to solve myself, others that I haven't.
A few notes on this M/B:
1) To get proper cpu detection, make sure you cet the CPU_CLK to auto. Otherwise u'll be locked in at 100MHz FSB
2) If XP will not boot from SATA (either is raid or base mode). Download the latest 3x12 (Silicon Image 3512 Drivers) from the Gigabyte site and use these with the F6 Option in XP (or 2000 if you use that). The drivers from the CD *DO NOT* work properly to allow XP/2000 to boot after initial format and copy. The same can be said for the "GIGARAID" drivers.
3) A good idea after installing is to force add the alternate driver for the SiI 3512. (i.e. if u are using raid, force install new hardware ** *DO NOT REPLACE/UPDATE THE CURRENT DRIVERS* USE ADD NEW HARDWARE** and use the b**** (base) driver), this will allow you to still boot after changing modes from RAID to BASE, or vice versa, in the main BIOS
Other qwerks:
My system currently has 2 x 80GM WD800JD drives (Western Digital, 80 GB SATA 7200 RPM 8MB Cache... blah blah blah) I have encountered several strange problems...
1) From time to time (which i am currently looking for a solution) The onboard SATA RAID will drop the second drive (Channel 1). I can remove it from the set, but not re-add it. From the SiI 3512 BIOS I attempted to delete the Raid set (Mirrored) and recreate it and copy, this errored out, and therefore I had to start all over, creating the set, formating, reinstalling. It has now happened for the second time. Which leads me to check the drives, which is where I found the second issue.
2) I decided to run the DLGDIAG5 (Western Digital DOS Diagnostics). And upon running, the program would error out before comming up with a DRQ Error 0135. Now, this is a communications error. I remade the disk, same error again. So, I go to troubleshooting. What I have isolated, after much cable swapping, is that it only has this problem when both drives are connected at the same time (each to their own channel). I ran quick tests on both drives separately and they passed, I have yet to run extended tests (I know, I'm getting to it). I decided that I would use the Windows based Diagnostic. so then....
3) I booted in BASE mode (option set in main BIOS) so that the drives would not be masked by the raid set. I ran the WD windows diagnostic, and the funny thing is that in the drive properties, both drives showed up with the same Serial, NOT model, but same SERIAL number. Under the Windows XP, SiI 3512 Windows RAID Utility, and SATA RAID/BASE BIOS drive properties, however, their individual, different serial numbers are detected, properly. But under the DIAGNOSTIC they are shown as having the same serial number. I am going to run Extended DIAG tests on them individually to see if any problems are detected.
Solutions so far suggested by myself: I am going to first off run the DOS diags, on my two drives individually, since it's the best i've got right now.
I'm eventually going to attempt to mod the FK bios to add in the latest revision of the SiI 3512 BIOS, but for now I'm going to try the FI bios I downloaded from this wonderful site.
I'll post here when I figure out more. Hope maybe this has been helpful, and hope if someone has encountered these problems, maybe they can help me.
Thanks again.
A few notes on this M/B:
1) To get proper cpu detection, make sure you cet the CPU_CLK to auto. Otherwise u'll be locked in at 100MHz FSB
2) If XP will not boot from SATA (either is raid or base mode). Download the latest 3x12 (Silicon Image 3512 Drivers) from the Gigabyte site and use these with the F6 Option in XP (or 2000 if you use that). The drivers from the CD *DO NOT* work properly to allow XP/2000 to boot after initial format and copy. The same can be said for the "GIGARAID" drivers.
3) A good idea after installing is to force add the alternate driver for the SiI 3512. (i.e. if u are using raid, force install new hardware ** *DO NOT REPLACE/UPDATE THE CURRENT DRIVERS* USE ADD NEW HARDWARE** and use the b**** (base) driver), this will allow you to still boot after changing modes from RAID to BASE, or vice versa, in the main BIOS
Other qwerks:
My system currently has 2 x 80GM WD800JD drives (Western Digital, 80 GB SATA 7200 RPM 8MB Cache... blah blah blah) I have encountered several strange problems...
1) From time to time (which i am currently looking for a solution) The onboard SATA RAID will drop the second drive (Channel 1). I can remove it from the set, but not re-add it. From the SiI 3512 BIOS I attempted to delete the Raid set (Mirrored) and recreate it and copy, this errored out, and therefore I had to start all over, creating the set, formating, reinstalling. It has now happened for the second time. Which leads me to check the drives, which is where I found the second issue.
2) I decided to run the DLGDIAG5 (Western Digital DOS Diagnostics). And upon running, the program would error out before comming up with a DRQ Error 0135. Now, this is a communications error. I remade the disk, same error again. So, I go to troubleshooting. What I have isolated, after much cable swapping, is that it only has this problem when both drives are connected at the same time (each to their own channel). I ran quick tests on both drives separately and they passed, I have yet to run extended tests (I know, I'm getting to it). I decided that I would use the Windows based Diagnostic. so then....
3) I booted in BASE mode (option set in main BIOS) so that the drives would not be masked by the raid set. I ran the WD windows diagnostic, and the funny thing is that in the drive properties, both drives showed up with the same Serial, NOT model, but same SERIAL number. Under the Windows XP, SiI 3512 Windows RAID Utility, and SATA RAID/BASE BIOS drive properties, however, their individual, different serial numbers are detected, properly. But under the DIAGNOSTIC they are shown as having the same serial number. I am going to run Extended DIAG tests on them individually to see if any problems are detected.
Solutions so far suggested by myself: I am going to first off run the DOS diags, on my two drives individually, since it's the best i've got right now.
I'm eventually going to attempt to mod the FK bios to add in the latest revision of the SiI 3512 BIOS, but for now I'm going to try the FI bios I downloaded from this wonderful site.
I'll post here when I figure out more. Hope maybe this has been helpful, and hope if someone has encountered these problems, maybe they can help me.
Thanks again.
0