[ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More

[msTrix]

Hello everyone,can somebody help me with RX580 8gb Saphire NITRO+, I only get 930mh/s on XMR  my clock is 1200 gpu  950mV   and  2100 memmory 900mV autoconfig is L8+8

guess you have to play with your memory clockings, guess lower might help you here, as well as your GPU clock might be a little low. Maybe start with the default clocks and see what that gives. and Try without the L?

[VasilyS]

I'm really surprised by the performance of your miner! It gives hashrate 440 h/s while XMRStack on the same overclocking gives only 370 h/s! Thanks a lot!

After some time I switched again to XMRStack because of its better stability. Your miner needs more sophisticated adjustments. It is suitable to have stable configurations for popular GPUs inside your software.

[msTrix]

I'm really surprised by the performance of your miner! It gives hashrate 440 h/s while XMRStack on the same overclocking gives only 370 h/s! Thanks a lot!

After some time I switched again to XMRStack because of its better stability. Your miner needs more sophisticated adjustments. It is suitable to have stable configurations for popular GPUs inside your software.

  atm  stak is definitly not the best / easiest one to configure, and with less tweaking u ll get alot more hash and hash/watt from TRM. TRM needs a bit other clockings than common, but 20% more hash (atleast reading above on same clockings) is worth it 

[ku4eto]

I'm really surprised by the performance of your miner! It gives hashrate 440 h/s while XMRStack on the same overclocking gives only 370 h/s! Thanks a lot!

After some time I switched again to XMRStack because of its better stability. Your miner needs more sophisticated adjustments. It is suitable to have stable configurations for popular GPUs inside your software.

  atm  stak is definitly not the best / easiest one to configure, and with less tweaking u ll get alot more hash and hash/watt from TRM. TRM needs a bit other clockings than common, but 20% more hash (atleast reading above on same clockings) is worth it 

The 15% power consumption reduction alone is worth it to switch over from XMR-Stak. Thats why i did it.

I'm really surprised by the performance of your miner! It gives hashrate 440 h/s while XMRStack on the same overclocking gives only 370 h/s! Thanks a lot!

After some time I switched again to XMRStack because of its better stability. Your miner needs more sophisticated adjustments. It is suitable to have stable configurations for popular GPUs inside your software.

Stability with TRM is actually A LOT better than XMR-Stak. With XMR-Stak, my rig would BSOD once from 1 day to 5 days. Not to mention the massive amounts of rejected shares.
With TRM, i can run it without issues for a whole week. And i have like 5 rejected shares for 3 days, compared to 30 shares for the same period on XMR-Stak.

Also, TRM DO have auto configuration, but its not the best. And the amount of testing is like... 3-4 combinations total for GPU type.

[bbvedf]

I also like the stability of TRM. I have 4 RX580 8GB, Sapphire Pulse. For some reason they do not have the same performance, so I use 2 GPUs with CNv8 and another 2 GPUs with PHI2.
Zero problem.
I'm waiting to see what the next version surprises us with

[pbfarmer]

EDIT: I always run latest drivers - never had a problem w/ them other than when using stak/derivatives (TRM is an entirely separate codebase, so doesn't suffer from the same issues.)  It should be noted that the latest Adrenaline drivers allow setting P0-5 now, which should remove the need for PPT.  Sadly, based on my testing it would seem they forgot to extend this capability to the mem power states, which also act as voltage floors to the core.

https://www.dropbox.com/s/ibxcdlrgkm82ccg/OverdriveNTool%200.2.8beta1.7z?dl=1
Tried the ODN 2.8 beta?

Not yet - but the P0-2 mem states weren't even editable in Wattman...

[pbfarmer]

Just a small update on how my small farm is doing, I been running this miner for a week now pretty stable with almost no issues. Not sure how I can check for the percentage of rejected and accepted shares, but all the numbers seem to have evened out. All my miners have been running almost all the same across the board. Maybe a few points of difference between them but they can all hit at least 1900 sol/s for my vega 56's.

A few days ago I read a reddit post of a dude saying he was able to hit 2000 sol/s on his vega 56 with an extremely reduced power draw. He was using the recently released adrenalin drivers but didn't give out much more information. So far I have downloaded the second to latest drivers and have been able to closely replicate the results i had with using the soft powerplay table mod and using overdriveN tool. It does feel like there is room for fine tuning but i wouldn't know where to start. Ideally I would like to hit the 2000 sol/s using 115w on gpu-z. Maybe not that low but having a system total power draw of 500w or under for 3 vega 56 would be very nice.

Haha - "sol/s"...  someone's been mining ZEC?

I have mostly 64s, but my one 56 is running around 1950 H/s at sub-160W ATW.  It doesn't seem to be the best asic quality, and is a bit old, so I would expect better from a larger sample set.  I also flashed to 64 rom a while ago, which is useless for CNv2 (unless you don't care about power use,) so even lower power use should be expected on a stock rom given that 56 mem runs at a lower voltage, while it's tighter mem timings allow similar results at lower clocks.

For 2K H/s (and best efficiency,) I would suggest a voltage setting of around 840mv (or less if you can get away w/ it,) while targeting a 1400 effective core clock.  I say effective, because the low voltage will almost certainly cause significant core clock throttling, so you will likely have to set your P7 clock much higher than 1400 to get to that level while under a mining load.  For example, I run a 1450 @ 835mv P7 setting, and only get a ~1360 effective clock out of it.  On some of my 64s, my clock setting ranges from 1430-1500 (@ 815-850mv) to get to ~1400 effective.  As for mem clock, I believe you're looking for a ~950Mhz setting for a 56 - higher is obviously better, if possible.

Regarding the PPT, it really is only necessary for two reasons.  The first is to lower your P0-5 power state voltages to allow undervolting P6/7 appropriately.  This is necessary via PPT, because P0-5 can't be set w/ ODNT/Wattman/etc, but power state voltage settings must be in ascending order.  In other words, w/o PPT, the floor for P6/7 voltage is whatever the stock P5 voltage is set to - around 1.1v iirc.  With that in mind, I set my P0-P5 @ 800-805mv via PPT, then tune P7 (while miner is running) as appropriate via ODNT. 1450 @ 840mv is prob a good P7 starting point while tuning.

The second purpose of PPT is to lock in your final settings once you're done tuning, as it seems the drivers don't seem to always honor the ODNT voltage settings on load, but if those same settings are written to PPT, they 'stick'.  This also technically removes the need for loading ODNT profiles at startup, though it doesn't hurt anything to continue to do so.

So in short, your steps are:

  1. Create a first PPT simply to drop your voltage floor
  2. Tune while miner is running to get to an appropriate/stable P7
  3. Recreate PPT using final P6/7 values

A couple other notes:

 - a cn_config setting (for trm) of 15+15 seems to be better than 16+14, at least for these lower clocks

 - CNv2, esp w/ the TRM rocketship, is an unstable beast power wise.  Settings which may seem stable at first (even for hours,) may lead to a crash at some point due to power starvation.  Even once you think you've found the correct settings, expect to have to dial voltages up (or clocks down) by increments of 5-10 over time to get to a truly stable setup.

 - You can create PPTs via ODNT, by running in admin mode, then clicking on the GPU icon (top left) and selecting 'PPTable Editor'.

 - As a starting point, here is my ODNT profile for my 56, though every card, properly tuned, will have different P7 values (also note my mem clock setting is for a 64 bios):

Code:

[Profile_66]
Name=cn8-srvega56-s-r1-2
GPU_P0=852;800
GPU_P1=991;801
GPU_P2=1084;802
GPU_P3=1100;803
GPU_P4=1125;804
GPU_P5=1150;805
GPU_P6=1350;815
GPU_P7=1450;835
Mem_P0=167;800
Mem_P1=500;800
Mem_P2=800;802
Mem_P3=1107;830
Fan_Min=300
Fan_Max=4000
Fan_Target=50
Fan_Acoustic=0
Power_Temp=80
Power_Target=0

EDIT: I always run latest drivers - never had a problem w/ them other than when using stak/derivatives (TRM is an entirely separate codebase, so doesn't suffer from the same issues.)  It should be noted that the latest Adrenaline drivers allow setting P0-5 now, which should remove the need for PPT.  Sadly, based on my testing it would seem they forgot to extend this capability to the mem power states, which also act as voltage floors to the core.

how you manage to get mem P3 other value than P4 Core? i tried to set mem P3 at 830 but than Core P4 will set also to 830.

and are all my cards shit that i cant reach stable 1450Mhz also with 850mV (only 1430 is stable)

my main goal is saving energy (to put another Vega into my rig with 1500W PSU)

mem P3 will always be set to P4 core in PPT.  You can override this in ODNT w/ a profile later *if necessary*, though it shouldn't really ever be necessary.  'Mem voltage' in PPT and profiling tools (ODNT, wattman, etc) is simply a floor for core (and soc) voltage.  If it's set below your core voltage, it's pretty much inconsequential (though I'm not certain if it also sets a floor for AVFS feature, so a reasonable number may still be desireable.)  On the other hand, if your Mem P3 voltage setting is above your core P7, then you will run core at that voltage instead.  Your actual mem voltage is fixed in the BIOS.

regarding stability - are you trying to get to effective 1450 @ 850, or your setting is 1450?  If it's the former, that's likely just not possible.  If it's the latter, i wouldn't focus so much on the setting, but rather look at the effective.  I have some cards that drop 100Mhz under load (and therefore need to be set ~1500,) while others only drop only 25Mhz (and can be set closer to your 1430 number.)

[pbfarmer]

Just a small update on how my small farm is doing, I been running this miner for a week now pretty stable with almost no issues. Not sure how I can check for the percentage of rejected and accepted shares, but all the numbers seem to have evened out. All my miners have been running almost all the same across the board. Maybe a few points of difference between them but they can all hit at least 1900 sol/s for my vega 56's.

A few days ago I read a reddit post of a dude saying he was able to hit 2000 sol/s on his vega 56 with an extremely reduced power draw. He was using the recently released adrenalin drivers but didn't give out much more information. So far I have downloaded the second to latest drivers and have been able to closely replicate the results i had with using the soft powerplay table mod and using overdriveN tool. It does feel like there is room for fine tuning but i wouldn't know where to start. Ideally I would like to hit the 2000 sol/s using 115w on gpu-z. Maybe not that low but having a system total power draw of 500w or under for 3 vega 56 would be very nice.

Haha - "sol/s"...  someone's been mining ZEC?

I have mostly 64s, but my one 56 is running around 1950 H/s at sub-160W ATW.  It doesn't seem to be the best asic quality, and is a bit old, so I would expect better from a larger sample set.  I also flashed to 64 rom a while ago, which is useless for CNv2 (unless you don't care about power use,) so even lower power use should be expected on a stock rom given that 56 mem runs at a lower voltage, while it's tighter mem timings allow similar results at lower clocks.

