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

[dragonmike]

Yes,i set "Smart tune" from "off" to "auto" and set --cn_config L22+22

Are you able to run cn_config at L24+24 or will it crash with the tighter timings? With stock timings L24+24 is the fastest config for flashed 56's.

[logicus]

i dont test L24+24,just test L28+28 (win 10 settings),next L22+22 and now rig mining with L22+22.Maybe this weekend will test some different settings.

[reaper7881]

is there anyway of displaying stats on network like xmrstak or srbminer web api thingies

[fmz89]

is there anyway of displaying stats on network like xmrstak or srbminer web api thingies

Yeah i need to, when i ser api_listen=127.0.0.1:4028 only show some text, not showing status miner

[fmz89]

After  testing TeamRedMiner 0.4.3 under MMP OS 2 (Ubuntu) ,the result is impressive:

TeamRedMiner 0.4.3 under MMP OS 2

 4xVega 56(Vega 64 bios) core 1050mHz/845mV memory 1100mHz/845mV  80kH/s @ 690W from wall





https://imgur.com/eHv9Cxj


P.S.
Under win 10  my best result is 78kH/s @ 770W from wall

770w from the wall your gpus run at 0.9v even you set on 845mv check hw monitor
Cause my 4vegas run at 0.9v 77khs 740w win10

[logicus]

Some new tests:

TeamRedMiner 0.4.3 under MMP OS 2 (Ubuntu)

 4xVega 56(Vega 64 bios) core 1050mHz/845mV(0.85mV) memory 1100mHz/845mV(0.85mV) L24+24 72kH/s @ 650W from wall


TeamRedMiner 0.4.3 under win 10 19.3.2   PPT  Mem_P3=1100;880   GPU_P7=1100;880

 4xVega 56(Vega 64 bios) core 1100mHz/850mV(0.8625mV) memory 1100mHz/850mV(0.8625mV) L22+22 76kH/s @ 700W from wall


TeamRedMiner 0.4.3 under win 10 19.3.2   PPT  Mem_P3=1100;850   GPU_P7=1100;850

 4xVega 56(Vega 64 bios) core 1100mHz/850mV(0.8313mV) memory 1100mHz/850mV(0.8313mV) L22+22 73kH/s @ 670W from wall

My flashed 56 likes L22+22 

[reaper7881]

Anyone got any settings for turt

Can't get  my vega56 back up to 18khs I did it once but it messed up and I lost the settings

Miner defaults to 28+28 for config but it won't go past 16khs
Ive done ddu and reinstalled the same driver but still same

[fmz89]

Anyone got any settings for turt

Can't get  my vega56 back up to 18khs I did it once but it messed up and I lost the settings

Miner defaults to 28+28 for config but it won't go past 16khs
Ive done ddu and reinstalled the same driver but still same

Flash it to bios 64 / 64 liquid, then regkey, overdrive tool 1100/1090/880, for more 20khs you need memory timming
And check it hw info/gpuz your gpu must be under 0.9v for better efficiency

[reaper7881]

Anyone got any settings for turt

Can't get  my vega56 back up to 18khs I did it once but it messed up and I lost the settings

Miner defaults to 28+28 for config but it won't go past 16khs
Ive done ddu and reinstalled the same driver but still same

Flash it to bios 64 / 64 liquid, then regkey, overdrive tool 1100/1090/880, for more 20khs you need memory timming
And check it hw info/gpuz your gpu must be under 0.9v for better efficiency

thanks ive managed to get it to 21.8khs stable with no hw errors using 1050w from wall with 6 vegas

[seefatlow]

Can someone help me figure out why my ODNT set mem voltage is not what is shown in HWInfo. Core voltage is consistent with set value but not mem voltage for unknown reasons. This kinda explains why my power draw is higher than the rest for the same hashrate. Also, my pool hashrate is consistently lower than my internal hashrate for TRTL algo. Any idea why?

Name=RX Vega 56
GPU_P0=852;805
GPU_P1=991;810
GPU_P2=1084;815
GPU_P3=1138;820
GPU_P4=1150;830
GPU_P5=1202;835
GPU_P6=1212;840
GPU_P7=1220;850
Mem_P0=167;805
Mem_P1=500;805
Mem_P2=800;815
Mem_P3=910;850

[SamAlackass]

