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

[netmebtc]

This is XMR pool of https://www.poolin.com/ ,   I can use cast_xmr to connect this pool now.  So wait you release a new version to solve it. Thanks.

terry1

Hi dev,my 6xvega cannot login pool.Do you have any idea?

bat is :    teamredminer.exe -a cnv8 -o stratum+tcp://xmrv7-bj.ss.poolin.com:443 -u terry1.%computername%   -p x

Aaaaand where is the wallet address?

Hi netmebtc,

It appears that this pool doesn't follow the standard json rpc protocol in yet a new and different way than all the other pools we have tested on.
We will make a change to the miner to handle this in the next release, until then I suggest using a different pool.
If you absolutely want to use this pool and no other, you can also try to run through a proxy, although I'm not 100% sure that will fix the issue.

[1715256646]

1715256646

[Doucesti]

Great job on this miner!
But, does anyone know why I get 1.850kh/s on average on my miner with 1x vega56 and on two different pools (nano and supportxmr) I get an average of approx. 1.75kh/s ?

Thank you!

[peterboy1]

btw, what to do if you got hw error? what voltage should i increase?

[SpceGhst]

btw, what to do if you got hw error? what voltage should i increase?

Not sure voltage is your problem.  Probably has more to do with default intensity settings.  If 8+8 is throwing HW errors, try changing to 8+7.

[18-Terahash]

Dear, I really look forward to the function of the failover pool in backup-pools.txt

[GreyGhost_rc]

One of my rigs, the cards are being picked up by software like afterburner, device manager etc., but no mining software sees the cards. Any ideas?

[ku4eto]

One of my rigs, the cards are being picked up by software like afterburner, device manager etc., but no mining software sees the cards. Any ideas?

Change the OpenCL platform.

[GreyGhost_rc]

Eish, sorry to ask, but how do I do that?

[ku4eto]

Eish, sorry to ask, but how do I do that?

You could have looked in the --help menu...
Miner.exe --help.

--gpu-platform <arg> Select OpenCL platform ID to use for GPU mining (default: -1).

Set it to 0 or 1.

[golya87]

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.

After a Windows reinstall, with 18.5.1/18.6.1/18.11.1 in the cryptoknight and MPH pool still no luck.

Is there a log or debug mode in the miner? Maybe that could help to find my problem.

I mean, it seems clear that there's something very uncommon going on here given that you're the only one I know of with this problem and you're also seeing the same thing with SRB. It rather feels related to your networking setup. Personally, I would install Wireshark next and look at the network traffic to see what's going on. Really shooting from the hip here, but do you have any weird IPv6 setup?

Another thing you could post here would be the output of "netstat -n -p tcp" from the command prompt when (1) xmr-stak is running and (2) right when TRM or SRB is trying to connect to the same pool.

Today I've tested the mining with direct connection to the ISP with PPPoE. Everything is working fine.
Now I'm searching for my network's problem. I've a not so special setup. Asus router with a TP-Link switch, everything is in IPv4.

Update:

I've found the problem!
After I've turned off my Asus router's AiProtection/Network Protection/Malicious Sites Blocking "feature" the mining was started without any error.

Thank you guys for the help!

[todxx]

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.

After a Windows reinstall, with 18.5.1/18.6.1/18.11.1 in the cryptoknight and MPH pool still no luck.

Is there a log or debug mode in the miner? Maybe that could help to find my problem.

I mean, it seems clear that there's something very uncommon going on here given that you're the only one I know of with this problem and you're also seeing the same thing with SRB. It rather feels related to your networking setup. Personally, I would install Wireshark next and look at the network traffic to see what's going on. Really shooting from the hip here, but do you have any weird IPv6 setup?

Another thing you could post here would be the output of "netstat -n -p tcp" from the command prompt when (1) xmr-stak is running and (2) right when TRM or SRB is trying to connect to the same pool.

Today I've tested the mining with direct connection to the ISP with PPPoE. Everything is working fine.
Now I'm searching for my network's problem. I've a not so special setup. Asus router with a TP-Link switch, everything is in IPv4.

Update:

I've found the problem!
After I've turned off my Asus router's AiProtection/Network Protection/Malicious Sites Blocking "feature" the mining was started without any error.

Thank you guys for the help!

That's great!  Glad we could help

[professorkuusamo]

Hello.
After 2 days of mine one of rigs droped connection.all rigs has same ip,config,wallet,worker.another rigs work well.version of mainer 0.3.7.on different pools problem rig work well.

https://imgur.com/275VgsD
https://imgur.com/U7qFp9H

[mrpenta]

Great job on this miner!
But, does anyone know why I get 1.850kh/s on average on my miner with 1x vega56 and on two different pools (nano and supportxmr) I get an average of approx. 1.75kh/s ?

Thank you!

I  have 6x vega 64 and test my rig in two different pools ,I got an average 100h less than miner reported each card.whats the problem?

[peterboy1]

^

erm did you put dev fee into consideration?

[todxx]

Great job on this miner!
But, does anyone know why I get 1.850kh/s on average on my miner with 1x vega56 and on two different pools (nano and supportxmr) I get an average of approx. 1.75kh/s ?

Thank you!

I  have 6x vega 64 and test my rig in two different pools ,I got an average 100h less than miner reported each card.whats the problem?

