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

[pbfarmer]

Thanks for the timely release, Kerney & Tod.
I'll give it a whirl tonight with the Vegas.

Can you just confirm one thing quickly please: will the new CN/r version work on "legacy" drivers in Windows? I'm on 18.6.1 as it's proven to be the stablest overall thus far. I don't think your original post specified just that point.

Yep, I've tested a lot on 18.6.1 with my 8 x Vega 56 rig. I'd go even further and say the 18.6.1 driver is much more battle-tested than any 19.x.y driver.

I never had problems up through the last 18.x.  19.x was a whole different beast, and required some changes to ODNT which I didn't wait for, though I've heard they were addressed shortly after release.

[1714781275]

1714781275

[1714781275]

1714781275

[1714781275]

1714781275

[kerney666]

Team Red Miner v0.4.0 released

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

Changes in v0.4.0

• Added cryptonight R support.  (--algo cnr)
• Added support for ssl/tls pool connections using the stratum+ssl:// prefix.
• Added colors (and an option to disable them).
• Slight performance increase for lyra2rev3 (~0.5%).
• Fix for occasional crashes when pool disconnects.
• Added more messages regarding not being connected to dev pool.
• Changed printing to not block mining progress if stdout writes block.

A bit delayed with this post, but better late than never.

The main change in this version is the addition of CN/R support.
Performance of CN/R is roughly the same on Vegas as cnv8.  Polaris cards are a bit slower with larger cards losing about 0.5% and the smaller cards like rx550s losing ~1.5%.
Power for CN/R is up by 2-3% compared to cnv8.

Also we've added some user requested features like colors and support for ssl pool connections.

Hi,
I have problem with Vega and CryptonightR.
Intensity set to 12+11. (14+14, 14+13 hangs my cards)
And I have this results:

Code:

[2019-03-09 11:10:54] Stats Uptime: 0 days, 00:09:01
[2019-03-09 11:10:54] GPU 0 [34C, fan  0%] cnr: 2.811kh/s, avg 1.403kh/s, pool 2.235kh/s a:5 r:0 hw:0
[2019-03-09 11:10:54] GPU 1 [34C, fan  0%] cnr: 2.825kh/s, avg 1.413kh/s, pool 2.982kh/s a:7 r:0 hw:0
[2019-03-09 11:10:54] GPU 2 [29C, fan  0%] cnr: 2.800kh/s, avg 1.399kh/s, pool 1.491kh/s a:3 r:0 hw:0
[2019-03-09 11:10:54] GPU 3 [31C, fan  0%] cnr: 3.053kh/s, avg 1.523kh/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-09 11:10:54] Total                cnr: 11.49kh/s, avg 5.739kh/s, pool 6.708kh/s a:15 r:0 hw:0
[2019-03-09 11:11:10] Shutting down...
[2019-03-09 11:11:11] GPU 2 CN thread 1 exiting.
[2019-03-09 11:11:11] GPU 3 CN thread 0 exiting.
[2019-03-09 11:11:11] GPU 0 CN thread 1 exiting.
[2019-03-09 11:11:11] GPU 1 CN thread 1 exiting.
[2019-03-09 11:11:20] GPU 0 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 1 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 2 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 3 thread 1 shutdown timed out.

1. 2.8kh/s is rather high. Avarage is a half of this.

Intensity 13+12

Code:

[2019-03-09 11:21:02] GPU 0 [ 0C, fan  0%] cnr: 3.060kh/s, avg 1.525kh/s, pool 1.579kh/s a:2 r:0 hw:0
[2019-03-09 11:21:02] GPU 1 [ 0C, fan  0%] cnr: 3.072kh/s, avg 1.531kh/s, pool 1.579kh/s a:3 r:0 hw:0
[2019-03-09 11:21:02] GPU 2 [ 0C, fan  0%] cnr: 3.044kh/s, avg 1.517kh/s, pool 395.0 h/s a:1 r:0 hw:0
[2019-03-09 11:21:02] GPU 3 [ 0C, fan  0%] cnr: 3.050kh/s, avg 1.520kh/s, pool 2.371kh/s a:4 r:0 hw:0
[2019-03-09 11:21:02] Total                cnr: 12.22kh/s, avg 6.093kh/s, pool 5.923kh/s a:10 r:0 hw:0

2. I have trouble with shutdown. After that I have to force miner to close the window.

Hi! Like other people just noted, I believe this is related to your clocks. Intensity 12+12 will still have enough pads running to put load on the gpu. CN/r is yet another different beast than CNv8, those random ops are a heavy workload with a lot of muls. One of your threads per gpu has crashed in all cases above, you can tell from the timeouts when exiting.

I've tested all my Vega 64 LC and Vega 56s at old school CN clocks (1408@900, 1100@900, 56s flashed to 64 bios), and have ran successfully for extended periods without issues.

