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

[jazz1984]

Hi all, now try to start v0.3.6 with my 7970 and rx 470
7970: Failed to initialize device number 0 (-20)
470: Failed to initialize device number 0 (-6)

[peterboy1]

the new update is very helpful, the new stats, bus reorder and clean shutdown is nice.

however, one of my rig which is mixed 13 rx570 is having hard time achieving its max hashrate at startup. (unlike previous miner, sometimes, at startup, max hashrate is already achieved). it needed dirty tricks which is disabling and enabling lan.

another 13 gpu rig which is identical, all samsung is fine.

anyway, hope you wont change anything in the code about my issue, it seems that i like it better than the old miner.

i only need to dirty tricks my mixed rig once, than multiple times before this update.

[ku4eto]

Okay, i tried 0.3.7.

There is an issue when starting the miner and the GPUs.

For some reason, one of my GPUs will NOT initiate properly (first was GPU2, now is GPU1), and it will run at only 1 thread, the other thread is seemingly crashed, since it spews 500+HWs per 30 sec. Running 0.3.6 is all OK.

Hi ku4eto,

These stability issues seem to have no end.  It seems like every time we change something to get some rigs to be more stable, some else's start having problems.

That said, can you provide a bit more information about your rig and how the miner is behaving?
What OS are you running?
What version drivers are you using?
What GPUs are you running?
Can you post the output of the miner when it is having the issues you described?

This information would help us a lot in trying to find the cause of the problem.

The issue seems to be coming from the CN_CONFIG, for some reason, it did not like `8-7`. When i changed it to `7-7`, it started okay.

Also, the hashrate seems to have increased as well, gained ~60-70h/s total.

OS is Windows 10.
Drivers are 18.2.1.
The GPUS are 1x570 and 3x580.
The output was normal, just showing hw: ### for 1 random GPU (the one that does not initialize properly). And it keeps mining as if nothing happens (at lower hashrate though).

[todxx]

Hi all, now try to start v0.3.6 with my 7970 and rx 470
7970: Failed to initialize device number 0 (-20)
470: Failed to initialize device number 0 (-6)

Hi jazz1984,

I'm afraid we only support newer GCN cards, so the 7970 is not supported.
As for the 470, it seems that the driver might be too old.  What OS and driver version are you running?

[todxx]

the new update is very helpful, the new stats, bus reorder and clean shutdown is nice.

however, one of my rig which is mixed 13 rx570 is having hard time achieving its max hashrate at startup. (unlike previous miner, sometimes, at startup, max hashrate is already achieved). it needed dirty tricks which is disabling and enabling lan.

another 13 gpu rig which is identical, all samsung is fine.

anyway, hope you wont change anything in the code about my issue, it seems that i like it better than the old miner.

i only need to dirty tricks my mixed rig once, than multiple times before this update.

I'm glad to hear the miner is running well for you and that the new features are going to good use
The problem of hashrates varying is known to us, and seems to happen with other miners as well.  We plan to address this in the future so that max hashrate is always achieved, but we don't have an ETA for when we will get to that.
Lately we've mostly been working on getting the miner to be stable for everyone.

[jazz1984]

Hi all, now try to start v0.3.6 with my 7970 and rx 470
7970: Failed to initialize device number 0 (-20)
470: Failed to initialize device number 0 (-6)

Hi jazz1984,

I'm afraid we only support newer GCN cards, so the 7970 is not supported.
As for the 470, it seems that the driver might be too old.  What OS and driver version are you running?

Im using windows 7 64-bit and river adrenaline 18.5.1 when trying to run teamredminer. Next ill try 0.3.7 with 18.6.1 and report here.

[todxx]

Okay, i tried 0.3.7.

There is an issue when starting the miner and the GPUs.

For some reason, one of my GPUs will NOT initiate properly (first was GPU2, now is GPU1), and it will run at only 1 thread, the other thread is seemingly crashed, since it spews 500+HWs per 30 sec. Running 0.3.6 is all OK.

Hi ku4eto,

These stability issues seem to have no end.  It seems like every time we change something to get some rigs to be more stable, some else's start having problems.

That said, can you provide a bit more information about your rig and how the miner is behaving?
What OS are you running?
What version drivers are you using?
What GPUs are you running?
Can you post the output of the miner when it is having the issues you described?

This information would help us a lot in trying to find the cause of the problem.

The issue seems to be coming from the CN_CONFIG, for some reason, it did not like `8-7`. When i changed it to `7-7`, it started okay.

Also, the hashrate seems to have increased as well, gained ~60-70h/s total.

OS is Windows 10.
Drivers are 18.2.1.
The GPUS are 1x570 and 3x580.
The output was normal, just showing hw: ### for 1 random GPU (the one that does not initialize properly). And it keeps mining as if nothing happens (at lower hashrate though).

