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

[carlosmonaco]

Hello,
Any ETA for cryptonightR update ?

[MaxHa$h]

I can be mistaken, but it seems that FPGA work on these algorithms
CNv8 this is today's algorithm for monero?

The last month, the XMR Nethash jumped by 150~MH/s. This is certainly either private CNv8 FPGA bitstreams, or some weak ASICs. I would think its the first.

Definitely! though they have the flexibility to update the bitstream to "R" just like everyone else, even if it takes alittle longer they wont lag far behind!

[msTrix]

Hello,
Any ETA for cryptonightR update ?

saw some post on reddit yesterday or so, that they were expecting a version about today, lets see if that one is just as great as for the current CNv8!

[kerney666]

Hello,
Any ETA for cryptonightR update ?

saw some post on reddit yesterday or so, that they were expecting a version about today, lets see if that one is just as great as for the current CNv8!

We’re hustling to make it in time for the fork, it will be tight. I should be able to have indicative performance nrs shortly.

[emaugust]

Is this thread / git the places to keep an eye on for the updated build and related info tonight?

[kerney666]

Is this thread / git the places to keep an eye on for the updated build and related info tonight?

Is is. Todxx will be posting here within 1-2h max.

[carlosmonaco]

Great ! Good job ! Same setting as usual ? ( Vega ) Hashrate estimate ?

[heavyarms1912]

Is this thread / git the places to keep an eye on for the updated build and related info tonight?

Is is. Todxx will be posting here within 1-2h max.

[2019-03-08 20:01:01] GPU 7: detected DEAD (16:00.0), no restart script configured, will continue mining.
[2019-03-08 20:01:01] Please use command line argument --watchdog_script to handle dead GPUs.

Vega VII / R7 not working for me.

[kerney666]

Is this thread / git the places to keep an eye on for the updated build and related info tonight?

Is is. Todxx will be posting here within 1-2h max.

[2019-03-08 20:01:01] GPU 7: detected DEAD (16:00.0), no restart script configured, will continue mining.
[2019-03-08 20:01:01] Please use command line argument --watchdog_script to handle dead GPUs.

Vega VII / R7 not working for me.

We have spent _zero_ time optimizing for the VIIs, we debated not even allowing mining on it since we will not be competitive from a max perf perspective, and it's far from the quality standard we aim to deliver. That said, I don't know how we compare from an efficiency perspective, could still be interesting I guess. The main reason for enabling gfx906 support in this release was for the compute algos.

Regarding your issue though, I'm currently mining just fine using 0.4.0 under Win10 on one of my VIIs. The card is on fire within 2 mins unless you blast those fans though.

What environment are you running? I guess you don't see any action at all, the card never starts mining?

[heavyarms1912]

Is this thread / git the places to keep an eye on for the updated build and related info tonight?

Is is. Todxx will be posting here within 1-2h max.

[2019-03-08 20:01:01] GPU 7: detected DEAD (16:00.0), no restart script configured, will continue mining.
[2019-03-08 20:01:01] Please use command line argument --watchdog_script to handle dead GPUs.

Vega VII / R7 not working for me.

We have spent _zero_ time optimizing for the VIIs, we debated not even allowing mining on it since we will not be competitive from a max perf perspective, and it's far from the quality standard we aim to deliver. That said, I don't know how we compare from an efficiency perspective, could still be interesting I guess. The main reason for enabling gfx906 support in this release was for the compute algos.

Regarding your issue though, I'm currently mining just fine using 0.4.0 under Win10 on one of my VIIs. The card is on fire within 2 mins unless you blast those fans though.

What environment are you running? I guess you don't see any action at all, the card never starts mining?

nevermind. default intensity was the problem.  14+14 is hashing.
Yea the card started mining for a brief moment then this message popped up.  I played around with intensity and it's hashing.
it's windows 10.  

Another run
one thread was hashing alright.  
other one wasn't.

[todxx]

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.

[nordmann666]

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.

just in time...thx

[Divinity666]

In CNR Furies h\r is higher than in CNv8, though I didn't use Teamredminer to mine CNv8. It was 840hs@1000mhz, and here I have lower clocks(<980Mhz, was to lazy to set CN profiles to cards cos of 20mhz difference). Power consumption also dropped, but I guess @1000mhz it will be just the same

[kerney666]

In CNR Furies h\r is higher than in CNv8, though I didn't use Teamredminer to mine CNv8. It was 840hs@1000mhz, and here I have lower clocks(<980Mhz, was to lazy to set CN profiles to cards cos of 20mhz difference). Power consumption also dropped, but I guess @1000mhz it will be just the same

Hi! Interesting data point, we don't have any Fury cards that we test with! My hunch is that we probably would have been faster on CNv8 as well though, it makes no sense for our CNr being faster than our CNv8.

[ep690d]

Hi TeamRedMiner,

please add support to lyra2vc0ban.

https://forum.c0ban.co/t/topic/120

Thanks

[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.

[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.

[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.

[vmozara]

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

Your cards can't take it, either intensity or too high clock. When they start to make funny hashrates, they crashed

[pbfarmer]

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.

1. I'm on linux, but I'm seeing similar behavior to what I saw w/ cnv2 on Windows - for vega64, an effective core clock of 1400MHz, mem clock 1107, and voltage around 830-850mv should get you 2.1Kh/s w/ 16+14. 

2. The failure mode resulting from too much oc/uv can be pretty harsh - often you see a full opencl/driver crash, sometimes requiring a reboot or even hard reset.