For 2K H/s (and best efficiency,) I would suggest a voltage setting of around 840mv (or less if you can get away w/ it,) while targeting a 1400 effective core clock.  I say effective, because the low voltage will almost certainly cause significant core clock throttling, so you will likely have to set your P7 clock much higher than 1400 to get to that level while under a mining load.  For example, I run a 1450 @ 835mv P7 setting, and only get a ~1360 effective clock out of it.  On some of my 64s, my clock setting ranges from 1430-1500 (@ 815-850mv) to get to ~1400 effective.  As for mem clock, I believe you're looking for a ~950Mhz setting for a 56 - higher is obviously better, if possible.

Regarding the PPT, it really is only necessary for two reasons.  The first is to lower your P0-5 power state voltages to allow undervolting P6/7 appropriately.  This is necessary via PPT, because P0-5 can't be set w/ ODNT/Wattman/etc, but power state voltage settings must be in ascending order.  In other words, w/o PPT, the floor for P6/7 voltage is whatever the stock P5 voltage is set to - around 1.1v iirc.  With that in mind, I set my P0-P5 @ 800-805mv via PPT, then tune P7 (while miner is running) as appropriate via ODNT. 1450 @ 840mv is prob a good P7 starting point while tuning.

The second purpose of PPT is to lock in your final settings once you're done tuning, as it seems the drivers don't seem to always honor the ODNT voltage settings on load, but if those same settings are written to PPT, they 'stick'.  This also technically removes the need for loading ODNT profiles at startup, though it doesn't hurt anything to continue to do so.