Great! So the 7-7 config got your rig running without problems?
The auto-detect for config is some times a bit over-aggressive and will select configs that might be a bit too high, like 8+7 on 4GB cards.
In our experience, 8+7 can sometimes work on 4GB cards if they don't have a monitor connected to them and usually works best after a fresh reboot.

[todxx]

Hi all, now try to start v0.3.6 with my 7970 and rx 470
7970: Failed to initialize device number 0 (-20)
470: Failed to initialize device number 0 (-6)

Hi jazz1984,

I'm afraid we only support newer GCN cards, so the 7970 is not supported.
As for the 470, it seems that the driver might be too old.  What OS and driver version are you running?

Im using windows 7 64-bit and river adrenaline 18.5.1 when trying to run teamredminer. Next ill try 0.3.7 with 18.6.1 and report here.

You know, I just got another report from someone else running windows 7 and having issues.  Unfortunately all of our test rigs are running windows 10 and Ubuntu 18.04.
Do let us know if the 18.6.1 driver behaves any differently though.  Also you can try to select just the 470 card with the -d option.

[jazz1984]

Hi all, now try to start v0.3.6 with my 7970 and rx 470
7970: Failed to initialize device number 0 (-20)
470: Failed to initialize device number 0 (-6)

Hi jazz1984,

I'm afraid we only support newer GCN cards, so the 7970 is not supported.
As for the 470, it seems that the driver might be too old.  What OS and driver version are you running?

Im using windows 7 64-bit and river adrenaline 18.5.1 when trying to run teamredminer. Next ill try 0.3.7 with 18.6.1 and report here.

You know, I just got another report from someone else running windows 7 and having issues.  Unfortunately all of our test rigs are running windows 10 and Ubuntu 18.04.
Do let us know if the 18.6.1 driver behaves any differently though.  Also you can try to select just the 470 card with the -d option.

Ok, i got it. In my case 470 is -d 1. As i understand with --cn_config 7+7 or 7+8 i will get best result on 470?

[PIOUPIOU99]

The issue seems to be coming from the CN_CONFIG, for some reason, it did not like `8-7`. When i changed it to `7-7`, it started okay.

thanks ku4eto,  7+7 for my 470/480/570/580 4G is ok
v0.3.7 in auto = bsod or 0h/s
v0.3.6 auto = ok .

no card  monitor connected .

[ku4eto]

The issue seems to be coming from the CN_CONFIG, for some reason, it did not like `8-7`. When i changed it to `7-7`, it started okay.

thanks ku4eto,  7+7 for my 470/480/570/580 4G is ok
v0.3.7 in auto = bsod or 0h/s
v0.3.6 auto = ok .

no card  monitor connected .

the new update is very helpful, the new stats, bus reorder and clean shutdown is nice.

however, one of my rig which is mixed 13 rx570 is having hard time achieving its max hashrate at startup. (unlike previous miner, sometimes, at startup, max hashrate is already achieved). it needed dirty tricks which is disabling and enabling lan.

another 13 gpu rig which is identical, all samsung is fine.

anyway, hope you wont change anything in the code about my issue, it seems that i like it better than the old miner.

i only need to dirty tricks my mixed rig once, than multiple times before this update.

I'm glad to hear the miner is running well for you and that the new features are going to good use
The problem of hashrates varying is known to us, and seems to happen with other miners as well.  We plan to address this in the future so that max hashrate is always achieved, but we don't have an ETA for when we will get to that.
Lately we've mostly been working on getting the miner to be stable for everyone.

I was using manual config of `8-7`, not auto.

[todxx]

Hi all, now try to start v0.3.6 with my 7970 and rx 470
7970: Failed to initialize device number 0 (-20)
470: Failed to initialize device number 0 (-6)

Hi jazz1984,

I'm afraid we only support newer GCN cards, so the 7970 is not supported.
As for the 470, it seems that the driver might be too old.  What OS and driver version are you running?

Im using windows 7 64-bit and river adrenaline 18.5.1 when trying to run teamredminer. Next ill try 0.3.7 with 18.6.1 and report here.

You know, I just got another report from someone else running windows 7 and having issues.  Unfortunately all of our test rigs are running windows 10 and Ubuntu 18.04.
Do let us know if the 18.6.1 driver behaves any differently though.  Also you can try to select just the 470 card with the -d option.

Ok, i got it. In my case 470 is -d 1. As i understand with --cn_config 7+7 or 7+8 i will get best result on 470?

Yep, you got it.  The 7+7 and 7+8 configs are usually best for 4GB cards.  8GB cards can sometimes do well with 8+8.

[matt7659]

