New "D" for the [H]orde

Tobit

[H]ard|DCer of the Month - March 2010/May 2011
Joined
Dec 12, 2005
Messages
5,145
Coming online soon..

newX58-01.jpg


ASRock X58 Extreme
Core i7 920
6GB OCZ Gold DDR3 1600

and yes, I noticed the lop-sided NB-sink as well.. however, it appears to be a design flaw. it is on there securely and uses push-pins.. not much I can do to correct this problem if it is a problem.

Time to slide it in the chassis and power it up.
 
THats not a lian-li case..... hes got that uber 10 slot case that he ordered from MountainMods?!?!?!?!?
 
Just got mine online last night :)
I don't remember my NB HS being lopsided, but yes they do use those plastic pushpins. You could do a chipset HS mod (quick and cheap)...take those off, clean off the paste, reapply new paste (people usually recommend AS Ceramique for NB/SB IIRC since it's not conductive)...use some nuts and bolts from Lowes/Home Depot/Ace (what have you) to secure the heatsinks back on the board. Just grab a side that fits the threaded holes and bolts that aren't too long. You could also grab some rubber washers from the special screw "trays" they have to protect the backside of the board from getting scratched up by the bare bolts.

Truthfully I wouldn't worry about it, the heatsinks run warm to hot anyway so it probably won't matter much if yours is lopsided. I remember all the talk about the IP35 Pro heatsinks being mounted poorly; I never bothered trying to fix mine, I just left 'em alone and they were fine.

In case you wonder, the SATA ports are bottom then top, closest to board first. IE ports 1 and 2, port 1 is flush with the board and port 2 is the one higher up. I couldn't find any info anywhere to figure this out without basically hooking my drives up the other way (which I thought was right, given the "arrow" decal on the board)...and then realize they were wrong.
 
Nitro: It's a Mountain Mods Pinnacle-18.

I will post more pics and details later. I just finished configuring and flashing my BIOS and just booted PartedMagic from USB stick to partion a partion for WinXP (for OC testing) and several partitions for Linux (folding).
 
Here are a couple more pics while I install XP to start OC testing. I am not quite finished with it yet but it is pretty close to being done (if builds are ever done).

newX58-02.jpg


newX58-03.jpg


and, finally.. I'm a screenshot whore so here is PartedMagic USB image I used to do the initial partitioning for dual boot.

Screenshot.png
 
Nice usage of 1.5TB's of space! :) 1,336.789GB total storage

*edit* OMG, I is stupid..... didnt see the arrow besides sda4 as being an extended drive, so only 750GB.
 
Last edited:
Why does linux need so many partitions?
Good question. It doesn't "need" so many, you can run with just one, but, as a former Unix SA, I've always done it this way. Some reasons for doing so:

  • Reliability: Disk corruption tends to be specific to a given partition. By subsetting your disk(s), you're reducing the amount of space that's going to be affected by any given disk error. If part of your disk goes south, you'll still likely have most of your system available.

  • Containment: It's very helpful to contain runaway processes. By restricting /tmp and /var to their own partitions, you're pretty sure to have space available on the root filesystem or /home even if some process goes crazy with its tempfiles, or your system logs fill up.

  • Security: By separating out your partitions, you can assign permissions appropriately. As a matter of course, only root and /udev (generally handled automatcially) need be mounted with device permissions, it and /usr are the only partitions needing SUID permissions, /usr can be mounted read-only for the most part, etc. While these permissions can be changed without unmounting a filesystem, they may prevent some system exploits, and will almost certainly keep you from shooting yourself in the foot at some point.

  • Backups: many backup utilities are partition-based, or can be instructed to follow (or restrict themselves to) partition boundaries. Separating system partitions (root, /boot, /etc, /usr, /var) from locally managed (/usr/local, /home) and temporary (/tmp) makes system upgrades and migrations easier to handle as well.

  • Management: With separate partitions, it's possible to back up one partition to another while performing administrative tasks. This is useful should, say, you need to convert between non-interchangeable filesystem types.

  • Overdoing It??: Yes, you can have too many partitions. Beyond a point, partitioning creates more issues -- you're subdividing your system, cutting into usable space, and adding complexity -- than you're solving. For small systems (< 500 MiB), root, /usr, and swap may be all you need, with /tmp, /var, and /home symlinked under /usr. By priority, I'd create: root, swap, /usr, /boot, /tmp, /var, and /home as separate filesystems, with increasing space.
 
Just started running Prime 95 @ 3.8 GHz - 20x190