So in short, your steps are:

  1. Create a first PPT simply to drop your voltage floor
  2. Tune while miner is running to get to an appropriate/stable P7
  3. Recreate PPT using final P6/7 values

A couple other notes:

 - a cn_config setting (for trm) of 15+15 seems to be better than 16+14, at least for these lower clocks

 - CNv2, esp w/ the TRM rocketship, is an unstable beast power wise.  Settings which may seem stable at first (even for hours,) may lead to a crash at some point due to power starvation.  Even once you think you've found the correct settings, expect to have to dial voltages up (or clocks down) by increments of 5-10 over time to get to a truly stable setup.

 - You can create PPTs via ODNT, by running in admin mode, then clicking on the GPU icon (top left) and selecting 'PPTable Editor'.

 - As a starting point, here is my ODNT profile for my 56, though every card, properly tuned, will have different P7 values (also note my mem clock setting is for a 64 bios):

Code:

[Profile_66]
Name=cn8-srvega56-s-r1-2
GPU_P0=852;800
GPU_P1=991;801
GPU_P2=1084;802
GPU_P3=1100;803
GPU_P4=1125;804
GPU_P5=1150;805
GPU_P6=1350;815
GPU_P7=1450;835
Mem_P0=167;800
Mem_P1=500;800
Mem_P2=800;802
Mem_P3=1107;830
Fan_Min=300
Fan_Max=4000
Fan_Target=50
Fan_Acoustic=0
Power_Temp=80
Power_Target=0

