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

[todxx]

Team Red Miner v0.6.0 released

https://github.com/todxx/teamredminer/releases

Changes in v0.6.0

• Added ethash algo support.
• Relaxed ssl/tls cert chain verification.

We've added ethash algo support!

We've put a ton of effort into this release to deliver what we believe is the best ethash miner for AMD GPUs.
Performance advantage over existing miners will vary depending on GPU model and tuning and we've seen results ranging from +0 to +15%.
Vega and VII GPUs tend to see the most benefit, with Vega56s w/ Hynix mem and VIIs doing exceptionally well.
Polaris GPUs will typically see a very modest improvement in hashrate, but should also see some lowered power usage as well.

Please checkout the ETHASH_GENERAL_TUNING.txt doc in the miner release package for more details on tuning.

NOTE: We have observed some anomalous behavior with miner reported vs pool hashrates in competing miners.
We suggest that anyone comparing miners against each other should perform long (24hr+) tests and compare poolside hashrates only.
The more poolside shares that are taken into account during the test, the more accurate the results will be.
We will be posting more information on this soon, as well as tools for externally verifying miner hashrates.

As always, we encourage everyone to post their results and let us know how the miner performs

[1713942842]

1713942842

[1713942842]

1713942842

[1713942842]

1713942842

[1713942842]

1713942842

[todxx]

please include the pool fail-over in the next release. This is a very important option.
Thanks.

Just to note that I do use this mine for all of my AMD GPUs

Hi Apprentice,

Apologies that we didn't get this done in this release.  We recognize that pool failover is an important feature, and we will be adding it in the next release.
To help us get it right, could you describe the failover and/or load balancing features you would like to see added?

[ku4eto]

For those wondering, what performance improvement we can see on Ethash, i asked todxx in the Discord.

8:41 AM] todxx: On polaris we've seen varying results depending on clocks/voltages/timings, typically results are in the +0-2% improvment range, with typical values in the +0.5-1% range
[8:42 AM] todxx: We haven't done extensive tune testing, but so far we've seen that TRM will run the same or slightly better in terms of stability for a given hardware configuration.
[8:42 AM] todxx: Some of our early testers reported being able to lower voltage slightly more than with CM/PM
[8:44 AM] todxx: Also you'll need to keep in mind that I'm referring to poolside hashrate here (I.E. real effective hashrate).  We've noticed that CM/PM are often optimistic about reporting their hashrate compared to actual effective hashrate.
[8:45 AM] todxx: You can see this in PM directly as it prints the effective/pool hashrate in the miner, and it is typically less than the hashrate it reports for GPUs
[8:50 AM] todxx: As for vega, we do see a consistent +1.5-2% over other miners for Vegas with samsung mem.  Vega 56s with hynix mem do much much better with trm and the right tuning, easily hitting 50Mh/s with very low power usage.
[8:51 AM] todxx: For the VII we are seeing +5-7% increase in hashrate compared to other miners.
[8:55 AM] todxx: To get good performance on the VIIs you'll need to make sure you're running the v106 bios, hence the pinned message above with the v106 bios installer.

[Apprentice]

please include the pool fail-over in the next release. This is a very important option.
Thanks.

Just to note that I do use this mine for all of my AMD GPUs

Hi Apprentice,

Apologies that we didn't get this done in this release.  We recognize that pool failover is an important feature, and we will be adding it in the next release.
To help us get it right, could you describe the failover and/or load balancing features you would like to see added?

That would be great.
Simple failover, pool 1, pool 2, pool 3..with # of retries for each pool before switching to the next pool.
Keep checking pool 1 status and go back when it is available.

[cas333]

Please help!  I dont understand why miner doesnt start. This is my bat file

set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_MAX_HEAP_SIZE=100
set GPU_USE_SYNC_OBJECTS=1
teamredminer.exe -a ethash -o stratum+tcp://eu1-etc.ethermine.org:4444 -wal 0xc6147-----------------2614019f0fbe.rig1 -p x --temp_limit=65 --temp_resume=50

[kerney666]

Please help!  I dont understand why miner doesnt start. This is my bat file

set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_MAX_HEAP_SIZE=100
set GPU_USE_SYNC_OBJECTS=1
teamredminer.exe -a ethash -o stratum+tcp://eu1-etc.ethermine.org:4444 -wal 0xc614703e0090a58a26b8c301b7662614019f0fbe.rig1 -p x --temp_limit=65 --temp_resume=50

Wallet argument should be -u, not -wal. That’s the only thing I see, hope it works!

[cas333]

Please help!  I dont understand why miner doesnt start. This is my bat file

set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_MAX_HEAP_SIZE=100
set GPU_USE_SYNC_OBJECTS=1
teamredminer.exe -a ethash -o stratum+tcp://eu1-etc.ethermine.org:4444 -wal 0xc614703e00-----------------2614019f0fbe.rig1 -p x --temp_limit=65 --temp_resume=50

Wallet argument should be -u, not -wal. That’s the only thing I see, hope it works!

Thanks,now is OK

[lncm]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

[NCarter84]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

[lncm]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card. 

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

[kerney666]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card. 

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

[lncm]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card. 

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

Thanks. Great, great work. Now I can use TRM only.

As as you said, other miners do not report real hashrate. Using it for >12h, despite reporting -2 Mh/s than the miner I was using, calculated hashrate @ the pool went up 4 Mh/s...

That said, I'm not getting miner reported hashrate to eth.nanopool.org. How can I turn that on?

[kerney666]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card.  

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

Thanks. Great, great work. Now I can use TRM only.

