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

[kerney666]

I had 0 hw in stats, my cards are actually underclocked a bit and downvolted. Total rejects were around 8% on nicehash, with xmrig its ~2.5%

Unfortunately, the comparison doesn’t work since xmrig discards all shares it knows belongs to a stale job iirc, we gamble and send it anyway. That way we’ll always get a higher reject ratio. Looking at poolside with nicehash is also a bitch due to high diff. If you really want a tight poolside hashrate value, you need something like 10k shares found, which means you need to run for several days or even week(s) to really nail it.

8% is very high regardless. I’ve had my 8 x Vega rig run against nicehash for a longer time now, I’m at 3.9% rejected shares. May I ask what your rig(s) look like? Nr gpus and gpu type, and what cpu? You are of course connecting to the closest nicehash stratum?

[UnclWish]

Confirm, nicehash cnr mining - many rejected shares - job not found.
And "Dev pool connection was closed by remote side. Mining will proceed at reduced rate etc etc"

Hey guys! Sorry about all the mess with dev pool, there are some issues outside of our control that we are addressing, should hopefully be resolved today. However, I do believe you all see a reconnect within 30 secs or so, so the "reduced rate" period should really be minimal. Let me know if you are experiencing longer disconnected periods than 30-60 secs.

What about high amount of rejects due to "job not found" on nicehash?

The one big difference is that open source miners have excellent cpu code for the algo, borrowed from their cpu miner. For rigs with slow celerons, we will add significant latency with our more naive on-cpu verification. We need to implement automatic generation of x86 machine code for the random ops in CN/r, quite annoying crap to spend time on, but we don’t really have a choice it seems.

Fix for now: if your rig(s) are running without any hw errors, try running with —no_cpu_check. This will disable our check and let the pool run the check instead. Will be fine on most pools and if you don’t oc so much that you get invalid shares that you flood the pool with .

I didn't understand all of this. But I must notice that on other miners not so much rejected shares on nicehash. Speed on cnr on this miners is slower but lower rejected shares and lower fee can do the profit higher...
Thanks for option --no_cpu_check. I'll try it. But I use overclocked cards, so this may not help... Anyway I'll try it.

We will speed up our cpu code properly, we just didn't have the time for it with this release.

Overclocked cards are not bad in itself as long as they aren't pushed so hard they generate hw errs. Do you see any counts in the "hw" category when the hashrate stats are displayed?

Very rare. About 1-2 error on 24 hours on 1 of cards.

[dragonmike]

So I'm still running 0.4.0 (because it worked so far)... but I noticed it stopped displaying hashrate info completely after a while.

Is that something that's been fixed in 0.4.1 at all? Haven't seen it in the changelog...

EDIT: could it be related with the miner losing connection to devpool? I'm getting these every now and then:

"Dev pool connection was closed by remote side.
Mining will proceed at reduced rate etc etc"

...shortly followed by "Dev pool connected and ready"

...and hashrate clearly falls on the pool.

The hashrate display stopping completely indicates some kind of host-side hang.  We haven't seen this issue recently, but we will look into it.  I can't say that anything we changed in 0.4.1 should affect that.  Please let us know if it happens to you again.

As for the dev pool connection issue, we can't find any problems on our end.  One guess is that because we switched to using port 80 in v0.4.0, some network filters are occasionally killing connections.
In 0.4.1 we switched default port to 4000, if that fails it will try to use port 80 again.

I think the hashrate display stopping was due to one of the GPU's hanging indeed. Increased the voltage a bit on that dodgy card, and I've been mining fine all through the night.

Had 2% rejects over 12 hours at Nanopool. Just upgraded to 0.4.1, and added --no_cpu_check parameter as I wasn't sporting any hw errors. Let's see how that goes today.

Thanks for your work, as always!

[oxzhor]

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx  

We will start chewing away at variants shortly. I just finished adding the most low hanging fruit one of them all, cn/half for MSR and XTL, will continue with others the next few days. We will add heavy and derived variants in a not too distant future, but it's a little more work getting the base heavy kernels going first.

Edit: I've added heavyx for x-cash as well now, I thought it was a Heavy-derived algo, not CNv8 with 2x iterations. What a stupid choice of name .

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

Is x-cash algo working now in 0.4.1 ?? Which flag to use?

Graft planned also?

Nice Work !!

Half+double CNv8 variants are done already for MSR/XTL/x-cash, I'm going to to the waltz now for Graft. We have a few more things host-side we need to add, then we'll release, shouldn't be more than 2 days away from now.