EDIT: I always run latest drivers - never had a problem w/ them other than when using stak/derivatives (TRM is an entirely separate codebase, so doesn't suffer from the same issues.)  It should be noted that the latest Adrenaline drivers allow setting P0-5 now, which should remove the need for PPT.  Sadly, based on my testing it would seem they forgot to extend this capability to the mem power states, which also act as voltage floors to the core.

NICE TUTORIAL.

i have vega 56 with 64 bios. Are you sure that V8 algo is better to return stock bios? i have referent vega 56 with samsung mem and now i  u se 1095/1100 mhz mem

The main point of the 64 flash was to get 1150MHz+ mem speeds (which was consequential for CN/v1 while still maintaining efficiency.)   For CNv2, core power consumption has increased significantly, so if you're not comfortable running ~210W+ per vega, you'll need to drop your mem speed to 1107 or below (which in effect drops your SOC clock) to get total power consumption down.  Total throughput of 1107MHz @ 64 timings seems to be similar to 950MHz @ 56 timings based on other reported hashrates I've seen, which then means you're just burning extra power (though not much) for similar results.

[Goliaph]

if your 56th can work stable with 930+MHz - you have to keep 56th bios =) If not - 64th bios will allow you achieve 1100MHz stable and get more hashes. ( 56th @ 930 ~ 56th -> 64th @ 1100 with CN algos)

As for me - i've noticed that mem speed for V8 gives poor hashrate growth, so my Vegas are at 1070MHz and wattage difference i'm using with core speed =)

[Doucesti]

Hi it's me again, I bought a 570 4gb.
Now in my system I have a vega56 and this new 570 4gb strix.
Config is 7+7,16+14 and give me the best results (I tried everything else)

No bios mod and no clocking, no mem strap.
570 is in slot1 (pci express 3.0 8x) and vega 56 is in slot2 (pci expresse 3.0 16x) with a hdmi connected.

