[ANN] TeamRedMiner - Old Thread

[tvukoman]

Just setup vertcoin with:

1 x rx570 4GB
2 x Vega56 reference
1 x Vega 64 Strix

[2019-02-09 11:35:30] Stats Uptime: 0 days, 00:25:31
[2019-02-09 11:35:30] GPU 0 [49C, fan 22%] lyra2rev3: 42.45Mh/s, avg 42.40Mh/s, pool 49.20Mh/s a:36 r:0 hw:0
[2019-02-09 11:35:30] GPU 1 [56C, fan 72%] lyra2rev3: 85.55Mh/s, avg 85.44Mh/s, pool 85.76Mh/s a:64 r:0 hw:0
[2019-02-09 11:35:30] GPU 2 [50C, fan 70%] lyra2rev3: 99.62Mh/s, avg 99.55Mh/s, pool 80.14Mh/s a:61 r:0 hw:0
[2019-02-09 11:35:30] GPU 3 [55C, fan 72%] lyra2rev3: 85.26Mh/s, avg 85.25Mh/s, pool 69.61Mh/s a:56 r:0 hw:0
[2019-02-09 11:35:30] Total                lyra2rev3: 312.9Mh/s, avg 312.6Mh/s, pool 284.7Mh/s a:217 r:0 hw:0

[slim87]

Just setup vertcoin with:

1 x rx570 4GB
2 x Vega56 reference
1 x Vega 64 Strix

[2019-02-09 11:35:30] Stats Uptime: 0 days, 00:25:31
[2019-02-09 11:35:30] GPU 0 [49C, fan 22%] lyra2rev3: 42.45Mh/s, avg 42.40Mh/s, pool 49.20Mh/s a:36 r:0 hw:0
[2019-02-09 11:35:30] GPU 1 [56C, fan 72%] lyra2rev3: 85.55Mh/s, avg 85.44Mh/s, pool 85.76Mh/s a:64 r:0 hw:0
[2019-02-09 11:35:30] GPU 2 [50C, fan 70%] lyra2rev3: 99.62Mh/s, avg 99.55Mh/s, pool 80.14Mh/s a:61 r:0 hw:0
[2019-02-09 11:35:30] GPU 3 [55C, fan 72%] lyra2rev3: 85.26Mh/s, avg 85.25Mh/s, pool 69.61Mh/s a:56 r:0 hw:0
[2019-02-09 11:35:30] Total                lyra2rev3: 312.9Mh/s, avg 312.6Mh/s, pool 284.7Mh/s a:217 r:0 hw:0

What settings do you have for the VEGA?

[jimmyD30]

I'm getting this too often: " Pool vtc.suprnova.cc rpc timed out after 69 seconds.  Reconnecting."

Me too - different pool tho.

Lyra2rev3, Win 10, Vega 64.

Hello, is dev still maintaining this miner? If so, any fix for this yet? Or at least an acknowledgement after a weeks time since first asked?

Happens with:
0.3.10 / Lyra2rev3 / Windows 10 / amd 18.6.1 / Vega 64
0.3.10 / Lyra2rev3 / Ubuntu 18.04 / amd 18.50 / Vega 64

[kerney666]

I'm getting this too often: " Pool vtc.suprnova.cc rpc timed out after 69 seconds.  Reconnecting."

Me too - different pool tho.

Lyra2rev3, Win 10, Vega 64.

Hello, is dev still maintaining this miner? If so, any fix for this yet? Or at least an acknowledgement after a weeks time since first asked?

Happens with:
0.3.10 / Lyra2rev3 / Windows 10 / amd 18.6.1 / Vega 64
0.3.10 / Lyra2rev3 / Ubuntu 18.04 / amd 18.50 / Vega 64

Hey, sorry about that, this fell between the cracks. I'll get a test going against suprnova tonight. Meanwhile, have you tried adding "--pool_no_ensub"?

[freedom777]

Do you have a ready mod BIOS, or only manual tuning? What program is relevant for this today, I have not modified the BIOS for a long time (the last time it was Hawaii and I don’t remember exactly which programs were used). Maybe you have some link with manual of this question?

No, I don't have bios ready to mine lyra right on - I still gotta use wattman to set core clocks and voltages. For bios editing check here: https://www.overclock.net/forum/67-amd/1592384-fiji-bios-editing-fury-fury-x-nano-radeon-pro-duo.html Though you dont really need it unless your cards can be ulocked, as far as I know only Asus Strix and Sapphire Tri-X(not Nitro) can.

So How i can do 135W on lyrav3  without mod bios, only settings in Windows? Whats coreclock  and   core voltage do you use for this?
Because for me, all what less than -162mV(it is about 200-210W from the wall) is a system hang!

[Divinity666]

