Departure (OP)
|
|
July 04, 2011, 03:14:33 AM Last edit: July 04, 2011, 04:39:25 AM by Departure |
|
Hey guys thought I would just throw out my settings and software to maybe help other that are in the same boat I was in a couple of weeks ago(new people). Operating System:Windows 7 X64 Aero Theme Disabled Drivers:11.6 or 11.7 preview Software:Phoenix 1.50(with 3% patch to phat kernal) Aoclbf: Vectors - HD5xx - phatk - Worksize(128), Aggression(7) or GUIminer: Miner(Phoenix with 3% patch to phat kernal), Flags(+k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128) GPU Clocks:Core: 910 or 880(hash rate bouces around more) Mem: 840 Volts: Leave OC switch on cards in default position, No need to overclock Cooling:60% Fan speed on cards Linda box fan @ second speed Temps:Hottest: 72c Coolest: 62c Hash Rate:432-455 MH/s per GPU Details:I currently have 3 x 6990 in one box, using a 890FX-UD7 board I was able to get good spacing between the cards, I also setup a linda box fan with cardboard wind tunnel directing the air straight onto the cards(not need but reduce the temps alot) Anyway get your self a copy of aoclbf front end, I suggest this because you can overclock/underclock your cards from the gui, and MSI after burn had faults when the 3rd card was put in.. Get your self a copy of the Phoenix 1.50 and apply the 3% mod in the kernal(open in text editor) I found for the 6990 cards the best memory clock setting is 840 anything below increases heat and is unstable and anything above just increases heat. also set your core clocks 910, so you should have all GPU's set to 910/840 while keeping the OC switch on the cards in its default position. in aoclbf tick vectors, 5HDxx+ , phatk and set your worksize to 128 and aggression 7, yes 7 because higher aggression will give you less MH/s and lower will give you less MH/s. Or if you prefer to use GUIminer or straight console the use these flags "-k phatk VECTORS BFI_INT WORKSIZE=128 AGGRESSION=7" also make sure to use drivers 11.6 or preview drivers 11.7 for each GPU you should get 432 MH/s and bounces to 455 MH/s back and forth, which brings a grand total of around 2600 MH/s to 2700 MH/s if you have 3 cards like me. having these core clocks set lower than most OC'ers and keeping the OC switch in its default posistion not only reduces cost due to using the standard voltage but also keeps your cards cooler, my 3 6990's never go above 70c(card fan speed at 60%) with the linda box fan wind tunnel(set to speed 2 out of 3). Of cause this is only a base for you to work from, you can adjust to your desire but I found this to be efficient and fast. 3 x 6990 SettupBoxfan(HeadLess)If you have any 6990 settings you would like to share, feel free to post them and im sure with every ones help we could come up with a optimal settings for these cards.
|
|
|
|
Jack of Diamonds
|
|
July 04, 2011, 04:18:19 AM |
|
If I OC without the switch turned on, anything past 880mhz makes the hashrate slower.
Doesn't matter if I put it at 881 or 945mhz, it doesn't help. Some sort of throttling comes in play. Not a big deal otherwise but some manufacturers may void the card warranty if the sticker shows evidence of tampering.
|
1f3gHNoBodYw1LLs3ndY0UanYB1tC0lnsBec4USeYoU9AREaCH34PBeGgAR67fx
|
|
|
Departure (OP)
|
|
July 04, 2011, 04:26:12 AM Last edit: July 04, 2011, 04:38:05 AM by Departure |
|
I don't know what brand of card you have but im running the PowerColor 6990 and they cover warranty on the OC switch(under the yellow sticker). Saying that .. with these setting you don't need to switch OC switch so the sticker can be left attached and un-tampered with. I will try the 880 core clock and see what happens as I haven't tested 880 core since I applyed the 3% phatk patch. Also the key here is setting the aggression to 7, Im not 100% sure what exactly aggression does, but anything lower or higher will reduce the hash rate.
Thanks for the info...
//Edit
Just tested with core 880 and for my cards the max hash rate was the same but bounces around alot more, bounces between 408, 432, 457 MH/s up and down all the time, If we could stop the bouncing and get it stable at 432 or 457 would be good.
|
|
|
|
Jack of Diamonds
|
|
July 04, 2011, 04:44:46 AM Last edit: July 04, 2011, 05:04:11 AM by Jack of Diamonds |
|
Tbh 910 core clock makes device 1 run 20-30c hotter than the other core which sits nicely at 65-80. Might be just a faulty card though. If you can help me solve this I could pay out a bounty.
|
1f3gHNoBodYw1LLs3ndY0UanYB1tC0lnsBec4USeYoU9AREaCH34PBeGgAR67fx
|
|
|
Departure (OP)
|
|
July 04, 2011, 05:30:12 AM |
|
wow that is a big difference for GPU1.... I am guessing the OC switch on the card is flicked to OC instead of default? check and double check your mem clocks for that GPU as they some times default to 1250 when under clocked more than 100Mhz than core clocks. Is it only the single 6990 card you have int he box? if you more than 1 and they are stacked try placing 1 half of a plastic peg in between the cards to increase air gap. Also im not after any bounty if anything of this works for you, I just dont want people to go through the same hassle of getting information that I had to go through.
|
|
|
|
Jack of Diamonds
|
|
July 04, 2011, 05:42:55 AM |
|
Nah, not the memory clock.
I gave up a long time ago trying to get those hashrates you mentioned, due to temp. problems.. Room is maybe 20c, other core runs typically at 70-75. Core 0 simply skyrockets in temperature even if it has a massive 500cfm/h fan pointed at it.
Tried various stress tests like Furmark, only bitcoin and phoenixminer practically kill gpu#0.
Still, nice guide.
|
1f3gHNoBodYw1LLs3ndY0UanYB1tC0lnsBec4USeYoU9AREaCH34PBeGgAR67fx
|
|
|
fitty
|
|
July 04, 2011, 06:06:25 AM |
|
Nah, not the memory clock.
I gave up a long time ago trying to get those hashrates you mentioned, due to temp. problems.. Room is maybe 20c, other core runs typically at 70-75. Core 0 simply skyrockets in temperature even if it has a massive 500cfm/h fan pointed at it.
Tried various stress tests like Furmark, only bitcoin and phoenixminer practically kill gpu#0.
Still, nice guide.
I'd RMA it if it's still under warranty. Tell them it crashes 15-20 minutes after you start gaming. That's not normal there's clearly something wrong with that chip. Those types of issues usually get worse over time.
|
|
|
|
Acejam
|
|
July 04, 2011, 04:54:53 PM |
|
Great info here. I tried using your settings in the latest version of GUIMiner - but I'm only able to get ~402 MHash/s on the 1st core, and ~380-395 Mhash/s on the 2nd core. (for 1 card)
I'm running with the overclock switch enabled. It should be noted that some manufacturer's ship the card with this switch enabled. For example, my brand new *sealed* in box Sapphire 6990's shipped with the overclock mode enabled, and they even had the yellow warning sticker on them! I verified this by using GPU-Z, and was able to tell the core clock was set to ~880.
One of my rigs has (3) 6990's in it on a MSI 890FXA-GD70 motherboard. I'm also running a Corsair AX1200 PSU in that rig. Are you worried about overusing / maxing out your PSU at all? In non-overclock mode, each card uses about ~375w, and in position 2 they use ~450w. (or so I've read)
375 x 3 = 1125 W 450 x 3 = 1350 W
It should be noted that I have (5) 6990's. Three of them are in a dedicated rig all running in non-OC mode. I have another card in my main desktop rig running in OC mode (Corsair 750W PSU), and then another card is waiting to be installed. I'd like to flip the OC switch on my dedicated mining rig, but I'm worried about not having enough power for 3 cards in OC mode. Thoughts?
|
|
|
|
Jack of Diamonds
|
|
July 04, 2011, 06:03:23 PM |
|
Well since you asked, IMO a Corsair AX1200 is not enough for 3 cards with the OC switch on. It will work because the PSU is extremely robust (it will draw up to 1500W despite it's specs) but you are putting a large strain on it when going over 100% of it's specified limit.
I have that exact same PSU in one of my rigs and it runs two 6990's fine OC'ed about 390-400mhash per core
Then one with a Coolermaster 850W supply (screenshots above) which acts really weird on 1st core. Highly doubt PSU has anything to do with card stability or temps but just throwing it out there. Core 0 goes batshit crazy and those rigs are identical except for the PSU.
|
1f3gHNoBodYw1LLs3ndY0UanYB1tC0lnsBec4USeYoU9AREaCH34PBeGgAR67fx
|
|
|
CanaryInTheMine
Donator
Legendary
Offline
Activity: 2352
Merit: 1060
between a rock and a block!
|
|
July 05, 2011, 05:42:25 PM |
|
Hey guys thought I would just throw out my settings and software to maybe help other that are in the same boat I was in a couple of weeks ago(new people).
Operating System: Windows 7 X64 Aero Theme Disabled
Drivers: 11.6 or 11.7 preview
Software: Phoenix 1.50(with 3% patch to phat kernal) Aoclbf: Vectors - HD5xx - phatk - Worksize(128), Aggression(7) or GUIminer: Miner(Phoenix with 3% patch to phat kernal), Flags(+k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128)
GPU Clocks: Core: 910 or 880(hash rate bouces around more) Mem: 840 Volts: Leave OC switch on cards in default position, No need to overclock
Cooling: 60% Fan speed on cards Linda box fan @ second speed
Temps: Hottest: 72c Coolest: 62c
Hash Rate: 432-455 MH/s per GPU
Details: I currently have 3 x 6990 in one box, using a 890FX-UD7 board I was able to get good spacing between the cards, I also setup a linda box fan with cardboard wind tunnel directing the air straight onto the cards(not need but reduce the temps alot) Anyway get your self a copy of aoclbf front end, I suggest this because you can overclock/underclock your cards from the gui, and MSI after burn had faults when the 3rd card was put in.. Get your self a copy of the Phoenix 1.50 and apply the 3% mod in the kernal(open in text editor) I found for the 6990 cards the best memory clock setting is 840 anything below increases heat and is unstable and anything above just increases heat. also set your core clocks 910, so you should have all GPU's set to 910/840 while keeping the OC switch on the cards in its default position. in aoclbf tick vectors, 5HDxx+ , phatk and set your worksize to 128 and aggression 7, yes 7 because higher aggression will give you less MH/s and lower will give you less MH/s. Or if you prefer to use GUIminer or straight console the use these flags "-k phatk VECTORS BFI_INT WORKSIZE=128 AGGRESSION=7" also make sure to use drivers 11.6 or preview drivers 11.7 for each GPU you should get 432 MH/s and bounces to 455 MH/s back and forth, which brings a grand total of around 2600 MH/s to 2700 MH/s if you have 3 cards like me. having these core clocks set lower than most OC'ers and keeping the OC switch in its default posistion not only reduces cost due to using the standard voltage but also keeps your cards cooler, my 3 6990's never go above 70c(card fan speed at 60%) with the linda box fan wind tunnel(set to speed 2 out of 3). Of cause this is only a base for you to work from, you can adjust to your desire but I found this to be efficient and fast. If you have any 6990 settings you would like to share, feel free to post them and im sure with every ones help we could come up with a optimal settings for these cards.
Departure, Thanks for the post! I can confirm your results. I've applied what you have posted and am seeing nearly identical results to your setup. However, my OC switch is NOT in the default position. I will try this with the OC switch in default in the next few days.
|
|
|
|
Jack of Diamonds
|
|
July 05, 2011, 07:52:30 PM |
|
Thanks for the post! I can confirm your results. I've applied what you have posted and am seeing nearly identical results to your setup. However, my OC switch is NOT in the default position. I will try this with the OC switch in default in the next few days.
Can you post back with results? I'm thinking AMD powertune is crippling the card if OC switch is not on. I get pretty much the same results as OP, very noticeable boost from the standard 330-340mhash per core to at least 400-420 (with the exception of the temperature thing) However, even at same clock rates, OC switch in position 1 "unlocks" the speed. In position 0 (default) the hashing rate just wont go past 370mhash/s or so. So the switch could be doing some sort of power limiting on some 6990's.
|
1f3gHNoBodYw1LLs3ndY0UanYB1tC0lnsBec4USeYoU9AREaCH34PBeGgAR67fx
|
|
|
GorgonSed
Newbie
Offline
Activity: 19
Merit: 0
|
|
July 06, 2011, 07:09:54 PM |
|
Thanks for the post! I can confirm your results. I've applied what you have posted and am seeing nearly identical results to your setup. However, my OC switch is NOT in the default position. I will try this with the OC switch in default in the next few days.
Can you post back with results? I'm thinking AMD powertune is crippling the card if OC switch is not on. I get pretty much the same results as OP, very noticeable boost from the standard 330-340mhash per core to at least 400-420 (with the exception of the temperature thing) However, even at same clock rates, OC switch in position 1 "unlocks" the speed. In position 0 (default) the hashing rate just wont go past 370mhash/s or so. So the switch could be doing some sort of power limiting on some 6990's. It definitely sounds like Powertune to me. Look at these links http://www.guru3d.com/article/radeon-6950-6970-review/24http://www.anandtech.com/show/4061/amds-radeon-hd-6970-radeon-hd-6950/8Perhaps you need to add some % to the default powertune. I would try in increments of 5% or so.
|
|
|
|
CanaryInTheMine
Donator
Legendary
Offline
Activity: 2352
Merit: 1060
between a rock and a block!
|
|
July 06, 2011, 07:31:30 PM |
|
Thanks for the post! I can confirm your results. I've applied what you have posted and am seeing nearly identical results to your setup. However, my OC switch is NOT in the default position. I will try this with the OC switch in default in the next few days.
Can you post back with results? I'm thinking AMD powertune is crippling the card if OC switch is not on. I get pretty much the same results as OP, very noticeable boost from the standard 330-340mhash per core to at least 400-420 (with the exception of the temperature thing) However, even at same clock rates, OC switch in position 1 "unlocks" the speed. In position 0 (default) the hashing rate just wont go past 370mhash/s or so. So the switch could be doing some sort of power limiting on some 6990's. It definitely sounds like Powertune to me. Look at these links http://www.guru3d.com/article/radeon-6950-6970-review/24http://www.anandtech.com/show/4061/amds-radeon-hd-6970-radeon-hd-6950/8Perhaps you need to add some % to the default powertune. I would try in increments of 5% or so. Interesting! You better have a rock-solid PSU with 6990s... Given this formula: Power Consumption =( (shaderUsage * shaderWeight) + (ropUsage * ropWeight) + (memoryUsage * memoryWeight) ) * clockspeed I think it should be possible to come up with "best" parameters to set these 69xx cards to.
|
|
|
|
CanaryInTheMine
Donator
Legendary
Offline
Activity: 2352
Merit: 1060
between a rock and a block!
|
|
July 06, 2011, 08:02:48 PM |
|
Thanks for the post! I can confirm your results. I've applied what you have posted and am seeing nearly identical results to your setup. However, my OC switch is NOT in the default position. I will try this with the OC switch in default in the next few days.
Can you post back with results? I'm thinking AMD powertune is crippling the card if OC switch is not on. I get pretty much the same results as OP, very noticeable boost from the standard 330-340mhash per core to at least 400-420 (with the exception of the temperature thing) However, even at same clock rates, OC switch in position 1 "unlocks" the speed. In position 0 (default) the hashing rate just wont go past 370mhash/s or so. So the switch could be doing some sort of power limiting on some 6990's. So, it looks like I have to have the OC switch turned on... Departure, would you be able to double check your switch positions? I did make a small adjustment however, I set the clocks to 920 instead of 910 (everything else being the same). BTW, except clock speed, other params must be set exactly as they have been described by Departure. If they are not, you won't reproduce these results. Anyway, with 920 instead of 910, I'm seeing a constant lower boundary of 428 and upper to 458 per GPU. It's typical to observe: 428->432->458 in what seems to be some sort of a pattern, but I'm not gonna spend anymore time on this pattern observation to try to figure it out... Hope this helps.
|
|
|
|
burningrave101
Newbie
Offline
Activity: 55
Merit: 0
|
|
July 08, 2011, 05:45:03 AM Last edit: July 08, 2011, 06:04:38 AM by burningrave101 |
|
I've been testing these settings shown here in this thread as well as others on my 6990 for the last two days using GUIMiner and Phoenix 1.50 along with all the kernel tweaks I could find and I'm not getting anywhere near 432-455Mh/s. At 910/840 clock speeds using the flags (-k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128) on Windows 7 x64 with the 11.7 CATs I'm getting about 407 Mh/s which is 25-48Mh/s less per core. So if you guys are actually getting speeds in the range of 432-455 Mh/s at 910Mhz there must be something else going on here allowing the higher hash rate other than just using the settings mentioned otherwise the results would be more replicable.
|
|
|
|
CanaryInTheMine
Donator
Legendary
Offline
Activity: 2352
Merit: 1060
between a rock and a block!
|
|
July 08, 2011, 06:36:22 AM |
|
I've been testing these settings shown here in this thread as well as others on my 6990 for the last two days using GUIMiner and Phoenix 1.50 along with all the kernel tweaks I could find and I'm not getting anywhere near 432-455Mh/s. At 910/840 clock speeds using the flags (-k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128) on Windows 7 x64 with the 11.7 CATs I'm getting about 407 Mh/s which is 25-48Mh/s less per core. So if you guys are actually getting speeds in the range of 432-455 Mh/s at 910Mhz there must be something else going on here allowing the higher hash rate other than just using the settings mentioned otherwise the results would be more replicable.
Is the OC switch on?
|
|
|
|
burningrave101
Newbie
Offline
Activity: 55
Merit: 0
|
|
July 08, 2011, 06:46:45 AM |
|
Is the OC switch on?
Yeah I have the OC switch on and the voltage set to 1.12v since 1.175v made no improvement in hash rate.
|
|
|
|
CanaryInTheMine
Donator
Legendary
Offline
Activity: 2352
Merit: 1060
between a rock and a block!
|
|
July 08, 2011, 06:59:21 AM |
|
Is the OC switch on?
Yeah I have the OC switch on and the voltage set to 1.12v since 1.175v made no improvement in hash rate. I didn't mess with voltage. Which 6990 do you have?
|
|
|
|
grid
Newbie
Offline
Activity: 42
Merit: 0
|
|
July 08, 2011, 07:56:50 AM |
|
Tbh 910 core clock makes device 1 run 20-30c hotter than the other core which sits nicely at 65-80.
Might be just a faulty card though. If you can help me solve this I could pay out a bounty.
On the underside of the card (PCB) are several screws with springs underneath. These screws control the pressure between the cooler and the GPU. On my 6970 a couple of them got loose during shipping. Had the same problem - one card was 20-30C hotter than the other one. After tightening the screws (carefully) both cards have the same temp profiles, except for minor differences resulting from positioning inside the case.
|
|
|
|
yetis
Member
Offline
Activity: 112
Merit: 10
|
|
July 08, 2011, 10:50:09 AM |
|
I've been testing these settings shown here in this thread as well as others on my 6990 for the last two days using GUIMiner and Phoenix 1.50 along with all the kernel tweaks I could find and I'm not getting anywhere near 432-455Mh/s. At 910/840 clock speeds using the flags (-k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128) on Windows 7 x64 with the 11.7 CATs I'm getting about 407 Mh/s which is 25-48Mh/s less per core. So if you guys are actually getting speeds in the range of 432-455 Mh/s at 910Mhz there must be something else going on here allowing the higher hash rate other than just using the settings mentioned otherwise the results would be more replicable.
I agree with that. I am running two Gigabyte 6990s + ANTEC HCP-1200 + W7 64bit + Sabertooth P67 B3 + i5-2400S and I've tested the above settings with 11.6, latest phatk, 3%-patch, -k phatk VECTORS BFI_INT AGGRESSION=7 WORKSIZE=128, didn't touch the AUSUM switch at all, running @ 910/840 Mhz, ... i couldn't reproduce the Mhashrate. GUI-Miner shows ~399.6 Mhash/s for each core. @ 910/625 Mhz all cores running @ 404,3 Mhash/s with -k phatk VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128. Switching back to my standard setting -> 870/625 Mhz = steady 385,7 Mhash/s on each core. That's enough for me. I came to the conclusion that it has something to do with the excellent cooling solution i saw in the second picture + AUSUM switch to overclocked position + possibly something special we don't know. If i could see a picture of the Mhashrate + settings + clocks for all three cards then i would believe it, when not i think it's a hoax.
|
|
|
|
|