Foxconn Black Ops - Raw, Unadulterated Power
by Rajinder Gill on July 30, 2008 11:00 PM EST- Posted in
- Motherboards
Specifications
Foxconn Black Ops | |
Market Segment | High-End/Extreme Benchmarking |
CPU Interface | Socket T (Socket 775) |
CPU Support | LGA775-based Core 2 Duo, Core 2 Extreme, or Core 2 Quad Recommended |
Chipset | Intel X48 (MCH) Northbridge and ICH9R Southbridge |
Front Side Bus Speeds | Auto, 100 ~ 900 in 1MHz increments |
DDR3 Memory Speed | Auto, Nine Ratios dependent upon Strap Setting |
FSB Strap | Auto, 200, 266, 333, 400 |
PCIe Speeds | Auto, 100MHz - 255MHz |
PCI Speeds | Synchronus or Lockable at 33.6MHz, 37.3MHz and 42MHz |
Core Voltage | Auto, 0.825V to 1.60V in .00625 increments + Voltage Multiplier to 2.44V |
CPU Clock Multiplier | 6x ~ 11x, downward adjustable for Core 2, upward to 31 for Extreme |
DDR3 DRAM Voltage | Auto, 1.418V ~ 2.873V in .038V increments, 1.50V standard |
DRAM Timing Control | Auto, Manual - 34 DRAM/Chipset Options (tCL, tRCD, tRP, tRAS, tRFC + 11 sub-timings) |
DRAM Command Rate | Auto, 1T, 2T (mislabled - should be 1N and 2N) |
NB Voltage | 1.156V ~ 2.395V in .045V increments, 1.25v standard |
SB Voltage | 1.388V ~ 1.95V in .038V increments 1.05V standard |
CPU VTT Voltage | 1.20V to 1.725V in .075V increments, 1.20V standard |
CPU PLL Voltage | 1.395V to 2.446V in .33V increments, 1.5V standard |
CPU Vdroop Compensation | Enabled, Disabled |
CPU GTL | Individual Core Adjustments, Default, +31 or -31 steps in 1 step increments |
NB Voltage Reference | Default, +31 or -31 steps in 1 step increments |
Dram Pull Up, Down & Ref Voltage | Default, +31 or -31 steps in 1 step increments |
CPU Clock Skew Control | 0-1500ps in 100ps increments |
CPU Clock Amplitude Control | 700mv-1000mv in 100mv increments |
Memory Slots | Four 240-pin DDR3 DIMM Slots Dual-Channel Configuration Regular Unbuffered DDR3 Memory to 8GB Total |
Expansion Slots | 3 - PCIe 2.0 x16 (2 - x16, 1 - x4 electrical) 3 - PCI Slot 2.2 |
Onboard SATA/RAID | 6 SATA 3Gbps Ports - ICH9R (RAID 0,1, 10, 5) 2 eSATA 3Gbps Port - JMicron JMB363 |
Onboard IDE | 1 ATA133/100/66 Port (2 drives) |
Onboard USB 2.0/IEEE-1394 | 12 USB 2.0 Ports - 6 I/O Panel - 6 via Headers 2 Firewire 400 Ports - 1 I/O Panel, 1 via Header |
Onboard LAN | Dual Gigabit Lan |
Onboard Audio | 7.1 Channel HDA Plug-In Audio Card |
Power Connectors | ATX 24-pin, 8-pin ATX 12V |
I/O Panel | 1 x PS/2 Keyboard 1X PS/2 Mouse 2 x eSATA 2 x SPDIF - Optical Out, Coaxial Out 1 x IEEE 1394 2 x RJ45 6 x USB 2.0/1.1 |
Fan Headers | 6 - CPU, (5) Chassis |
Fan Control | CPU and Chassis Fan Control via BIOS |
BIOS Revision | G28 |
All manner of goodies are bundled with the Black Ops: a 120MM fan, a plastic dry ice cooling pot for the Northbridge, and a Plexiglas "benching table" for open-air use.
Software wise, we have the Aegis Panel, which allows on-the-fly FSB changes and adjustments for all primary voltage circuitry as well as monitoring and changing fan speeds for the processor, motherboard and Northbridge areas. We found the Aegis Panel quite useful for most situations, although when benchmarking at very high speed you'll probably find that Aegis Panel won't always open. In such situations, the use of SetFSB is advised.
32 Comments
View All Comments
yyrkoon - Monday, August 11, 2008 - link
You sir have obviously not heard of the term of "being slash-doted", but lets just say many hosts dread having links to their machines being on slash-dot because of the sheer volume of traffic that is caused on the host end.Either way, I never said anything about slash-dot so . . .
DrMrLordX - Thursday, July 31, 2008 - link
Seriously:http://linux.slashdot.org/article.pl?sid=08/07/25/...">http://linux.slashdot.org/article.pl?sid=08/07/25/...
Rajinder Gill - Thursday, July 31, 2008 - link
And in response,http://www.xtremesystems.org/forums/showthread.php...">http://www.xtremesystems.org/forums/showthread.php...
read post 61.
regards
Raja
DrMrLordX - Thursday, July 31, 2008 - link
This matter isn't settled, but it is being argued by others in other forums where such things will be discussed in greater detail than they will here. Don't expect it to go away so easily.whatthehey - Thursday, July 31, 2008 - link
In order for it to go away, it just needs to be fixed. That shouldn't be too difficult. And then all the millions of Linux enthusiasts that run top-end $400 motherboards with heavy overclocking can rest easy.Wait! What's that you say? Most home Linux users are running hand-me-down $200 systems? Hmmm.... Can't imagine why they aren't a priority.
DrMrLordX - Thursday, July 31, 2008 - link
I put Xubuntu on my X2-3600+ system when it was brand new and pushed the chip to 3.2 ghz (stable) at one point. $200 hand-me-down? Nah.The fact that there are fully-suported flavors of Linux out there that can run on a cheap-as-in-free system from ten years ago is a plus, but it doesn't mean you have to run Linux on a system like that.
yyrkoon - Thursday, July 31, 2008 - link
I think you're a bit confused. Nothing like stereotyping whole groups for our own enjoyment though eh ?yyrkoon - Thursday, July 31, 2008 - link
Those threads are bogus. There is NOTHING innocent regarding pointing 5 versions of Windows to the right tables, while having the Linux table point to an invalid region of memory, thus causing lock ups and instabilities.yyrkoon - Saturday, August 2, 2008 - link
FOXCONN has seen the error in their ways whether intentional or not. This is a boon for both FOXCONN, and linux users a like.http://ubuntuforums.org/showthread.php?t=877721">http://ubuntuforums.org/showthread.php?t=877721
Regardless of whatever OS/Hardware I choose, it is very good to know that a company such as FOXCONN is a company that listens to its customers(eventually).
MamiyaOtaru - Thursday, July 31, 2008 - link
Yeah, they screwed up. But seriously, follow the threads. The one on Ubuntu forums where it all seems to have started lead to someone from the company replying, saying someone screwed up and that they would be fixing it.The initial tech support guy's response was not what one would want to hear, but in the end it was just a lowly tech support guy.
Seriously, it was good to get steamed when it looked like they were deliberately screwing people over, but the need has passed. Keep some pressure on to make sure they actually follow through, but perpetual nerdrage isn't doing any good now that the issue is acknowledged and scheduled for a fix.