So How i can do 135W on lyrav3  without mod bios, only settings in Windows? Whats coreclock  and   core voltage do you use for this?
Because for me, all what less than -162mV(it is about 200-210W from the wall) is a system hang!

900Mhz/975mV

[jimmyD30]

I'm getting this too often: " Pool vtc.suprnova.cc rpc timed out after 69 seconds.  Reconnecting."

Me too - different pool tho.

Lyra2rev3, Win 10, Vega 64.

Hello, is dev still maintaining this miner? If so, any fix for this yet? Or at least an acknowledgement after a weeks time since first asked?

Happens with:
0.3.10 / Lyra2rev3 / Windows 10 / amd 18.6.1 / Vega 64
0.3.10 / Lyra2rev3 / Ubuntu 18.04 / amd 18.50 / Vega 64

Hey, sorry about that, this fell between the cracks. I'll get a test going against suprnova tonight. Meanwhile, have you tried adding "--pool_no_ensub"?

Hi, I haven’t , but will today and report back later, thank you for replying.

[kerney666]

I'm getting this too often: " Pool vtc.suprnova.cc rpc timed out after 69 seconds.  Reconnecting."

Me too - different pool tho.

Lyra2rev3, Win 10, Vega 64.

Hello, is dev still maintaining this miner? If so, any fix for this yet? Or at least an acknowledgement after a weeks time since first asked?

Happens with:
0.3.10 / Lyra2rev3 / Windows 10 / amd 18.6.1 / Vega 64
0.3.10 / Lyra2rev3 / Ubuntu 18.04 / amd 18.50 / Vega 64

Hey, sorry about that, this fell between the cracks. I'll get a test going against suprnova tonight. Meanwhile, have you tried adding "--pool_no_ensub"?

Hi, I haven’t , but will today and report back later, thank you for replying.

I've verified it solved the issue for me against Suprnova. What happens is:

• We send an extranonce subscription on startup.
• Suprnova ignores and drops the requests instead of replying to it with an error.
• After our timeout threshold has passed, we croak due to an outstanding rpc request and display the error message and restart the connection.

We could handle this more gracefully, it's a special case when it's the extranonce subscription that never is replied to and not e.g. a share submit. That said, adding --pool_no_ensub will solve it as well.

Cheers, K

[jimmyD30]

I'm getting this too often: " Pool vtc.suprnova.cc rpc timed out after 69 seconds.  Reconnecting."

Me too - different pool tho.

Lyra2rev3, Win 10, Vega 64.

Hello, is dev still maintaining this miner? If so, any fix for this yet? Or at least an acknowledgement after a weeks time since first asked?

Happens with:
0.3.10 / Lyra2rev3 / Windows 10 / amd 18.6.1 / Vega 64
0.3.10 / Lyra2rev3 / Ubuntu 18.04 / amd 18.50 / Vega 64

Hey, sorry about that, this fell between the cracks. I'll get a test going against suprnova tonight. Meanwhile, have you tried adding "--pool_no_ensub"?

Hi, I haven’t , but will today and report back later, thank you for replying.

I've verified it solved the issue for me against Suprnova. What happens is:

• We send an extranonce subscription on startup.
• Suprnova ignores and drops the requests instead of replying to it with an error.
• After our timeout threshold has passed, we croak due to an outstanding rpc request and display the error message and restart the connection.

We could handle this more gracefully, it's a special case when it's the extranonce subscription that never is replied to and not e.g. a share submit. That said, adding --pool_no_ensub will solve it as well.

Cheers, K

Great, it’s working for me as well on both platforms - thank you!

P.S. This solution is ‘graceful’ enough for me :-)

[tvukoman]

Just setup vertcoin with:

1 x rx570 4GB
2 x Vega56 reference
1 x Vega 64 Strix

[2019-02-09 11:35:30] Stats Uptime: 0 days, 00:25:31
[2019-02-09 11:35:30] GPU 0 [49C, fan 22%] lyra2rev3: 42.45Mh/s, avg 42.40Mh/s, pool 49.20Mh/s a:36 r:0 hw:0
[2019-02-09 11:35:30] GPU 1 [56C, fan 72%] lyra2rev3: 85.55Mh/s, avg 85.44Mh/s, pool 85.76Mh/s a:64 r:0 hw:0
[2019-02-09 11:35:30] GPU 2 [50C, fan 70%] lyra2rev3: 99.62Mh/s, avg 99.55Mh/s, pool 80.14Mh/s a:61 r:0 hw:0
[2019-02-09 11:35:30] GPU 3 [55C, fan 72%] lyra2rev3: 85.26Mh/s, avg 85.25Mh/s, pool 69.61Mh/s a:56 r:0 hw:0
[2019-02-09 11:35:30] Total                lyra2rev3: 312.9Mh/s, avg 312.6Mh/s, pool 284.7Mh/s a:217 r:0 hw:0