Can you guys provide a bit more information?
How long did you run the miner?
How many shares were submitted to the pool during your test?
Where any shares rejected?  Were there any hw errors?
How does the pool report hashrate?  Are you looking at a 24 hour average reported by the pool?
Which of the 3 hashrates printed by the miner are you comparing to the pool hashrate?

Can you post the output of the miner at the end of your test?

[mrpenta]

Great job on this miner!
But, does anyone know why I get 1.850kh/s on average on my miner with 1x vega56 and on two different pools (nano and supportxmr) I get an average of approx. 1.75kh/s ?

Thank you!

I  have 6x vega 64 and test my rig in two different pools ,I got an average 100h less than miner reported each card.whats the problem?

Can you guys provide a bit more information?
How long did you run the miner?
How many shares were submitted to the pool during your test?
Where any shares rejected?  Were there any hw errors?
How does the pool report hashrate?  Are you looking at a 24 hour average reported by the pool?
Which of the 3 hashrates printed by the miner are you comparing to the pool hashrate?

Can you post the output of the miner at the end of your test?

I ran the test for 24h in stock settings (200w limit bios) in support xmr pool and I cant mine grft in hashvault or cryptonight cc and cnv8 in nicehash because  I got lots of rejected shares. I will put the output for 24 h tonight.

[Doucesti]

Can you guys provide a bit more information?
How long did you run the miner?
How many shares were submitted to the pool during your test?
Where any shares rejected?  Were there any hw errors?
How does the pool report hashrate?  Are you looking at a 24 hour average reported by the pool?
Which of the 3 hashrates printed by the miner are you comparing to the pool hashrate?

Can you post the output of the miner at the end of your test?

I've run the miner for a good 4-5 days on nanopool, each time I checked, saw the average xmr mined approx. 7% lower then whattomine and cryptocompare resulted (with deducing pool and dev fee) and hashrate 6% lower.
I've run on supportxmr for 24hours, still 6% lower. But now It seems more reasonable after 48 hours... will update!

I don't know about shares, supportxmr adds all my other miners.
No share rejected, no hw errors.
I am comparing the last hashrate of the miner, (pool)

Maybe nanopool was the problem, maybe because I have other, less powerfull miners on it?

[kerney666]

Can you guys provide a bit more information?
How long did you run the miner?
How many shares were submitted to the pool during your test?
Where any shares rejected?  Were there any hw errors?
How does the pool report hashrate?  Are you looking at a 24 hour average reported by the pool?
Which of the 3 hashrates printed by the miner are you comparing to the pool hashrate?

Can you post the output of the miner at the end of your test?

I've run the miner for a good 4-5 days on nanopool, each time I checked, saw the average xmr mined approx. 7% lower then whattomine and cryptocompare resulted (with deducing pool and dev fee) and hashrate 6% lower.
I've run on supportxmr for 24hours, still 6% lower. But now It seems more reasonable after 48 hours... will update!

I don't know about shares, supportxmr adds all my other miners.
No share rejected, no hw errors.
I am comparing the last hashrate of the miner, (pool)

Maybe nanopool was the problem, maybe because I have other, less powerfull miners on it?

You know, this is a little interesting. Nanopool has a broken rpc implementation which causes issues when e.g. submitting two or more shares in quick succession. Now, we assumed that we'd still get replies for all submitted shares, but there could cases where they actually drop rpc requests. I didn't do the fix though, need to check with todxx.

Comparing pool payouts is a different thing though. Unless you're sure the pools hit exactly 100% avg luck over the same period, it doesn't say much. The poolside hashrate displayed in the miner should match your miner hashrate minus dev fee and any rejected shares. If that looks good, we can't really do much more from a miner dev perspective. If that number is ok, but the pool reports a different hashrate, something is fishy.

[fenomenyaa]

something wrong on nanopool with this miner newer seen smthg like this on SRB.and sometimes rig power consumption decrase to 100w from 1300w's

all it's clearly possible to understand from vega's fan noise.Usualy do this every 5 min. maybe much more early.

Code:

2018-11-10 22:54:53] Pool xmr-eu1.nanopool.org invalid RPC ID received.  (If this error repeats, try using the --pool_broken_rpc option.)
[2018-11-10 22:54:53] Pool xmr-eu1.nanopool.org failed to parse server rpc: {"id":40,"jsonrpc":"2.0","result":{"status":"OK"},"error":null}
[2018-11-10 22:54:54] Stats Uptime: 0 days, 00:43:01
[2018-11-10 22:54:54] GPU 0 - cnv8: 1.016kh/s, avg 1.009kh/s, pool 1.211kh/s a:26 r:0 hw:0

Yes, quite clearly documented both in the release docs, and for your convenience also in the log you’re pasting yourself.

Have you enabled —pool_broken_rpc as mentioned above? We might do this by default going forward. The issue is that nanopool can’t handle multiple outstanding requests.

Cheers, K

hi

already add" —pool_broken_rpc to config " but it seems that i'ts same same.After this stuation some of the cards on rigs takes vddc to 1.15v(and have to reconfigıre overdrivventool) and too much heat and consumption appears.i switched all rigs back to srb,no problem on vega side..

[heavyarms1912]

@kerney666

when's the gpu watchdog feature going to be added.  The miner loses a card after several hours and it's not usually the same card.