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

[todxx]

Hello. It seems that the load on the Grin29 Radeon VII is not optimal enough. the card's power consumption jumps back and forth. Are there plans to fix this in future versions?

Unfortunately that's just the nature of the cuckoo algos.
They start out with a very compute intensive first step and then the following steps are memory intensive.
So the power will go up during the compute parts and down during the memory parts.

[1715262179]

1715262179

[1715262179]

1715262179

[1715262179]

1715262179

[UnclWish]

You can specify configs for the cards like with the cn_config, but it's eth_config instead.  To make all cards run A mode, you can use --eth_config=A
You can set a specific mode and intensity with something like so: --eth_config=A300
You can also provide a list with one entry per card, like so: --eth_config=A300,B400,A,B

And it's need to optimize speed... On Phoenix with double kernels my RX 580 gives about 600KH/s (about 2%) more speed. Even if 0,65% dev fee not true, speed on TRM eth too low in compare with PM.

I'm guessing you haven't read any of the last ~20 posts in this thread.  You might want to go back and look through them a bit.
TL;DR: Phoenix miner reports hashrate ~2.9% higher than it actually gets.  So by your measurement, we're getting about 0.9% better actual hashrate (I.E. your pool hashrate will go up 0.9%).

Number after A or B is the intensity? A200 is less intensive than A400?

I read last several pages and understand that Claymore and Phoenix give fake speeds, but I look into accepted speed on the pool-side and Phoenix gives me the same speed as showed accepted speed in miner. And for now it sometimes a bit more than TRM and sometims a bit lower.
But thanks for answers.

[kerney666]

You can specify configs for the cards like with the cn_config, but it's eth_config instead.  To make all cards run A mode, you can use --eth_config=A
You can set a specific mode and intensity with something like so: --eth_config=A300
You can also provide a list with one entry per card, like so: --eth_config=A300,B400,A,B

And it's need to optimize speed... On Phoenix with double kernels my RX 580 gives about 600KH/s (about 2%) more speed. Even if 0,65% dev fee not true, speed on TRM eth too low in compare with PM.

I'm guessing you haven't read any of the last ~20 posts in this thread.  You might want to go back and look through them a bit.
TL;DR: Phoenix miner reports hashrate ~2.9% higher than it actually gets.  So by your measurement, we're getting about 0.9% better actual hashrate (I.E. your pool hashrate will go up 0.9%).

Number after A or B is the intensity? A200 is less intensive than A400?

I read last several pages and understand that Claymore and Phoenix give fake speeds, but I look into accepted speed on the pool-side and Phoenix gives me the same speed as showed accepted speed in miner. And for now it sometimes a bit more than TRM and sometims a bit lower.
But thanks for answers.

Hi UnclWish!

I truly believe you only mean well, and I _really_ believe you want to run the miner most optimal for yourself, and you (like all miners) would like to be able to test and verify miners to compare for yourselves. Like todxx mentioned, Phoenix miner has been underperforming its displayed hash rates with an avg of -2.9% right now across all our runs. That has now been verified in tests done outside of our control as well, but still mostly with people that we know, and I'd love if people like you, that we only really interact with here in this forum, would run some tests as well.

Therefore, I would like to offer you compensation in XMR for mining air for a few days so you can test for yourself using our released ethash miner testing tool. I've tried to present the math and statistics in the documentation for the tool, and show that 24h poolside tests using a single gpu or even full rig are just way too random to trust. We need a much much larger sample size, and that's why we built and released the tool in the first place.

It is indeed difficult on a single 580 though, it will take maybe 5 days to do a single test, and naturally, it must run 100% stable during that time, no crashes or internet outages etc. Maybe you have more than one 580 to test with? If you're interested, try to get started yourself, then we'll answer any questions you might have here in public to you get going. Then you report back when the test is done.

For people thinking that running a 5+ days long test with a much lower diff than normal pools sounds ridiculous, unfortunately it's what you need if you only do a single gpu. The test is just a very controlled way of keeping track of your mining over a longer period of time, where pools normally only present a sliding window of the last N hours.

Again, the tool and documentation is available here:

https://github.com/Kerney666/trm-ethash-miner-tester/

Cheers, Kerney

[UnclWish]

You can specify configs for the cards like with the cn_config, but it's eth_config instead.  To make all cards run A mode, you can use --eth_config=A
You can set a specific mode and intensity with something like so: --eth_config=A300
You can also provide a list with one entry per card, like so: --eth_config=A300,B400,A,B

And it's need to optimize speed... On Phoenix with double kernels my RX 580 gives about 600KH/s (about 2%) more speed. Even if 0,65% dev fee not true, speed on TRM eth too low in compare with PM.