I'm getting only 638 and 1780h/s, is this normal? What to try beside mem strap, bios mod and clocking?? Thanks for your help!

[ku4eto]

Hi it's me again, I bought a 570 4gb.
Now in my system I have a vega56 and this new 570 4gb strix.
Config is 7+7,16+14 and give me the best results (I tried everything else)

No bios mod and no clocking, no mem strap.
570 is in slot1 (pci express 3.0 8x) and vega 56 is in slot2 (pci expresse 3.0 16x) with a hdmi connected.

I'm getting only 638 and 1780h/s, is this normal? What to try beside mem strap, bios mod and clocking?? Thanks for your help!

Thats... the main thing that you need to try.

[Doucesti]

Thats... the main thing that you need to try.

Clocking doesnt get me far, I'll try mem strap if you suggest me some guide/instructions.
Btw how do I give some merit/rep points?
thanks

[nordmann666]

Hi it's me again, I bought a 570 4gb.
Now in my system I have a vega56 and this new 570 4gb strix.
Config is 7+7,16+14 and give me the best results (I tried everything else)

No bios mod and no clocking, no mem strap.
570 is in slot1 (pci express 3.0 8x) and vega 56 is in slot2 (pci expresse 3.0 16x) with a hdmi connected.

I'm getting only 638 and 1780h/s, is this normal? What to try beside mem strap, bios mod and clocking?? Thanks for your help!

disable Crossfire Auto link und ulps in registry (EnableULPS=0 and EnableCrossFireAutoLink=0)
set compute mode for polaris card in Radeon Settings (from "gaming" to "computing")

but important...check the guides...this two things are just two from x important things you have to check

[carlosmonaco]

Hello everyone,
I tried to use this miner for a while on my rigs but I can't get them stable.
Using windows 10 with 18.6.1 drivers ( srb almost stable)

I use only reference card with blower, vega 56 and vega 64 and some vega 56 with 64 bios .
Im using these PPT for all cards Core P0-P6 : 900mv Mem P0-P2 : 900mV

Most of the card are running 1395 core 945 Mem for Vega56  and 1395 core 1090 mem for Vega 64 . (925-900 for some 56, 1025 for some 64)
Best one are running 870mv core 850 mv Mem, bad ones 950 core and 900-930 mem.

The best hashrate I can get with that settings are 2020h/s for vega 64 but average is around 1950h/s for 64 and 1900h/s for Vega 56.

Someone can help me to find best settings for reference card , PPT ? overdriventool settings ? Miner setting?

Thanks

[Doucesti]

...

disable Crossfire Auto link und ulps in registry (EnableULPS=0 and EnableCrossFireAutoLink=0)
set compute mode for polaris card in Radeon Settings (from "gaming" to "computing")

but important...check the guides...this two things are just two from x important things you have to check

Thanks for your help, did both but it didnt change anything.
Overclocking gives me +2-4% max before becoming unstable, memory and clock, even after rebooting.
I'm really welcoming any important thing you suggest me to check!

[smeads]

I've been asked to include your miner, in my automated mining software (www.profitbotpro.com); however, I have a few questions:

#1 When will your miner support other CN algo's? The 1st page mentions CN8, but not any of the others.
#2 When will you have a release-ready version? It seems you folks may still be in beta?

Of course, there's 35 pages of forums.... so maybe I missed some information.

Have a good day.

Randy

[nordmann666]

Just a small update on how my small farm is doing, I been running this miner for a week now pretty stable with almost no issues. Not sure how I can check for the percentage of rejected and accepted shares, but all the numbers seem to have evened out. All my miners have been running almost all the same across the board. Maybe a few points of difference between them but they can all hit at least 1900 sol/s for my vega 56's.

