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

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.

Yesterday run teamredminer 0.3.7 on my 470. The most stable cn_config for me is 4-4, its so low because i think monitor plugged in videocard. I got 670 H/s with 7/64 and 18.6.1

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

Yesterday run teamredminer 0.3.7 on my 470. The most stable cn_config for me is 4-4, its so low because i think monitor plugged in videocard. I got 670 H/s with 7/64 and 18.6.1

That is much lower than what you would typically expect from a 470.  Have you enabled compute mode on the card?  Have you modified the memory straps on it?

[peterboy1]

is there a problem with dev pool right now? reconnecting every now and then.

[todxx]

is there a problem with dev pool right now? reconnecting every now and then.

There was a problem about 3 hours ago that would have caused miners to reconnect.  Other than that, you shouldn't be seeing it reconnect frequently.
Are you seeing frequent reconnects to the dev pool?

[lebuawu2]

Hi,

any estimation when you planning to release heavy variant algorithm?

Thanks.

[kerney666]

Hi,

any estimation when you planning to release heavy variant algorithm?

Thanks.

We’re discussing the roadmap currently, there are a few different options. If we choose heavy for the next step it will still be two weeks, I’d say.

[N2DCRYPT]

Todxx/K66,

I know you guys have plenty on your plate... figured no hurt in asking though--any plans on optimizing for VFE's or too niche a product?

N2

[kerney666]

Todxx/K66,

I know you guys have plenty on your plate... figured no hurt in asking though--any plans on optimizing for VFE's or too niche a product?

N2

Would be great fun, and we have one for testing! That said, there are a few things higher up on the prio list though .

[pbfarmer]

what method are you guys using to have a fixed core clock ?
i set it up for let's say 1400mhz for vega56 using overdriventool but when watching it with HWiNFO is not the same it's about 1350Mhz
any hint appreciated

from yesterday I experience same problem with Vega 56 / 64 cards.

Have you tried disabling all lower p-states in OverdriveNTool, i.e. click the little text "P2", "P3" etc left of the MHz column so they are greyed out? Only using the highest state has helped me sometimes to force the driver to use the specified clocks.

Yes kerney, that is my standard settings in OvedriveNtool.

Just did some more test and found, when applying overdrive and look in the HWiNFO64 i see that GPUP7 clocks is set on  higher values of set in overdrive.ini ?
And when i start miner values go down?
Down in profiles of ovedrivetool.ini i added actual clock values read by HWiNFO before and after start miner:

Run_OverdriveNTool.bat (OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Sapphire -p2Nitro_RX570 -p3Asus_Vega64 -p4Gigabyte)
[General]
ShowBusNumber=1
ShowPnpString=0
ShowAdapterIndex=0
ShowFriendlyName=0
ShowRegistryKey=1
MainWindowLeft=984
MainWindowTop=244

[Profile_0]
Name=Sapphire
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0    before start miner        after start miner
GPU_P7=1408;955      1437;955            1378 and 1381 (changeing)
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1088;945
Fan_Min=3500
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=0

[Profile_1]
Name=Nitro_RX570
GPU_P0=300;750;0
GPU_P1=588;765;0
GPU_P2=952;943;0
GPU_P3=1041;1012;0
GPU_P4=1106;1075;0
GPU_P5=1168;1143;0
GPU_P6=1209;1150;0
GPU_P7=1170;850
Mem_P0=300;750;0
Mem_P1=1000;800;0
Mem_P2=1970;900
Fan_Min=576
Fan_Max=2150
Fan_Target=50
Fan_Acoustic=1340
Power_Temp=85
Power_Target=0

[Profile_2]
Name=Asus_Vega64
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0
GPU_P7=1490;930             1535;930        1463 and 1466 and 1467 (changeing)
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1100;910
Fan_Min=2300
Fan_Max=3500
Fan_Target=50
Fan_Acoustic=1600
Power_Temp=85
Power_Target=0

[Profile_3]
Name=Gigabyte
GPU_P0=852;900;0
GPU_P1=991;900;0
GPU_P2=1084;900;0
GPU_P3=1138;900;0
GPU_P4=1150;900;0
GPU_P5=1202;900;0
GPU_P6=1212;905;0
GPU_P7=1408;950                1444;950        1381 and 1382 and 1385 (changeing)         
Mem_P0=167;900;0
Mem_P1=500;900;0
Mem_P2=800;900;0
Mem_P3=1070;950
Fan_Min=3350
Fan_Max=4900
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=0