Can someone help me figure out why my ODNT set mem voltage is not what is shown in HWInfo. Core voltage is consistent with set value but not mem voltage for unknown reasons. This kinda explains why my power draw is higher than the rest for the same hashrate. Also, my pool hashrate is consistently lower than my internal hashrate for TRTL algo. Any idea why?

Name=RX Vega 56
GPU_P0=852;805
GPU_P1=991;810
GPU_P2=1084;815
GPU_P3=1138;820
GPU_P4=1150;830
GPU_P5=1202;835
GPU_P6=1212;840
GPU_P7=1220;850
Mem_P0=167;805
Mem_P1=500;805
Mem_P2=800;815
Mem_P3=910;850

https://imgur.com/x6cCgcI
https://imgur.com/b0G16RA
https://imgur.com/n9xKXLP

That's how it is with Vegas, you can't change mem voltage. Try disabling p0 to p6 and see if you can get lower mV at the same clock or lower core clock a bit and see if it makes enough difference in consumption.

[pbfarmer]

Can someone help me figure out why my ODNT set mem voltage is not what is shown in HWInfo. Core voltage is consistent with set value but not mem voltage for unknown reasons. This kinda explains why my power draw is higher than the rest for the same hashrate. Also, my pool hashrate is consistently lower than my internal hashrate for TRTL algo. Any idea why?

Name=RX Vega 56
GPU_P0=852;805
GPU_P1=991;810
GPU_P2=1084;815
GPU_P3=1138;820
GPU_P4=1150;830
GPU_P5=1202;835
GPU_P6=1212;840
GPU_P7=1220;850
Mem_P0=167;805
Mem_P1=500;805
Mem_P2=800;815
Mem_P3=910;850

The so-called ‘memory’ voltage in profile tools (e.g. odnt, wattman) does not control the actual operating voltage of the memory package.  Instead, it is a floor to your core voltage, intended to prevent someone from inadvertently starving the SOC/mem controller (which uses the same power line as CUs) by lowering core voltage too much.  In other words, core voltage = max(coreV, ‘memV’).

Your actual mem package operating voltage is fixed in bios @ 1.25 for 56s, and 1.365 (iirc) for 64s.  FYI, this mem voltage increase is the main point of the 56->64 bios flash

[Zorg33]

It's better called Vddci which stands for I/O Voltage
"VDDCI is the I/O bus voltage (between memory and GPU core)"

source

[pbfarmer]

It's better called Vddci which stands for I/O Voltage
"VDDCI is the I/O bus voltage (between memory and GPU core)"

source

That would be true for any GPU w/ an independent MC/bus voltage, but as it's the physically the same as core voltage in this case, it's also Vddc.  Or as most people simply call it - core voltage.

[micax1]

Does it support R9 cards - like 280x 290 290x?

[seefatlow]

Can someone help me figure out why my ODNT set mem voltage is not what is shown in HWInfo. Core voltage is consistent with set value but not mem voltage for unknown reasons. This kinda explains why my power draw is higher than the rest for the same hashrate. Also, my pool hashrate is consistently lower than my internal hashrate for TRTL algo. Any idea why?

Name=RX Vega 56
GPU_P0=852;805
GPU_P1=991;810
GPU_P2=1084;815
GPU_P3=1138;820
GPU_P4=1150;830
GPU_P5=1202;835
GPU_P6=1212;840
GPU_P7=1220;850
Mem_P0=167;805
Mem_P1=500;805
Mem_P2=800;815
Mem_P3=910;850

The so-called ‘memory’ voltage in profile tools (e.g. odnt, wattman) does not control the actual operating voltage of the memory package.  Instead, it is a floor to your core voltage, intended to prevent someone from inadvertently starving the SOC/mem controller (which uses the same power line as CUs) by lowering core voltage too much.  In other words, core voltage = max(coreV, ‘memV’).

Your actual mem package operating voltage is fixed in bios @ 1.25 for 56s, and 1.365 (iirc) for 64s.  FYI, this mem voltage increase is the main point of the 56->64 bios flash

Can someone help me figure out why my ODNT set mem voltage is not what is shown in HWInfo. Core voltage is consistent with set value but not mem voltage for unknown reasons. This kinda explains why my power draw is higher than the rest for the same hashrate. Also, my pool hashrate is consistently lower than my internal hashrate for TRTL algo. Any idea why?

Name=RX Vega 56
GPU_P0=852;805
GPU_P1=991;810
GPU_P2=1084;815
GPU_P3=1138;820
GPU_P4=1150;830
GPU_P5=1202;835
GPU_P6=1212;840
GPU_P7=1220;850
Mem_P0=167;805
Mem_P1=500;805
Mem_P2=800;815
Mem_P3=910;850