A few days ago I read a reddit post of a dude saying he was able to hit 2000 sol/s on his vega 56 with an extremely reduced power draw. He was using the recently released adrenalin drivers but didn't give out much more information. So far I have downloaded the second to latest drivers and have been able to closely replicate the results i had with using the soft powerplay table mod and using overdriveN tool. It does feel like there is room for fine tuning but i wouldn't know where to start. Ideally I would like to hit the 2000 sol/s using 115w on gpu-z. Maybe not that low but having a system total power draw of 500w or under for 3 vega 56 would be very nice.

Haha - "sol/s"...  someone's been mining ZEC?

I have mostly 64s, but my one 56 is running around 1950 H/s at sub-160W ATW.  It doesn't seem to be the best asic quality, and is a bit old, so I would expect better from a larger sample set.  I also flashed to 64 rom a while ago, which is useless for CNv2 (unless you don't care about power use,) so even lower power use should be expected on a stock rom given that 56 mem runs at a lower voltage, while it's tighter mem timings allow similar results at lower clocks.

For 2K H/s (and best efficiency,) I would suggest a voltage setting of around 840mv (or less if you can get away w/ it,) while targeting a 1400 effective core clock.  I say effective, because the low voltage will almost certainly cause significant core clock throttling, so you will likely have to set your P7 clock much higher than 1400 to get to that level while under a mining load.  For example, I run a 1450 @ 835mv P7 setting, and only get a ~1360 effective clock out of it.  On some of my 64s, my clock setting ranges from 1430-1500 (@ 815-850mv) to get to ~1400 effective.  As for mem clock, I believe you're looking for a ~950Mhz setting for a 56 - higher is obviously better, if possible.

Regarding the PPT, it really is only necessary for two reasons.  The first is to lower your P0-5 power state voltages to allow undervolting P6/7 appropriately.  This is necessary via PPT, because P0-5 can't be set w/ ODNT/Wattman/etc, but power state voltage settings must be in ascending order.  In other words, w/o PPT, the floor for P6/7 voltage is whatever the stock P5 voltage is set to - around 1.1v iirc.  With that in mind, I set my P0-P5 @ 800-805mv via PPT, then tune P7 (while miner is running) as appropriate via ODNT. 1450 @ 840mv is prob a good P7 starting point while tuning.

The second purpose of PPT is to lock in your final settings once you're done tuning, as it seems the drivers don't seem to always honor the ODNT voltage settings on load, but if those same settings are written to PPT, they 'stick'.  This also technically removes the need for loading ODNT profiles at startup, though it doesn't hurt anything to continue to do so.

So in short, your steps are:

  1. Create a first PPT simply to drop your voltage floor
  2. Tune while miner is running to get to an appropriate/stable P7
  3. Recreate PPT using final P6/7 values

A couple other notes:

 - a cn_config setting (for trm) of 15+15 seems to be better than 16+14, at least for these lower clocks

 - CNv2, esp w/ the TRM rocketship, is an unstable beast power wise.  Settings which may seem stable at first (even for hours,) may lead to a crash at some point due to power starvation.  Even once you think you've found the correct settings, expect to have to dial voltages up (or clocks down) by increments of 5-10 over time to get to a truly stable setup.

 - You can create PPTs via ODNT, by running in admin mode, then clicking on the GPU icon (top left) and selecting 'PPTable Editor'.

 - As a starting point, here is my ODNT profile for my 56, though every card, properly tuned, will have different P7 values (also note my mem clock setting is for a 64 bios):

Code:

[Profile_66]
Name=cn8-srvega56-s-r1-2
GPU_P0=852;800
GPU_P1=991;801
GPU_P2=1084;802
GPU_P3=1100;803
GPU_P4=1125;804
GPU_P5=1150;805
GPU_P6=1350;815
GPU_P7=1450;835
Mem_P0=167;800
Mem_P1=500;800
Mem_P2=800;802
Mem_P3=1107;830
Fan_Min=300
Fan_Max=4000
Fan_Target=50
Fan_Acoustic=0
Power_Temp=80
Power_Target=0