As as you said, other miners do not report real hashrate. Using it for >12h, despite reporting -2 Mh/s than the miner I was using, calculated hashrate @ the pool went up 4 Mh/s...

That said, I'm not getting miner reported hashrate to eth.nanopool.org. How can I turn that on?

I believe nanopool only can do reported hashrate with the ethproxy protocol. We typically default to one of the other possible protocols. Try adding "--eth_stratum_mode=ethproxy", I think it will solve it for you. Otherwise, let us know and we'll look into it more closely.

[0xcosmos]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

using amdmemtweak cli
created a bat file to apply ref 30 in 6 gpus starting from gpu 0 to gpu 5 index
but after running it
it makes no difference
any way to do it in gui?

[NCarter84]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

using amdmemtweak cli
created a bat file to apply ref 30 in 6 gpus starting from gpu 0 to gpu 5 index
but after running it
it makes no difference
any way to do it in gui?

yes - you can also use the gui. Sometimes ref doesn't make a huge difference too. What type of memory do you have? Post your cli line for reference also.

[lncm]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card.  

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

Thanks. Great, great work. Now I can use TRM only.

As as you said, other miners do not report real hashrate. Using it for >12h, despite reporting -2 Mh/s than the miner I was using, calculated hashrate @ the pool went up 4 Mh/s...

That said, I'm not getting miner reported hashrate to eth.nanopool.org. How can I turn that on?

I believe nanopool only can do reported hashrate with the ethproxy protocol. We typically default to one of the other possible protocols. Try adding "--eth_stratum_mode=ethproxy", I think it will solve it for you. Otherwise, let us know and we'll look into it more closely.

Nopes, it says "Pool eth-eu1.nanopool rpc method "eth_getWork" timed out after 69 seconds. Discarding."

[kerney666]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card.  

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

Thanks. Great, great work. Now I can use TRM only.

As as you said, other miners do not report real hashrate. Using it for >12h, despite reporting -2 Mh/s than the miner I was using, calculated hashrate @ the pool went up 4 Mh/s...

That said, I'm not getting miner reported hashrate to eth.nanopool.org. How can I turn that on?

I believe nanopool only can do reported hashrate with the ethproxy protocol. We typically default to one of the other possible protocols. Try adding "--eth_stratum_mode=ethproxy", I think it will solve it for you. Otherwise, let us know and we'll look into it more closely.

Nopes, it says "Pool eth-eu1.nanopool rpc method "eth_getWork" timed out after 69 seconds. Discarding."

That's nothing to worry about though, but you're still not seeing any reported hashrates? Please confirm and I'll look into it.

[lncm]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card.  

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

Thanks. Great, great work. Now I can use TRM only.

As as you said, other miners do not report real hashrate. Using it for >12h, despite reporting -2 Mh/s than the miner I was using, calculated hashrate @ the pool went up 4 Mh/s...

That said, I'm not getting miner reported hashrate to eth.nanopool.org. How can I turn that on?

I believe nanopool only can do reported hashrate with the ethproxy protocol. We typically default to one of the other possible protocols. Try adding "--eth_stratum_mode=ethproxy", I think it will solve it for you. Otherwise, let us know and we'll look into it more closely.

Nopes, it says "Pool eth-eu1.nanopool rpc method "eth_getWork" timed out after 69 seconds. Discarding."

That's nothing to worry about though, but you're still not seeing any reported hashrates? Please confirm and I'll look into it.

No. It briefly reported (black line), but then it stopped reporting again.

[kerney666]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

Thanks alot! Free +1 Mh/s on each card.  

I have memory strips made with polaris bios editor some 2 years ago, but REF was 5 on all cards.

To set it on command line, the argument should be --REF 30000, right?

No that would rather be for Vegas . For Polaris, it’s just “--REF 30”. You can always inspect the current values to get a feeling for the right scale.
 

Thanks. Great, great work. Now I can use TRM only.

As as you said, other miners do not report real hashrate. Using it for >12h, despite reporting -2 Mh/s than the miner I was using, calculated hashrate @ the pool went up 4 Mh/s...

That said, I'm not getting miner reported hashrate to eth.nanopool.org. How can I turn that on?

I believe nanopool only can do reported hashrate with the ethproxy protocol. We typically default to one of the other possible protocols. Try adding "--eth_stratum_mode=ethproxy", I think it will solve it for you. Otherwise, let us know and we'll look into it more closely.

Nopes, it says "Pool eth-eu1.nanopool rpc method "eth_getWork" timed out after 69 seconds. Discarding."

That's nothing to worry about though, but you're still not seeing any reported hashrates? Please confirm and I'll look into it.

No. It briefly reported (black line), but then it stopped reporting again.

Thank you, had a report from a different pool where the reported hashrate became stale, will investigate.

[pbfarmer]

Very cool, I just left it running on a 4 polaris machine.

Anyone knows of good mem timings to use with AMDmemtweak with Elpida and Hynix 4 Gb cards?

ref 30

using amdmemtweak cli
created a bat file to apply ref 30 in 6 gpus starting from gpu 0 to gpu 5 index
but after running it
it makes no difference
any way to do it in gui?

I ran into the same problem - but I also confirmed (using amdmemtweak --current) that the settings weren't actually being applied.  I could only get it to work a single time after each machine power-cycle.  Tried the gui version (including the original and xl versions) and had the same issue.

Then i finally figured out there was some conflict while also running HWInfo64.  So maybe try a full power cycle, make sure you don't run any hardware monitoring apps (hwinfo, gpu-z, etc) and try the cli again - and use the '--current' option after to make sure your settings actually get applied as expected.