What environment (OS, driver) are you using, and what Vegas are these?

[dragonmike]

Thanks for the timely release, Kerney & Tod.
I'll give it a whirl tonight with the Vegas.

Can you just confirm one thing quickly please: will the new CN/r version work on "legacy" drivers in Windows? I'm on 18.6.1 as it's proven to be the stablest overall thus far. I don't think your original post specified just that point.

Yep, I've tested a lot on 18.6.1 with my 8 x Vega 56 rig. I'd go even further and say the 18.6.1 driver is much more battle-tested than any 19.x.y driver.

Perfect, cheers
What intensities were you using with the Vegas by the way (so I have a basis to start with)? Same as CNv2?

[kerney666]

Thanks for the timely release, Kerney & Tod.
I'll give it a whirl tonight with the Vegas.

Can you just confirm one thing quickly please: will the new CN/r version work on "legacy" drivers in Windows? I'm on 18.6.1 as it's proven to be the stablest overall thus far. I don't think your original post specified just that point.

Yep, I've tested a lot on 18.6.1 with my 8 x Vega 56 rig. I'd go even further and say the 18.6.1 driver is much more battle-tested than any 19.x.y driver.

Perfect, cheers
What intensities were you using with the Vegas by the way (so I have a basis to start with)? Same as CNv2?

Yes, start with your CNv2 settings but if your rigs were trimmed to their very limit, you will need to provide some more juice or tweak your clocks. Need a little more power to drive this one.

[dragonmike]

Thanks for the timely release, Kerney & Tod.
I'll give it a whirl tonight with the Vegas.

Can you just confirm one thing quickly please: will the new CN/r version work on "legacy" drivers in Windows? I'm on 18.6.1 as it's proven to be the stablest overall thus far. I don't think your original post specified just that point.

Yep, I've tested a lot on 18.6.1 with my 8 x Vega 56 rig. I'd go even further and say the 18.6.1 driver is much more battle-tested than any 19.x.y driver.

Perfect, cheers
What intensities were you using with the Vegas by the way (so I have a basis to start with)? Same as CNv2?

Yes, start with your CNv2 settings but if your rigs were trimmed to their very limit, you will need to provide some more juice or tweak your clocks. Need a little more power to drive this one.

Rock'n'roll

[wacholek]

Team Red Miner v0.4.0 released

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

Changes in v0.4.0

• Added cryptonight R support.  (--algo cnr)
• Added support for ssl/tls pool connections using the stratum+ssl:// prefix.
• Added colors (and an option to disable them).
• Slight performance increase for lyra2rev3 (~0.5%).
• Fix for occasional crashes when pool disconnects.
• Added more messages regarding not being connected to dev pool.
• Changed printing to not block mining progress if stdout writes block.

A bit delayed with this post, but better late than never.

The main change in this version is the addition of CN/R support.
Performance of CN/R is roughly the same on Vegas as cnv8.  Polaris cards are a bit slower with larger cards losing about 0.5% and the smaller cards like rx550s losing ~1.5%.
Power for CN/R is up by 2-3% compared to cnv8.

Also we've added some user requested features like colors and support for ssl pool connections.

Hi,
I have problem with Vega and CryptonightR.
Intensity set to 12+11. (14+14, 14+13 hangs my cards)
And I have this results:

Code:

[2019-03-09 11:10:54] Stats Uptime: 0 days, 00:09:01
[2019-03-09 11:10:54] GPU 0 [34C, fan  0%] cnr: 2.811kh/s, avg 1.403kh/s, pool 2.235kh/s a:5 r:0 hw:0
[2019-03-09 11:10:54] GPU 1 [34C, fan  0%] cnr: 2.825kh/s, avg 1.413kh/s, pool 2.982kh/s a:7 r:0 hw:0
[2019-03-09 11:10:54] GPU 2 [29C, fan  0%] cnr: 2.800kh/s, avg 1.399kh/s, pool 1.491kh/s a:3 r:0 hw:0
[2019-03-09 11:10:54] GPU 3 [31C, fan  0%] cnr: 3.053kh/s, avg 1.523kh/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-09 11:10:54] Total                cnr: 11.49kh/s, avg 5.739kh/s, pool 6.708kh/s a:15 r:0 hw:0
[2019-03-09 11:11:10] Shutting down...
[2019-03-09 11:11:11] GPU 2 CN thread 1 exiting.
[2019-03-09 11:11:11] GPU 3 CN thread 0 exiting.
[2019-03-09 11:11:11] GPU 0 CN thread 1 exiting.
[2019-03-09 11:11:11] GPU 1 CN thread 1 exiting.
[2019-03-09 11:11:20] GPU 0 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 1 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 2 thread 0 shutdown timed out.
[2019-03-09 11:11:20] GPU 3 thread 1 shutdown timed out.