EDIT: I always run latest drivers - never had a problem w/ them other than when using stak/derivatives (TRM is an entirely separate codebase, so doesn't suffer from the same issues.)  It should be noted that the latest Adrenaline drivers allow setting P0-5 now, which should remove the need for PPT.  Sadly, based on my testing it would seem they forgot to extend this capability to the mem power states, which also act as voltage floors to the core.

how you manage to get mem P3 other value than P4 Core? i tried to set mem P3 at 830 but than Core P4 will set also to 830.

and are all my cards shit that i cant reach stable 1450Mhz also with 850mV (only 1430 is stable)

my main goal is saving energy (to put another Vega into my rig with 1500W PSU)

mem P3 will always be set to P4 core in PPT.  You can override this in ODNT w/ a profile later *if necessary*, though it shouldn't really ever be necessary.  'Mem voltage' in PPT and profiling tools (ODNT, wattman, etc) is simply a floor for core (and soc) voltage.  If it's set below your core voltage, it's pretty much inconsequential (though I'm not certain if it also sets a floor for AVFS feature, so a reasonable number may still be desireable.)  On the other hand, if your Mem P3 voltage setting is above your core P7, then you will run core at that voltage instead.  Your actual mem voltage is fixed in the BIOS.

regarding stability - are you trying to get to effective 1450 @ 850, or your setting is 1450?  If it's the former, that's likely just not possible.  If it's the latter, i wouldn't focus so much on the setting, but rather look at the effective.  I have some cards that drop 100Mhz under load (and therefore need to be set ~1500,) while others only drop only 25Mhz (and can be set closer to your 1430 number.)

so if i understand you...after i have to set P7 Core to 860 (everything lower will result in instant crash or core speed 850MHz) i can also set Mem P3 to 860 cause it will not affect the power consumption?
and i tried P7 1400 with 830,840,850mv but nothing to get stable - after 860mv i can push P7 until 1460-1480 (effective 1375-1395 depends on card)

it´s most important for me to reach stable hs around 1900-1950 with lowest possible power consumption. with getting back to vega 56 bios i save 10W/card - thats good..but the cards need 160-170W - to much

[kerney666]

I've been asked to include your miner, in my automated mining software (www.profitbotpro.com); however, I have a few questions:

#1 When will your miner support other CN algo's? The 1st page mentions CN8, but not any of the others.
#2 When will you have a release-ready version? It seems you folks may still be in beta?

Of course, there's 35 pages of forums.... so maybe I missed some information.

Have a good day.

Randy

Hi Randy!

Yeah, we probably had expected to be including more variants at this point, but right now CNv8 is the only CN family algo. I believe we'll make a push in Jan though.

The beta status is more due to missing features rather than stability issues etc. I'd say the major remaining feature is pool failover support. With that added, I think we might drop the beta tag, it's almost a little silly that it's still around .

-- K

[pbfarmer]

mem P3 will always be set to P4 core in PPT.  You can override this in ODNT w/ a profile later *if necessary*, though it shouldn't really ever be necessary.  'Mem voltage' in PPT and profiling tools (ODNT, wattman, etc) is simply a floor for core (and soc) voltage.  If it's set below your core voltage, it's pretty much inconsequential (though I'm not certain if it also sets a floor for AVFS feature, so a reasonable number may still be desireable.)  On the other hand, if your Mem P3 voltage setting is above your core P7, then you will run core at that voltage instead.  Your actual mem voltage is fixed in the BIOS.

regarding stability - are you trying to get to effective 1450 @ 850, or your setting is 1450?  If it's the former, that's likely just not possible.  If it's the latter, i wouldn't focus so much on the setting, but rather look at the effective.  I have some cards that drop 100Mhz under load (and therefore need to be set ~1500,) while others only drop only 25Mhz (and can be set closer to your 1430 number.)

so if i understand you...after i have to set P7 Core to 860 (everything lower will result in instant crash or core speed 850MHz) i can also set Mem P3 to 860 cause it will not affect the power consumption?
and i tried P7 1400 with 830,840,850mv but nothing to get stable - after 860mv i can push P7 until 1460-1480 (effective 1375-1395 depends on card)