I'm guessing you haven't read any of the last ~20 posts in this thread.  You might want to go back and look through them a bit.
TL;DR: Phoenix miner reports hashrate ~2.9% higher than it actually gets.  So by your measurement, we're getting about 0.9% better actual hashrate (I.E. your pool hashrate will go up 0.9%).

Number after A or B is the intensity? A200 is less intensive than A400?

I read last several pages and understand that Claymore and Phoenix give fake speeds, but I look into accepted speed on the pool-side and Phoenix gives me the same speed as showed accepted speed in miner. And for now it sometimes a bit more than TRM and sometims a bit lower.
But thanks for answers.

Hi UnclWish!

I truly believe you only mean well, and I _really_ believe you want to run the miner most optimal for yourself, and you (like all miners) would like to be able to test and verify miners to compare for yourselves. Like todxx mentioned, Phoenix miner has been underperforming its displayed hash rates with an avg of -2.9% right now across all our runs. That has now been verified in tests done outside of our control as well, but still mostly with people that we know, and I'd love if people like you, that we only really interact with here in this forum, would run some tests as well.

Therefore, I would like to offer you compensation in XMR for mining air for a few days so you can test for yourself using our released ethash miner testing tool. I've tried to present the math and statistics in the documentation for the tool, and show that 24h poolside tests using a single gpu or even full rig are just way too random to trust. We need a much much larger sample size, and that's why we built and released the tool in the first place.

It is indeed difficult on a single 580 though, it will take maybe 5 days to do a single test, and naturally, it must run 100% stable during that time, no crashes or internet outages etc. Maybe you have more than one 580 to test with? If you're interested, try to get started yourself, then we'll answer any questions you might have here in public to you get going. Then you report back when the test is done.

For people thinking that running a 5+ days long test with a much lower diff than normal pools sounds ridiculous, unfortunately it's what you need if you only do a single gpu. The test is just a very controlled way of keeping track of your mining over a longer period of time, where pools normally only present a sliding window of the last N hours.

Again, the tool and documentation is available here:

https://github.com/Kerney666/trm-ethash-miner-tester/

Cheers, Kerney

Hi, Kerney!

Thanks for offer! I'd love to test with you on my 580 cards, but unfortunately I can't control them all time, and rigs at all. They not only mine ))) But I'm somehow believe your words. Sometimes reported accepted hashrate in PM and Claymore is too differes from pool...
Now I'm testing your miner. Hope it better and without fakes )))

Thanks again! And I hope you add in future updates clocks and voltages control at least for windows.

[todxx]

Team Red Miner v0.6.1 released

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

Changes in v0.6.1

• Added pool failover and load balancing.
• Added better error messages when failing to allocate eth DAG buffers.
• Added server name for TLS SNI.
• Added automatic setting for environment variables for 4GB GPUs.
• Extended maximum length of usernames and passwords (for some merged mining setups).
• Added report of pool stats.
• Changed initial pool auto detect mode to eth proxy.
• Various fixes for submitting hashrate to pools.

It's been a long time coming, but we finally did it; we added pool failover support
We also added pool hashrate stats to help with tracking multi-pool use.
For the more advanced users, we also support load balancing pool strategies.  (See the --help output for more info)
If you want to try it out, there is an example start_multipool.sh/bat file included in the miner packages.

[UnclWish]

Team Red Miner v0.6.1 released

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

Changes in v0.6.1

• Added pool failover and load balancing.
• Added better error messages when failing to allocate eth DAG buffers.
• Added server name for TLS SNI.
• Added automatic setting for environment variables for 4GB GPUs.
• Extended maximum length of usernames and passwords (for some merged mining setups).
• Added report of pool stats.
• Changed initial pool auto detect mode to eth proxy.
• Various fixes for submitting hashrate to pools.

It's been a long time coming, but we finally did it; we added pool failover support
We also added pool hashrate stats to help with tracking multi-pool use.
For the more advanced users, we also support load balancing pool strategies.  (See the --help output for more info)
If you want to try it out, there is an example start_multipool.sh/bat file included in the miner packages.

Good! Now testing it!

[chimaeraa]

there is no update for monero fork?

[NCarter84]

there is no update for monero fork?

No -- they won't be updating their miner for the CPU fork.. Unfortunately.

[chimaeraa]

there is no update for monero fork?

No -- they won't be updating their miner for the CPU fork.. Unfortunately.

it's good miner app. i love it.
but why?

[dragonmike]

there is no update for monero fork?

No -- they won't be updating their miner for the CPU fork.. Unfortunately.

it's good miner app. i love it.
but why?

Because RandomX is pointless for GPUs... and Teamred focuses on making miners for GPUs, simple as that.
Partly why they've now also released EThash.

[WMIRK]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