What settings do you have for the VEGA?

1408/930 core 500/800 mem - Vega 56
1442/920 core 500/900 mem - Vega 64

[pbfarmer]

How you set memory voltage to 600mV on RX580? It's minimal 750... I tried to set less than 750mV but it really stay at 750mV.

Mem voltage in the profiling tools is not really mem voltage - it's just a floor for core voltage (it's really for the SOC / mem controller.)  So unless you're planning on trying to run your core at 600, there's no use setting mem that low.  Simply make sure it's below core voltage, and it's basically unused.

If you really want to change your mem voltage (which is about 1.6v) you need to get into the bios.

Of course I was mentioned memory controller voltage not memory itself... But I can't set any voltage lower 750 mV on it. If I set lower it stays 750.

There are driver enforced (read from bios) min and max core voltages I believe.

[tvukoman]

Bloody hell it does work... Memory is shown at 500MHz (on the Vega 56's).
I'm testing on x16RT currently (which isn't very memory bound either) and I've dropped power draw massively. Hallelujah.

EDIT: on the Vegas, disabling P1 to P3 works, on the Polaris cards it won't, so I set the values of P1 and P2 equal to P0.

Hmm, for some reason, I cant disable P1 on Vega cards in ONT...

What i'm doing wrong, is it because power play table or driver (use 18.6.1), or clocks?
Also, try to put p0 mem to 500/800 but cant...

mem:
p0 167 / 800
p1 500 / 800
p2 and p3 disabled

GPU:
p0 to p6 disabled
p7 1408 / 930

EDIT: Dragonmike, I can disable P1 P2 and P3 on Polaris (RX570 4GB Nitro+), but Vega...

[iRonNuke]

Hi your miner is great, actually it's the best AMD miner of all I have been mining some Vertcoin lately on my AMD rig. But I wanted to try out Lyra2Rev3 at NiceHash too, but I'm getting "Share above target" all the time and rejected shares. Anything particular I need to do?

[UnclWish]

Hi your miner is great, actually it's the best AMD miner of all I have been mining some Vertcoin lately on my AMD rig. But I wanted to try out Lyra2Rev3 at NiceHash too, but I'm getting "Share above target" all the time and rejected shares. Anything particular I need to do?

Lyra2rev3 normal mines with TR miner on nicehash. Post your bat file.

[iRonNuke]

Hi your miner is great, actually it's the best AMD miner of all I have been mining some Vertcoin lately on my AMD rig. But I wanted to try out Lyra2Rev3 at NiceHash too, but I'm getting "Share above target" all the time and rejected shares. Anything particular I need to do?

Lyra2rev3 normal mines with TR miner on nicehash. Post your bat file.

Thanks for the help! When I should copy/paste it I saw the problem with the config. It said Lyra2Rev2 not 3 I though it was incompatible with NiceHash because it worked just fine with another pool. But a typing error was there

[scryptr]

LYRA2REV3 SCREENSHOT--

The TeamRedMiner (TRM v3.10) is working smoothly on my Vega 64 rig.  Here is a screenshot:


TRM v3.10 mining Lyra2rev3 on Vega 64 rig.

My core/mem clocks are 1507/945.  Core has a reported default of 1630, memory is at the reported default of 945.  This previous week I have been mining at 1507/500, but the rig was less stable and hashed ~10% more slowly.  Running on this 1507/945 setting, the rig is consuming power at the default level, as reported at the console.  Reported default wattage is 260-300W per card; the rig has 4 cards.

--scryptr

[freedom777]

So How i can do 135W on lyrav3  without mod bios, only settings in Windows? Whats coreclock  and   core voltage do you use for this?
Because for me, all what less than -162mV(it is about 200-210W from the wall) is a system hang!

900Mhz/975mV

Whats program do you use for this? and does it make sense to switch memory timings for this card, for others algo?

[Divinity666]

Whats program do you use for this? and does it make sense to switch memory timings for this card, for others algo?

I told you already I use Wattman. Lowering timings improve h\r on daggerhash, as of other algos I dunno what kind of benefit it gives - I never compared. But its not making things worse thats for sure

[ku4eto]

So How i can do 135W on lyrav3  without mod bios, only settings in Windows? Whats coreclock  and   core voltage do you use for this?
Because for me, all what less than -162mV(it is about 200-210W from the wall) is a system hang!

900Mhz/975mV

Whats program do you use for this? and does it make sense to switch memory timings for this card, for others algo?

No, memory timings have absolutely 0 effect here. Its entirely core bound algorithm.

[ep690d]

Hi, can you please add Lyra2v2c0ban? It's has same code like lyra2v2 or lyra2v3 with difference only in some lines. Please do it asap.
Thank you

Please add support to lyra2v2c0ban.

Thanks.