ss.jpg
 
Welp, that didn't work out too well. =) Prime 95 was having some rounding errors and Linpack was not stable. So, I turned vdroop off so I could have some more control over vcore and things are a bit more stable now. I just finished 20 passes of Linpack and now running Prime 95 again.
 
Best of luck with the build, Tobit. It's an awesome setup! :cool:
 
Thanks Apollo.

Just noticed the very loose memory timings as I was just trying to figure out why Prime 95 was still giving me rounding errors. I tightened them up to OCZ spec speeds of 8-8-8-24 and Prime 95 is much happier.

Still at 3.8 GHz 20x190 -- DDR3 1520 -- 1.264 Vcore -- 66C is the highest temp reported so far.
 
Very nice. I'm looking to buy a D0 i920 myself so I can get low temps.
 
Welp, that didn't work out too well. =) Prime 95 was having some rounding errors and Linpack was not stable. So, I turned vdroop off so I could have some more control over vcore and things are a bit more stable now. I just finished 20 passes of Linpack and now running Prime 95 again.

You could have more luck than me; having 1333 ram cut my oc (but then again I'm perfectly happy with 3.7 for all intents and purposes on stock volts) This Corsair didn't like running higher speeds but it could be because I didn't want to put too much juice through them, or it could be because I'm running with all dimm slots populated (never can tell).

Nice job though, hope you enjoy yours as much as I am mine now (especially after deciding to splurge on the SSD as my boot drive). Fast fast fast :D Brings a smile to my face to see the -bigadv crunching away :)
 
Tobit let me know how that asrock extreme motherboard works. I have the p55 asrock extreme for my i7 860 system but i'm going to be building another i7 920 system soon, I just have to wait for the old checking account to recharge ( bought skis instead, doh!).
 
(not to jack, just to offer my own opinion as a fellow ASRock x58 Extreme owner)
*I* can say IMHO it's a completely kickass board. Great design, excellent layout, tons of features...great bios, awesome price. IMO it's definitely the best low to mid range x58 board you can buy (especially if you're in the sub-$200 range).

(also not to thread jack and divert but here's a few pics as promised of my new 'D' for Team 33 as well :))
IMG_0424_1.jpg

IMG_0423_1.jpg

could sleeve some cables...eh, I just wanted to get it done. Happy with the results and love the K7B about as much as I love my V1000.
 
Looking good man, I am currently running Linpack @ 3.990 GHz - DDR3 1560 and half way through a 20 unit run @ 15K size. =)
 
Oh baby, it worked.. time to cook some prime 95 for awhile.

ss2.png
 
Running Prime 95 overnight and, if it is still running when I wake up in the morning, it'll be time to start folding. :cool:
 
For a while my goal was to keep my threat list from being full of 10 people. I don't think I'm going to be able to do that for a while. There are currently 17 people who are making more ppd with less total points than me, and you will soon make 18 on that list.
 
Sheesh, my goal is just to keep my spot at 228, and i'm pushing 7k plus to stay THERE!!
 
Folding has begun! I am showing 2m 44s frame times with -smp 8 on 1920 pernt A2's for 10115 PpD. I think that is pretty good. :)
 
my goal is to.. um.. shit.. what is my goal people?


nice overclock btw tobit.. 4 ghz at 1.28v is nuts.. never seen anyone reach 4ghz under 1.4v stable before..
 
Folding has begun! I am showing 2m 44s frame times with -smp 8 on 1920 pernt A2's for 10115 PpD. I think that is pretty good. :)
Yep, and running -bigadv you should easily hit 20kPPD is my minimal estimate. :cool:
 
Yep, and running -bigadv you should easily hit 20kPPD is my minimal estimate. :cool:

My i7's @3.9Ghz do a bigadv at ~33 MpF.
That gives me a PF of 62%.
That gives me ~11k without the bonus and ~25k PpD with bonus.

I think the bigadv gives you slightly better PpD than the standard so your about the right times with them.

Luck ............ :D
 
Machine is running absolutely flawless. I just started folding with the GTX 260 on the same box via WINE and there is no slow down whatsoever
to the native Linux SMP client. I've never had a system this stable @ 4GHz under native Linux doing everything it is doing. The next test, of course,
is -bigadv stability once I finish my 10 A2's. I could try and run one now but I'd much rather wait til I am eligible for the bonus.

Gentoo Linux - Extremely minimal install, no GUI
NVIDIA 195.30 Beta Driver
CUDA 2.3 32-Bit Toolkit

Kernel:
Code:
tobit@ganymede ~ $ uname -a
Linux ganymede 2.6.32-zen4 #2 ZEN SMP PREEMPT Wed Jan 6 04:23:07 EST 2010 x86_64
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz GenuineIntel GNU/Linux

ss3.jpg
 
my goal is to.. um.. shit.. what is my goal people?

To keep up with Tobit on the awesome [H]ardware scale...;)