[chimaeraa]

there is no update for monero fork?

No -- they won't be updating their miner for the CPU fork.. Unfortunately.

it's good miner app. i love it.
but why?

Because RandomX is pointless for GPUs... and Teamred focuses on making miners for GPUs, simple as that.
Partly why they've now also released EThash.

thanx.
yes i use that and it's better than other miner, for my vegas.

[kerney666]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

We did include a short tuning guide in the release (ETHASH_GENERAL_TUNING.tx) that you can use as a base. It includes examples timings and clocks, check the section for Vega 64 and let us know if you still have issues.

[Spoonbox]

I got couple Hynix Vega 56 cards so TRM really surprised me when it boosted my CN hashrate from 1,9k to 2,2k a while back.
However yesterday I got new surprise with Eth hashrate going from 44 Mh (phoenix/claymore) to 50,7 Mh. Only settings non stock are 1250/900 core, 950/900 memory, RCDRD 12, RC 35 and tREF 15600. Been stable now for 24h, power draw is 130W according to GPU-Z. Need to tweak a bit more when I got some spare time, with tighter settings I was able to get 52 Mh with same power draw but it crashed after hour or so.
Thanks TRM for keeping Hynix bois in the game!

[UnclWish]

1st look on 0.6.1 eth mining RX 580 cards after not so much time...
It's better tham 0.6.0. Less rejects, good accepted speed, stable. Nice work!

[chimaeraa]

i got this error  when switch to eth
[2019-12-01 14:52:03] Dev pool connection was closed by remote side.
[2019-12-01 14:52:03] Mining will proceed at reduced rate while not connected to dev pool.

[WMIRK]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

We did include a short tuning guide in the release (ETHASH_GENERAL_TUNING.tx) that you can use as a base. It includes examples timings and clocks, check the section for Vega 64 and let us know if you still have issues.

I got it. Now one of my cards is not stable. Can you give me the link for Vega 64 section tuning please?

[chimaeraa]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

We did include a short tuning guide in the release (ETHASH_GENERAL_TUNING.tx) that you can use as a base. It includes examples timings and clocks, check the section for Vega 64 and let us know if you still have issues.

I got it. Now one of my cards is not stable. Can you give me the link for Vega 64 section tuning please?

i got stable hash with no HW error.

core : 1150 mem : 1090  V:900m 50mh/s

amdmemorytweak --CL 20 --RAS 30 --RCDRD 14 --RCDWR 12 --RC 44 --RP 14 --RRDS 3 --RRDL 6 --RTP 5 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 14 --REF 17000 --RFC 249


but pool hash  very different .
i got 1020Mh/s in my system and in pool it's about 500Mh - 5% reject and no hw error.

[kerney666]

What are the settings for Vega 64  mining for ETHASH  (etherium) please?

ONT settings  (voltage) please advice.

We did include a short tuning guide in the release (ETHASH_GENERAL_TUNING.tx) that you can use as a base. It includes examples timings and clocks, check the section for Vega 64 and let us know if you still have issues.

I got it. Now one of my cards is not stable. Can you give me the link for Vega 64 section tuning please?

i got stable hash with no HW error.

core : 1150 mem : 1090  V:900m 50mh/s

amdmemorytweak --CL 20 --RAS 30 --RCDRD 14 --RCDWR 12 --RC 44 --RP 14 --RRDS 3 --RRDL 6 --RTP 5 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 14 --REF 17000 --RFC 249


but pool hash  very different .
i got 1020Mh/s in my system and in pool it's about 500Mh - 5% reject and no hw error.

Which pool is this? And, how many accepted shares when you had 500 MH/s poolside?

[kerney666]

I got couple Hynix Vega 56 cards so TRM really surprised me when it boosted my CN hashrate from 1,9k to 2,2k a while back.
However yesterday I got new surprise with Eth hashrate going from 44 Mh (phoenix/claymore) to 50,7 Mh. Only settings non stock are 1250/900 core, 950/900 memory, RCDRD 12, RC 35 and tREF 15600. Been stable now for 24h, power draw is 130W according to GPU-Z. Need to tweak a bit more when I got some spare time, with tighter settings I was able to get 52 Mh with same power draw but it crashed after hour or so.
Thanks TRM for keeping Hynix bois in the game!

Honestly, I'm a humble guy, but I gotta say I think we REALLY did nail it for V56 Hynix and ethash. We were surprised ourselves, we do most of our dev and testing on V56/64 ref cards with Samsung mem. The experience is that it's both simpler and more stable to push the V56 Hynix > 50 MH/s compared to V56 Samsung cards.

So, nice to see someone noticing and also didn't have any troubles getting it up and running properly! The normal interaction with users most often starts with an issue .