This is standard behavior of Vegas, due to ACG/AVFS.  The lower your voltages, the more clock throttling under load.  This has nothing to do with the miner, other than the fact that it puts a certain signature load on the GPU.

[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

[tvukoman]

what method are you guys using to have a fixed core clock ?
i set it up for let's say 1400mhz for vega56 using overdriventool but when watching it with HWiNFO is not the same it's about 1350Mhz
any hint appreciated

from yesterday I experience same problem with Vega 56 / 64 cards.

Have you tried disabling all lower p-states in OverdriveNTool, i.e. click the little text "P2", "P3" etc left of the MHz column so they are greyed out? Only using the highest state has helped me sometimes to force the driver to use the specified clocks.

Yes kerney, that is my standard settings in OvedriveNtool.

Just did some more test and found, when applying overdrive and look in the HWiNFO64 i see that GPUP7 clocks is set on  higher values of set in overdrive.ini ?
And when i start miner values go down?
Down in profiles of ovedrivetool.ini i added actual clock values read by HWiNFO before and after start miner:

Run_OverdriveNTool.bat (OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Sapphire -p2Nitro_RX570 -p3Asus_Vega64 -p4Gigabyte)

GPU_P6=1212;905;0    before start miner        after start miner
GPU_P7=1408;955      1437;955            1378 and 1381 (changeing)

GPU_P7=1490;930             1535;930        1463 and 1466 and 1467 (changeing)

GPU_P7=1408;950                1444;950        1381 and 1382 and 1385 (changeing)         

This is standard behavior of Vegas, due to ACG/AVFS.  The lower your voltages, the more clock throttling under load.  This has nothing to do with the miner, other than the fact that it puts a certain signature load on the GPU.

Thank you pbfarmer that makes sense.
You force me to learn more of Advanced Clock Generator(ACG)/Advanced Voltage Frequency Scaling(AVFS) :-)
Never noticed that behavior before in HWiNFO. Found some interesting stuff here: https://www.reddit.com/r/Amd/comments/7dzc9j/vega_56_w_64_bios_tweak_result_good_chip_or/

[kerney666]

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

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

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.

[kerney666]

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.

[netmebtc]

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

[ku4eto]

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?

[netmebtc]

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?

[pbfarmer]

what method are you guys using to have a fixed core clock ?
i set it up for let's say 1400mhz for vega56 using overdriventool but when watching it with HWiNFO is not the same it's about 1350Mhz
any hint appreciated

from yesterday I experience same problem with Vega 56 / 64 cards.

Have you tried disabling all lower p-states in OverdriveNTool, i.e. click the little text "P2", "P3" etc left of the MHz column so they are greyed out? Only using the highest state has helped me sometimes to force the driver to use the specified clocks.

Yes kerney, that is my standard settings in OvedriveNtool.

Just did some more test and found, when applying overdrive and look in the HWiNFO64 i see that GPUP7 clocks is set on  higher values of set in overdrive.ini ?
And when i start miner values go down?
Down in profiles of ovedrivetool.ini i added actual clock values read by HWiNFO before and after start miner:

Run_OverdriveNTool.bat (OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Sapphire -p2Nitro_RX570 -p3Asus_Vega64 -p4Gigabyte)

GPU_P6=1212;905;0    before start miner        after start miner
GPU_P7=1408;955      1437;955            1378 and 1381 (changeing)

GPU_P7=1490;930             1535;930        1463 and 1466 and 1467 (changeing)

GPU_P7=1408;950                1444;950        1381 and 1382 and 1385 (changeing)         

This is standard behavior of Vegas, due to ACG/AVFS.  The lower your voltages, the more clock throttling under load.  This has nothing to do with the miner, other than the fact that it puts a certain signature load on the GPU.

Thank you pbfarmer that makes sense.
You force me to learn more of Advanced Clock Generator(ACG)/Advanced Voltage Frequency Scaling(AVFS) :-)
Never noticed that behavior before in HWiNFO. Found some interesting stuff here: https://www.reddit.com/r/Amd/comments/7dzc9j/vega_56_w_64_bios_tweak_result_good_chip_or/

No problem.  You may not have noticed it before because previous versions of cryptonight were much less taxing on the core, so the clock (frequency) scaling, especially at 950mv, was likely significantly less aggressive.

[ku4eto]

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?

"terry1" is not a valid wallet address if this is exactly what you are inputting there.

[todxx]

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.