Which parameter do i need to use for x-cash kerney666? Thx

[kerney666]

@kerney666 any idea when cryptonight-heavyx ( x-cash ) will implemented into TeamRedMiner? Thx  

We will start chewing away at variants shortly. I just finished adding the most low hanging fruit one of them all, cn/half for MSR and XTL, will continue with others the next few days. We will add heavy and derived variants in a not too distant future, but it's a little more work getting the base heavy kernels going first.

Edit: I've added heavyx for x-cash as well now, I thought it was a Heavy-derived algo, not CNv8 with 2x iterations. What a stupid choice of name .

If anyone has any specific ideas about your favorite CN variants you'd like to see added, give us a holler here. No promises for any specific order though .

Is x-cash algo working now in 0.4.1 ?? Which flag to use?

Graft planned also?

Nice Work !!

Half+double CNv8 variants are done already for MSR/XTL/x-cash, I'm going to to the waltz now for Graft. We have a few more things host-side we need to add, then we'll release, shouldn't be more than 2 days away from now.

Which parameter do i need to use for x-cash kerney666? Thx

It’s done but not released. Aiming for tomorrow, we have a few more things and fixes we need to get done.

[oxzhor]

Ok thx for the good work!

[carlosmonaco]

Hello ,
Can I use --no_cpu_check parameters if I have some HW error ( 3 / 24hours). I have a lot of rejected share on nanopool.

[bobben2]

HELP
Trying to run this miner with 2 x Sapphire Pulse RX 574, miner version 0.4.1.   Win 10, AMD driver version 18.6.1.
Miner runs for  a while, then driver gets stuck in device driver.. and system reboots..
Usually, this means too much undervolt, but I am now running both GPUs at 1200/2000 at 1V core and it still it crashes....
The previous version ran fine mining CNV8 coins.

EDIT:
Lowered core freq to 1150.  Seems more stable now.  But I see a lot of memory errors in HWiNFO now... and mem is only at 2000...
Hmm.  Maybe these cards were not made for monero mining..  A lot better in ETH mining they are..

[nordmann666]

HELP
Trying to run this miner with 2 x Sapphire Pulse RX 574, miner version 0.4.1.   Win 10, AMD driver version 18.6.1.
Miner runs for  a while, then driver gets stuck in device driver.. and system reboots..
Usually, this means too much undervolt, but I am now running both GPUs at 1200/2000 at 1V core and it still it crashes....
The previous version ran fine mining CNV8 coins.

EDIT:
Lowered core freq to 1150.  Seems more stable now.  But I see a lot of memory errors in HWiNFO now... and mem is only at 2000...
Hmm.  Maybe these cards were not made for monero mining..  A lot better in ETH mining they are..

there are ETH Bios versions and non ETH Bios versions for polaris cause it´s different!
only 2000 - hahaha...thats high if you have realy fast strips for your mem - go lower and lower until you dont see HW errors - save this as CN setting

[P00P135]

HELP
Trying to run this miner with 2 x Sapphire Pulse RX 574, miner version 0.4.1.   Win 10, AMD driver version 18.6.1.
Miner runs for  a while, then driver gets stuck in device driver.. and system reboots..
Usually, this means too much undervolt, but I am now running both GPUs at 1200/2000 at 1V core and it still it crashes....
The previous version ran fine mining CNV8 coins.

EDIT:
Lowered core freq to 1150.  Seems more stable now.  But I see a lot of memory errors in HWiNFO now... and mem is only at 2000...
Hmm.  Maybe these cards were not made for monero mining..  A lot better in ETH mining they are..

Save your current BIOS and try new straps.  I'd suggest 1 click BIOS straps if you havent used them before..

[nordmann666]

HELP
Trying to run this miner with 2 x Sapphire Pulse RX 574, miner version 0.4.1.   Win 10, AMD driver version 18.6.1.
Miner runs for  a while, then driver gets stuck in device driver.. and system reboots..
Usually, this means too much undervolt, but I am now running both GPUs at 1200/2000 at 1V core and it still it crashes....
The previous version ran fine mining CNV8 coins.

EDIT:
Lowered core freq to 1150.  Seems more stable now.  But I see a lot of memory errors in HWiNFO now... and mem is only at 2000...
Hmm.  Maybe these cards were not made for monero mining..  A lot better in ETH mining they are..

Save your current BIOS and try new straps.  I'd suggest 1 click BIOS straps if you havent used them before..