@ Tobit - that is a badass case you've got yourself there. No lack of breathing room for any of your components in that thing! Very nice...
 
To keep up with Tobit on the awesome [H]ardware scale...;)
Yeah, but I bet he is eating betting than me. This month, it's peanut butter sammiches and water only. I'm so broke this month, I can't even afford jelly for a real PB&J. :p
 
I prefer PB to PBJ myself. Even better when it's a grilled PB and it gets all warm and gooey. [mmm hungry] :)

Nice job on the build and oc Tobit. ;)

I'm going to rework my oc later; I was an oc n00b on the p35/p45 boards, now the x58 board I've had to re-learn some things...couple of the oc settings were throwing me for a loop. I just know there's *gotta* be a way to go higher even on my ram (obviously by lowering the divider to run within it's oc range). I just gotta have more patience I suppose. I think I need to fart around with the QPI and uncore more.

I had a -bigadv Core FF (255) on me overnight...was around 35% done. That wasn't a pleasant thing to wake up to. :( I think it's because I had the VM ram set to 4.6 instead of 4.8+ so I changed it to 5gb this morning.
 
Zero, I believe three things were the key to my success with this board:

  • Disabling Vdroop
  • Setting QPI Voltage to 1.34V -- I was hesitant with this much at first but as soon as I did, the results were "OMG, wow!"
  • Setting the multiplier to 21x -- Despite the BIOS screen saying that 20x was the limit, I was actually able to set the multiplier.
The above was in order resulting in my final ~4 GHz epiphany. RAM timings also played a huge part as I noted earlier in the thread. However, I haven't done -bigadv's yet so the jury is still out but everything is looking really good.

Edit: there were some other voltages I had tweaked as well if you want/need the full run down.
 
Hmm, maybe the vdroop being enabled is my problem. :eek:
I left some of the stuff on auto and tweaked others.
Using this as a rough guide, I tried
Method #2: Quick and dirty method for 4ghz aka screw efficiency

Set your ioh and ich to 1.2, your vdimm to 1.65, your cpu pll to 1.88, and your qpi/uncore to 1.35.
For D0 users set your vcore to 1.275 and for c0/c1 users set your vcore to 1.4 Bclk to 190/191 or 210/211 and multiplier to 21 and 19 respectively. Check for prime stability. D0s should be fine, but c0/c1 still may not make it, at this point your temps may be too high if you're not on water so I suggest you start working backward in order to hit a much lower vcore or use method 3.

The guide was clearly written with ddr3 1600 in mind (which runs at 1.65vdimm); my 1333 1.5vdimm Corsair does not like the juice. Running them 1.56 they would disappear dimm to dimm during post (I'd go down to 10gb ram or 8gb ram or even 6gb ram and in the bios 2-3 dimm slots would appear as "empty"). I believe the bios for our board goes from 1.4something to 1.56.

I *believe* I did jump the qpi (Vtt) to 1.34 as you said, but then I was still having issues so I threw in the towel just to get things done. I really need to go in there and take the qpi and uncore off auto because I think that could be another one of the reasons I'm having issues as well. Basically either the board wouldn't post (and the LED would flash a few codes that escape me ATM), the ram would disappear (so I'd go back into the bios and change something else), or it would crash booting Windows. I did get the ram to boot at 1600 so I think the ram can handle the speed, and I had the vdimm at 1.56x and it seemed ok...I think it was just a qpi/uncore issue that was causing my post or boot to fail.

I also read one of the threads (via Google search) in the [H] OC/Cooling subforum that mentioned raising QPI and how it fixes stability putting QPI 1.3 or higher...I'm aiming for something like you...decent oc on safe volts. (your volts are definitely safe range).

Thanks for the info! I appreciate it :) It was nice to be able to bump the multi to 21, I did notice that. ;)
 
Zero, as I am running DDR3 1600 it may not help you much but, I am finishing up a WU in about 10m and will be shutting down the system briefly to do some final wire management and hook up the case switches. While the machine is down, I will write down all my OC numbers and post this in this thread.
 
Back
Top