That's how it is with Vegas, you can't change mem voltage. Try disabling p0 to p6 and see if you can get lower mV at the same clock or lower core clock a bit and see if it makes enough difference in consumption.

Thanks guys for the tip!

[seefatlow]

Running 6 Vega56@64 @ 850 MHz @ 825mV (850mV for two weaker cards) on core_P7.
Getting approx 98 KH/s combined at 950W at the wall.

That's actually hilarious. This is pretty much roughly 150W per Vega. 103 h/W. L18+18.

L20+20 results in roughly the same figures. More interleave adjusts though.

L22+22 gives a whole bunch of interleave adjusts (all GPUs) and no improvements in hashrate from the values tested above... and ends up crashing after a while.

EDIT: @pbfarmer, I've not managed 18.3 kh/s as you seem to though. More like 16.5 at 850/1107. Using Core_P7 though, not sure that's what's making the difference?

Dragonmike,

Any new update on this? I am still unable to get that level of efficiency. The best i got is 180W per Vega at 18kh/s using L22+22.

[todxx]

Team Red Miner v0.4.4 released

https://github.com/todxx/teamredminer/releases

Changes in v0.4.4

• Added * mode specifically for modded timings on Vega GPUs. Use with e.g. --cn_config=15*15. This mode is now the default for Vegas.
• Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage.
• Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don't gravitate and get stuck.
• Added support for forcing colors (--force_color) for windows redirected consoles (git bash, cygwin, node.js).
• Added hotkey menu system (show stats, enable/disable gpu).

The new * mode opens up tweaking Vega timings for 2MB CN algos like CN-R!
We've seen a few extremely tuned V64 LCs able to hit over 2400h/s on CN-R with 1400/1100 clocks!
For those of you playing with timings, please share your results!  We love seeing how far you guys can push these cards

[rednoW]

Team Red Miner v0.4.4 released

https://github.com/todxx/teamredminer/releases

Changes in v0.4.4

• Added * mode specifically for modded timings on Vega GPUs. Use with e.g. --cn_config=15*15. This mode is now the default for Vegas.
• Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage.
• Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don't gravitate and get stuck.
• Added support for forcing colors (--force_color) for windows redirected consoles (git bash, cygwin, node.js).
• Added hotkey menu system (show stats, enable/disable gpu).

The new * mode opens up tweaking Vega timings for 2MB CN algos like CN-R!
We've seen a few extremely tuned V64 LCs able to hit over 2400h/s on CN-R with 1400/1100 clocks!
For those of you playing with timings, please share your results!  We love seeing how far you guys can push these cards

Max I got is 2470h/s with vega64lc 1428/1140@880mv and 147watt gpu power - all according to gpu-z.
Not worth it ))
2390h/s at 1320/1100@825mv and 127watt is better I think
Or even better vega56 (both samsung and hynix) 2100h/s at 1220/940@775mv  and 97watt in gpu-z

[hammuh]

Team Red Miner v0.4.4 released

https://github.com/todxx/teamredminer/releases

Changes in v0.4.4

• Added * mode specifically for modded timings on Vega GPUs. Use with e.g. --cn_config=15*15. This mode is now the default for Vegas.
• Introduced slow start/ramp-up. Threads increase their workload slowly at start or restart after e.g. a network outage.
• Added interleave adjustment logic. Readjusts the two threads per gpu over time to make sure they don't gravitate and get stuck.
• Added support for forcing colors (--force_color) for windows redirected consoles (git bash, cygwin, node.js).
• Added hotkey menu system (show stats, enable/disable gpu).

The new * mode opens up tweaking Vega timings for 2MB CN algos like CN-R!
We've seen a few extremely tuned V64 LCs able to hit over 2400h/s on CN-R with 1400/1100 clocks!
For those of you playing with timings, please share your results!  We love seeing how far you guys can push these cards

Quick test...

Vega 64 timing via pbfarmer and others:
--RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --RFC 248 --REF 15600

Settings:
1401 mhz core
1107 mhz memory
870 mv voltage

TRM v0.4.4 results:
cnr (monero): ~2.400 kh/s
cnv8_rwz (graft): ~3.150 kh/s
cnv8_half (masari): ~4.600 kh/s
cnv8_dbl (x-cash): ~1.200 kh/s