ASRock AM2NF4G-SATA2

Written by Michael Larabel in Motherboards on 4 June 2006 at 01:00 PM EDT. Page 3 of 8. Add A Comment.

Performance:

As we have already delivered a wealth of ASRock AM2NF4G-SATA2 benchmarks throughout our other AMD Socket AM2 benchmarks, as well as comparing the performance to the Socket 939 components, for this article today we will solely be looking at this motherboard -- unlike our traditional motherboard reviews with multiple comparison motherboards. With that said, we will also be looking at its integrated GeForce 6100 video. When overclocking the AMD Athlon 64 X2 4200+, whether we raised the multiplier or the FSB, and no matter the voltage or memory settings, the system would fail to boot, and when it attempted to restore the original settings, the reported frequencies would be incorrect. We imagine this overclocking issue is due to early BIOS used as we received the sample prior to the board being officially announced.

Hardware Components
Processor: AMD Athlon 64 X2 4200+ (2.20GHz)
Motherboard: ASRock AM2NF4G-SATA2 (nForce 410)
Memory: 2 x 512MB Corsair XMS2 DDR2-667
Graphics Card: NVIDIA GeForce 7800GTX 256MB
Hard Drives: Seagate Barracuda 7200.9 160GB SATA2
Optical Drives: Lite-On 16x DVD-ROM
Power Supply: Sytrin Nextherm 460W
Software Components
Operating System: Fedora Core 5
Linux Kernel: 2.6.16-1.2122_FC5 SMP (x86_64)
GCC: 4.1.0
Graphics Driver: NVIDIA 1.0-8762
X.Org: 7.0.0

As the AM2NF4G-SATA2 relies upon a Chipset that was released last year, the support in Linux has improved. However, like the ASRock 939NF4G-SATA2, when attempting to boot Fedora Core 5 with an optical drive attached, there was a problem with the drive being confused (ireason = 0x02). When it comes to LM_Sensors, it had loaded the w83627ehf-isa-0290 module, which had successfully contained the case fan speed. CPU fan speed, system temperature, CPU temperature, and an additional temperature probe named temp3. Other than the IDE issue, the AM2 experience with Fedora Core 5 on this motherboard was satisfactory with no other compatibility problems. For benchmarking we used Enemy Territory, Doom 3, HDparm, Gzip Compression, LAME Compilation, LAME Encoding, Blue Sail Software Opstone Sparse-Vector Scalar Product, Blue Sail Software Opstone Singular Value Decomposition, and FreeBench.


Related Articles