1. 2.8kh/s is rather high. Avarage is a half of this.

Intensity 13+12

Code:

[2019-03-09 11:21:02] GPU 0 [ 0C, fan  0%] cnr: 3.060kh/s, avg 1.525kh/s, pool 1.579kh/s a:2 r:0 hw:0
[2019-03-09 11:21:02] GPU 1 [ 0C, fan  0%] cnr: 3.072kh/s, avg 1.531kh/s, pool 1.579kh/s a:3 r:0 hw:0
[2019-03-09 11:21:02] GPU 2 [ 0C, fan  0%] cnr: 3.044kh/s, avg 1.517kh/s, pool 395.0 h/s a:1 r:0 hw:0
[2019-03-09 11:21:02] GPU 3 [ 0C, fan  0%] cnr: 3.050kh/s, avg 1.520kh/s, pool 2.371kh/s a:4 r:0 hw:0
[2019-03-09 11:21:02] Total                cnr: 12.22kh/s, avg 6.093kh/s, pool 5.923kh/s a:10 r:0 hw:0

2. I have trouble with shutdown. After that I have to force miner to close the window.

Hi! Like other people just noted, I believe this is related to your clocks. Intensity 12+12 will still have enough pads running to put load on the gpu. CN/r is yet another different beast than CNv8, those random ops are a heavy workload with a lot of muls. One of your threads per gpu has crashed in all cases above, you can tell from the timeouts when exiting.

I've tested all my Vega 64 LC and Vega 56s at old school CN clocks (1408@900, 1100@900, 56s flashed to 64 bios), and have ran successfully for extended periods without issues.

What environment (OS, driver) are you using, and what Vegas are these?

Ok lets start from a beginning.

Clocks. 1530@1050V and 1100@1050. Works great on CNv8 with 15+14. 2050h/s. Cards are on water.
On the same clocks on CNR and those crashes. On 13+12 works with bad hashrate reporting. At that settings and 18.6.1 driver I have 36*C on the core and 155W of power.

I also use this miner for Lyra2rev3 with 108Mh/s per cards with no problem for weeks.

So NO, this is not the problem with voltage/clocks setting.

What about the bad hashrate rapport? This is voltage/clocks setting issue to?

[pbfarmer]

Ok lets start from a beginning.

Clocks. 1530@1050V and 1100@1050. Works great on CNv8 with 15+14. 2050h/s. Cards are on water.
On the same clocks on CNR and those crashes. On 13+12 works with bad hashrate reporting. At that settings and 18.6.1 driver I have 36*C on the core and 155W of power.

I also use this miner for Lyra2rev3 with 108Mh/s per cards with no problem for weeks.

So NO, this is not the problem with voltage/clocks setting.

Every algo creates a different load signature, which can require different clock/voltage settings.  Just because some combo of settings worked for some other algo, doesn't mean it will work here.  Though it does appear the settings should be close to cnv2.

What about the bad hashrate rapport? This is voltage/clocks setting issue to?

Absolutely - I've seen the same behavior, in many different miners, for many different algos.  Just now, in linux, I experienced a 2700H/s report from TRM stemming from a too extreme uv.

[kerney666]

Ok lets start from a beginning.

Clocks. 1530@1050V and 1100@1050. Works great on CNv8 with 15+14. 2050h/s. Cards are on water.
On the same clocks on CNR and those crashes. On 13+12 works with bad hashrate reporting. At that settings and 18.6.1 driver I have 36*C on the core and 155W of power.

I also use this miner for Lyra2rev3 with 108Mh/s per cards with no problem for weeks.

So NO, this is not the problem with voltage/clocks setting.

Every algo creates a different load signature, which can require different clock/voltage settings.  Just because some combo of settings worked for some other algo, doesn't mean it will work here.  Though it does appear the settings should be close to cnv2.

What about the bad hashrate rapport? This is voltage/clocks setting issue to?

Absolutely - I've seen the same behavior, in many different miners, for many different algos.  Just now, in linux, I experienced a 2700H/s report from TRM stemming from a too extreme uv.

Yes, the combo of clocks and algo is the key metric. The issue with this algo is the random code (re)generation. Since we build our kernels in asm, we don't recompile like the other miners, we solve this in a different way. In turn, this means this kernel gets a very different load footprint in one specific way.

@wacholek: we've also done some extensive host-side changes in this release, so can you verify that CNv8 and lyra2rev3 runs just as good as before with _this_ version, not 0.3.8 or 0.3.9? Would be great data to have to fix things. Also, I remember you running some custom mod for water, but what OS and driver are you running?

[wacholek]

Ok lets start from a beginning.

Clocks. 1530@1050V and 1100@1050. Works great on CNv8 with 15+14. 2050h/s. Cards are on water.
On the same clocks on CNR and those crashes. On 13+12 works with bad hashrate reporting. At that settings and 18.6.1 driver I have 36*C on the core and 155W of power.