Hi! I have a problem with my 9 ref Vega 64 rigs… I start the miner, hashrate is better and the power consumption is lower then my other miner. But after few minutes one of rigs psu crashes and 5 vegas stop working. On my other miner there are no crashes. I tried multiple intensity settings and the same thing happens.

Thank you!

[kerney666]

Hi! I have a problem with my 9 ref Vega 64 rigs… I start the miner, hashrate is better and the power consumption is lower then my other miner. But after few minutes one of rigs psu crashes and 5 vegas stop working. On my other miner there are no crashes. I tried multiple intensity settings and the same thing happens.

Thank you!

Hi! The power draw behavior of this miner is a little special. We have a good plan for addressing it, but it will be a while before we get there. The power draw over time is as low as you can get for CNv8 right now, but during small periods of the execution we need to go full throttle, drawing more power than the rest of the time. It seems to me one of your psus isn't really happy about those ramp-ups after a while.

Have you tried balancing your Vegas a little differently across the psus, assuming you have the raw capacity in watts? It might be the case that one of your psus is more sensitive to the changes in power draw than the other. Or, if it's possible and simple enough, switch the roles of 5 Vega vs 4 Vega+system between the two psus.

[O-Coin]

Hello,

Findings on 3.7

TRM 3.6 Stable on 6 Rigs since release Auto config.  
Just tried 3.7 on 1 Rig Its 6 GPUS 3-RX5808GB 1-RX5804gb and 2-RX570 8GB. I set the 4gb card to 7+7 and removed all OC and undervolt so card is running w stock clocks and voltages.  The same card runs just fine on 3.6 w OC and undervolt.  

https://imgur.com/a/xe6Reww

[kerney666]

Hello,

Findings on 3.7

TRM 3.6 Stable on 6 Rigs since release Auto config.  
Just tried 3.7 on 1 Rig Its 6 GPUS 3-RX5808GB 1-RX5804gb and 2-RX570 8GB. I set the 4gb card to 7+7 and removed all OC and undervolt so card is running w stock clocks and voltages.  The same card runs just fine on 3.6 w OC and undervolt.  

This is so annoying. We had an invalid assumption that we finally could reproduce and nail down and has gotten reports from a lot of users with issues earlier that it's now working fine, but now we have regression issues with other rigs.

Is this random, or the same failure 100% of the time?

[O-Coin]

Happens everytime on this rig. I didnt try on any other rigs I can if you want they are all stable on 3.6

[golya87]

This is my starting command:

Code:

teamredminer.exe --algo=cnv8 --url=stratum+tcp://gulf.moneroocean.stream:10128 --user=45n...aBx --pass=Moria:x --devices=0,1,2,3,4 --cn_config 14+14,14+14,14+14,14+14,14+14

What did I wrong?

Thank you in advance!

Hmm, hashing looks fine, it would rather be something in the rpc communication with Monero Ocean, although we haven't gotten any other reports for this pool. We're working on fixing some small rpc bugs, we'll make sure to test against Monero Ocean as well.

I've get the same error with monero.miningpoolhub.com and wownero.ingest.cryptoknight.cc also.
I've enabled the miner sw in the windows firewall rules also, so it shouldn't be a FW issue.

I've tried running the latest public release (0.3.6) against all three pools now, I don't have any problems mining at gulf.moneroocean.stream:10128, us-east.cryptonight-hub.miningpoolhub.com:20580, wownero.ingest.cryptoknight.cc:50901.

With the same error on all three pools, I'm guessing the issue is something specific about your setup. Have you found any pool that works? Are other CN miners working fine against the pools above on your machine?

I've checked with the latest TRM miner the following pools:
wownero.ingest.cryptoknight.cc
graft.ingest.cryptoknight.cc
xmr-eu1.nanopool.org
europe.cryptonight-hub.miningpoolhub.com
gulf.moneroocean.stream

I've get the same error with SRB miner. With Stak-XMR everything works fine. I've tried with turned off Defender and FW also.

[coke15]

hi

no way to mine stellite with? only v8?

there is a bug(for me) :
on a rig i had many rejected on 1 card----->low diff---->pool kick rig.

possible to implement "watchdog"? in this case,reboot the miner ?or automaticly reduce intensity?

thnaks

[kerney666]

hi

no way to mine stellite with? only v8?

there is a bug(for me) :
on a rig i had many rejected on 1 card----->low diff---->pool kick rig.

possible to implement "watchdog"? in this case,reboot the miner ?or automaticly reduce intensity?

thnaks

Hi! We will add all variants, all time has gone to work in stability and small features since release. We kicked things off with v8, it felt like the natural first choice.

Did you run the latest 0.3.7 version? It added cpu verification of shares, so low diff shares shouldn't really be sent to the pool. Many pools have crap implementations themselves though and say low diff when the share really was for a previous job.

Watchdog functionality, as well as temps/fans monitoring, are on the TODO list.