it´s most important for me to reach stable hs around 1900-1950 with lowest possible power consumption. with getting back to vega 56 bios i save 10W/card - thats good..but the cards need 160-170W - to much

Yes, you can set mem-p3 to anything <= core-p7 and it will not affect power consumption.  Or you can just leave it set to whatever you have in the PPT, as you will always be using your core-p7 mv while mining.

As for your stability issues - i would guess you're running up against SOC/controller power needs, rather than core.  A 5-10mv change in voltage probably wouldn't give you an extra 80+Mhz headroom for core, so it's more likely the 860mv is required for the 1107Mhz SOC (56 still runs 1107 for the top state despite the much lower mem clock iirc.)  If you really want lower power, you can try playing some tricks - like locking out mem-p3 and using the mem-p2 as your top state, which seems to use a tiered SOC clock, allowing something closer to the necessary <=950Mhz, which should further reduce power needs.  I've only taken a cursory look at this functionality tho, so can't say for sure whether it will work.

[livada]

mem P3 will always be set to P4 core in PPT.  You can override this in ODNT w/ a profile later *if necessary*, though it shouldn't really ever be necessary.  'Mem voltage' in PPT and profiling tools (ODNT, wattman, etc) is simply a floor for core (and soc) voltage.  If it's set below your core voltage, it's pretty much inconsequential (though I'm not certain if it also sets a floor for AVFS feature, so a reasonable number may still be desireable.)  On the other hand, if your Mem P3 voltage setting is above your core P7, then you will run core at that voltage instead.  Your actual mem voltage is fixed in the BIOS.

regarding stability - are you trying to get to effective 1450 @ 850, or your setting is 1450?  If it's the former, that's likely just not possible.  If it's the latter, i wouldn't focus so much on the setting, but rather look at the effective.  I have some cards that drop 100Mhz under load (and therefore need to be set ~1500,) while others only drop only 25Mhz (and can be set closer to your 1430 number.)

so if i understand you...after i have to set P7 Core to 860 (everything lower will result in instant crash or core speed 850MHz) i can also set Mem P3 to 860 cause it will not affect the power consumption?
and i tried P7 1400 with 830,840,850mv but nothing to get stable - after 860mv i can push P7 until 1460-1480 (effective 1375-1395 depends on card)

it´s most important for me to reach stable hs around 1900-1950 with lowest possible power consumption. with getting back to vega 56 bios i save 10W/card - thats good..but the cards need 160-170W - to much

Yes, you can set mem-p3 to anything <= core-p7 and it will not affect power consumption.  Or you can just leave it set to whatever you have in the PPT, as you will always be using your core-p7 mv while mining.

As for your stability issues - i would guess you're running up against SOC/controller power needs, rather than core.  A 5-10mv change in voltage probably wouldn't give you an extra 80+Mhz headroom for core, so it's more likely the 860mv is required for the 1107Mhz SOC (56 still runs 1107 for the top state despite the much lower mem clock iirc.)  If you really want lower power, you can try playing some tricks - like locking out mem-p4 and using the mem-p3 as your top state, which seems to use a tiered SOC clock, allowing something closer to the necessary <=950Mhz, which should further reduce power needs.  I've only taken a cursory look at this functionality tho, so can't say for sure whether it will work.

How you chg p4 mem in ODNT? only p3 in
How you change SOC in ODNT?
i use PPT generator but question is:
in ODNT i chg p3 mem etc 1100/860mv . what p4 mem use in ppt table? more = less ?
SOC on my vega56/64bios is 1200. Must change this?
http://imgbox.com/sRzuqn07

put your ppt table here for 56 and 64 .

now i use 940mhz/900mv 1500/900mv and i have 6*vega nitro+ hynix- 11600hr with 1080W from the wall or 11950Hr with 1150W for the wall.
ref card 56 samsung use 64 bios and 900mv and have 2030hr and vega 64 LE with 900mv have 2145hr