I also use this miner for Lyra2rev3 with 108Mh/s per cards with no problem for weeks.

So NO, this is not the problem with voltage/clocks setting.

Every algo creates a different load signature, which can require different clock/voltage settings.  Just because some combo of settings worked for some other algo, doesn't mean it will work here.  Though it does appear the settings should be close to cnv2.

What about the bad hashrate rapport? This is voltage/clocks setting issue to?

Absolutely - I've seen the same behavior, in many different miners, for many different algos.  Just now, in linux, I experienced a 2700H/s report from TRM stemming from a too extreme uv.

Yes, the combo of clocks and algo is the key metric. The issue with this algo is the random code (re)generation. Since we build our kernels in asm, we don't recompile like the other miners, we solve this in a different way. In turn, this means this kernel gets a very different load footprint in one specific way.

@wacholek: we've also done some extensive host-side changes in this release, so can you verify that CNv8 and lyra2rev3 runs just as good as before with _this_ version, not 0.3.8 or 0.3.9? Would be great data to have to fix things. Also, I remember you running some custom mod for water, but what OS and driver are you running?

System Win10. 4 x Vega 64 wit LC bios on water.

Lyra2Rev3 1500@950 1100@945   On v0.3.10  429.8Mh/s  ; On v0.4.0 435.7Mh/s.  Very good. Hashrate and avr Hashrate the same. Good work!!!

I will test CNv8 later.

[vmozara]

Kerney666,
Which driver you recommend for Vega 56 and 64 rigs for new CN-R? I am on the ship and access my rigs remotely, they now have 18.6.1, should i change anything?

Thanks!

[geoteo]

Does the new version support graft?

[MaxHa$h]

Team Red Miner v0.4.0 released

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

Changes in v0.4.0

• Added cryptonight R support.  (--algo cnr)

Haven't updated yet, quick question, do i have to wait for the fork, or will this switch over?[/list]

[VictorGT]

Team Red Miner v0.4.0 released

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

Changes in v0.4.0

• Added cryptonight R support.  (--algo cnr)

Haven't updated yet, quick question, do i have to wait for the fork, or will this switch over?[/list]

I'll also like a lot to know this...

[vmozara]

No, you have to switch manually

[dragonmike]

Kerney666,
Which driver you recommend for Vega 56 and 64 rigs for new CN-R? I am on the ship and access my rigs remotely, they now have 18.6.1, should i change anything?

Thanks!

scroll up a bit!

[kerney666]

Team Red Miner v0.4.0 released

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

Changes in v0.4.0

• Added cryptonight R support.  (--algo cnr)

Haven't updated yet, quick question, do i have to wait for the fork, or will this switch over?[/list]

I'll also like a lot to know this...

Sorry, would have been nice if we’d added automatic algo switch but no, miner shutdown and restart is the way to go.

[kerney666]

Kerney666,
Which driver you recommend for Vega 56 and 64 rigs for new CN-R? I am on the ship and access my rigs remotely, they now have 18.6.1, should i change anything?

Thanks!

scroll up a bit!

I think most, if not all, drivers >= 18.5.x will work ok. I’ve tested with 18.6.1 and 19.2.2 myself (just bc that workstation has a Radeon VII). In short, you should be able to keep your CNv8 setup as-is. Might need to retune and tweak clocks though.

[MaxHa$h]

Team Red Miner v0.4.0 released

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

Changes in v0.4.0

• Added cryptonight R support.  (--algo cnr)

Haven't updated yet, quick question, do i have to wait for the fork, or will this switch over?[/list]

I'll also like a lot to know this...

Sorry, would have been nice if we’d added automatic algo switch but no, miner shutdown and restart is the way to go.

Ok, thank you for the quick response! been spreading your miner all over twitter for months, even on the castxmr thread stating he will no longer be supporting the software for development

#teamredminer

[kerney666]

Team Red Miner v0.4.0 released

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

Changes in v0.4.0

• Added cryptonight R support.  (--algo cnr)

Haven't updated yet, quick question, do i have to wait for the fork, or will this switch over?[/list]

I'll also like a lot to know this...

Sorry, would have been nice if we’d added automatic algo switch but no, miner shutdown and restart is the way to go.

Ok, thank you for the quick response! been spreading your miner all over twitter for months, even on the castxmr thread stating he will no longer be supporting the software for development

#teamredminer

Haha nice, appreciate the shilling! Cast was indeed a great miner when it came out, I remember it well. Let us know if there’s anything else you need or have questions about!

[nordmann666]

[2019-03-09 17:57:06] Dev pool connection was closed by remote side.
[2019-03-09 17:57:06] Mining will proceed at reduced rate while not connected to dev pool.


hmmmm
any fix soon?!