i´m sure he has tight straps and cause this he got problems with 2000mhz (1900 will be faster with tight straps than with 2000mhz and slow straps) - i also had some RX580 some time ago with ultra tight straps and i only can use them with 1850mhz (but also 30,5MHs Ethereum) - and got errors on CN lite (have to go 1800MHz for stable CN mining)

[roma__11]

support is planned GRAFT

[kerney666]

support is planned GRAFT

It is done and will be included in the next release, 1-2 days max.

[fenomenyaa]

--no_cpu_check parameter not helps on nanopool. %3 rejected share 0 hw error.

[D8V1D]

I've been running 0.4.0 on SupportXMR for 2 days without any rejects.

Also have 0.4.1 on another rig for 15 hours without rejects.

[geoteo]

It seems to be a problem with nanopool. 10 rigs for 24 hours with 3% rejects and no hw errrors. Switch to supportxmr for 6 hours with no rejects yet.

All the best to the developers for the great miner.

[UnclWish]

On nicehash --no_cpu_check didn't help too. For me with this option rejects became more... Disable it.
Tried other miners. Speed on all slower, also exists rejects "job not found". Pool-side speed on TR miner is best! Waiting updates!

[pbfarmer]

HELP
Trying to run this miner with 2 x Sapphire Pulse RX 574, miner version 0.4.1.   Win 10, AMD driver version 18.6.1.
Miner runs for  a while, then driver gets stuck in device driver.. and system reboots..
Usually, this means too much undervolt, but I am now running both GPUs at 1200/2000 at 1V core and it still it crashes....
The previous version ran fine mining CNV8 coins.

EDIT:
Lowered core freq to 1150.  Seems more stable now.  But I see a lot of memory errors in HWiNFO now... and mem is only at 2000...
Hmm.  Maybe these cards were not made for monero mining..  A lot better in ETH mining they are..

1V core sounds crazy high for 570s.  I run 580-8s between 812-843mv w/ 1225 core (some down to 1200,) for ~1Kh/s.  Mem speed is totally dependent on the mfg and your straps - 2K is pretty much the upper limit for the PBE one-click straps on samsung, so if that's what you're running, maybe dial it down a touch.

Also, this algo (or maybe this implementation) is a bit funny - it almost seems like voltage requirements may be a bit quantized.  For instance, on pretty much all my 580s, I couldn't get 1250 running w/o errors even at 850mv.  But after dropping to 1225, I could reduce my voltage all the way down to 812mv on a number of cards before errors started appearing again.

[bobben2]

HELP
Trying to run this miner with 2 x Sapphire Pulse RX 574, miner version 0.4.1.   Win 10, AMD driver version 18.6.1.
Miner runs for  a while, then driver gets stuck in device driver.. and system reboots..
Usually, this means too much undervolt, but I am now running both GPUs at 1200/2000 at 1V core and it still it crashes....
The previous version ran fine mining CNV8 coins.

EDIT:
Lowered core freq to 1150.  Seems more stable now.  But I see a lot of memory errors in HWiNFO now... and mem is only at 2000...
Hmm.  Maybe these cards were not made for monero mining..  A lot better in ETH mining they are..

1V core sounds crazy high for 570s.  I run 580-8s between 812-843mv w/ 1225 core (some down to 1200,) for ~1Kh/s.  Mem speed is totally dependent on the mfg and your straps - 2K is pretty much the upper limit for the PBE one-click straps on samsung, so if that's what you're running, maybe dial it down a touch.

Also, this algo (or maybe this implementation) is a bit funny - it almost seems like voltage requirements may be a bit quantized.  For instance, on pretty much all my 580s, I couldn't get 1250 running w/o errors even at 850mv.  But after dropping to 1225, I could reduce my voltage all the way down to 812mv on a number of cards before errors started appearing again.

Thanks for all the advice.  Yeah, 1V is uber.  But power draw and temps are reasonable. 
I reduced core freq and mem freq to 1150/1975 with core volt 925 and rig ran stably overnight, both cards hashing at 935H/s.   Still memory errors.  Will work on these three parameters when I get home from work:
Core freq
Core volt
Mem freq
Looks like the mem strap is too tight for CNR, so will have to reduce mem freq further.   Cards work flawlessly at 1100/2000 on ETH with core volt at 813mV.
For CNR core volt needs at least 925 mV...
Anyhow, the miner software looks to be stable.  Thankyou goes to the developers.

[carlosmonaco]

Hello ,
Is it possible to record log on this miner ? One of mine is freezing but I need to hard reboot it without possibility to know what card crash