Pages:
Author

Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 22. (Read 85791 times)

member
Activity: 658
Merit: 86
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"?
jr. member
Activity: 64
Merit: 1
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
jr. member
Activity: 53
Merit: 1
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?
jr. member
Activity: 69
Merit: 5
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
newbie
Activity: 8
Merit: 0
VEGA FE 93 MH/s
VEGA 56 86-89 MH/s

anyone know how to control the fan manually? my vega FE runs at 40%, I'd like it to run at 50%. tia

You can try this command (keep in mind its global for all cards , this sh file will not control only one of them) .

wget http://drakyla.org/atifans.sh && chmod 755 atifans.sh

After this do ./atifans.sh -s 50                    (where 50 is the % of the fans you want to be used .. can  be 60/70/100 or 0 .. up to you) .

Works fine on all 470/480/570/580 .. should work on vegas too .

Regards
sr. member
Activity: 1484
Merit: 253
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.
member
Activity: 340
Merit: 29
Boy, dumping the memory down to P0 saves A LOT of power.

RX 580, at 1240/1750 does 49.6Mh/s at ~100W per GPU (as per GPU-Z).
Rig has 3x 580, 1x570 and was doing ~530W at wall.

Entered memory P0 state, and lost ~20W per 580 according to GPU-Z. Wall power consumption dropped from 530 to 440W.
Performance dropped with ~0.6MH/s per card.

Best performance/power consmption seems to be around 1200-1250Mhz.

Getting 190.8Mh/s for 440W at wall with 4 cards.

RX 570 - ~45.9MH/s
3x RX 580 - ~49.08MH/s.
Core clocks are all 1240Mhz. Core voltage is ~0.875V-0.893V (2x 0.875, 1x0.887, 1x0.893V).

Raising core voltage to sustain 1280Mhz core raises performance to 50.45MH/s per RX 580, but raises power consumption by ~30W (from 440 to 470). So, 10% power increase for 1% performance increase.


Yeah this algo isn't about memory it seems. I also dumped my Vegas at 500 MHz and RX series at 300 MHz. No big difference in hashrate.

My rig have the following cards;
3 x RX 560 4 GB 18 MH/s
4 x RX 570 4 GB 39 MH/s
2 x RX 580 8 GB 43-44 MH/s
2 x Vega 56 85-86 MH/s

My total rig wattage is exactly 1000W at 470 MH/s. (Lower power consumption than at CryptoNight V8!). Because I have quite expensive electricity I have quite aggressive undervoltating, 820 mV at core for RX 570/580 and memory all down to 600 mV. The Vega's have like 880 mV at core and 800 mV at memory (can't set lower because restriction in drivers apperantly. At this rates the rig is rock solid stable, havn't crashed one single time since like the fork of Vertcoin.

Till now, with my expensive electricity 0.1268$ kWh it have been profitable, like 1.5$-0.3$ (yesterday), but not anymore. So now the fun is over Smiley
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.
jr. member
Activity: 194
Merit: 4
Quote from: ku4eto
I do not use OverDrivenTool, its annoying as hell. Simply downclocked via Wattman.
It's really the first time EVER I've read the above.
If anything is annoying as hell, and buggy to death and beyond, it's Wattman. Overdriventool is the easiest, most straightforward and logical piece of software to set clocks for AMD. The first thing I do when I install new drivers is to make 300% sure "Radeon Settings" is unchecked.

Sorry, but i do not rely a lot on 3rd party tools, that i would need to wait for a new version, if they suddenly stop working because of the new drivers. Wattman is easy to use and has all the bells and whistles i need. If you do not like it, do not use it. There is nothing buggy about it.

It is impossible you tried OverdriveNTool you would not have said such foolishness Smiley

Pretty sure i did. I did not like it. Do i have to like it? Its called personal opinion.
Quote from: ku4eto
I do not use OverDrivenTool, its annoying as hell. Simply downclocked via Wattman.
It's really the first time EVER I've read the above.
If anything is annoying as hell, and buggy to death and beyond, it's Wattman. Overdriventool is the easiest, most straightforward and logical piece of software to set clocks for AMD. The first thing I do when I install new drivers is to make 300% sure "Radeon Settings" is unchecked.

Sorry, but i do not rely a lot on 3rd party tools, that i would need to wait for a new version, if they suddenly stop working because of the new drivers. Wattman is easy to use and has all the bells and whistles i need. If you do not like it, do not use it. There is nothing buggy about it.

It is absolutely buggy - stopped using it a couple days after first trying (for mining) because of all the bugs.  The only time ODNT has required an update was during the transition from 18.x to 19.x drivers, due to the introduction of mem profiling and some other stuff.

The only bug that i have encountered - the Zero Fan one, was fixed with the last update. So, still, no bugs for me.
member
Activity: 340
Merit: 29
Quote from: ku4eto
I do not use OverDrivenTool, its annoying as hell. Simply downclocked via Wattman.
It's really the first time EVER I've read the above.
If anything is annoying as hell, and buggy to death and beyond, it's Wattman. Overdriventool is the easiest, most straightforward and logical piece of software to set clocks for AMD. The first thing I do when I install new drivers is to make 300% sure "Radeon Settings" is unchecked.

Sorry, but i do not rely a lot on 3rd party tools, that i would need to wait for a new version, if they suddenly stop working because of the new drivers. Wattman is easy to use and has all the bells and whistles i need. If you do not like it, do not use it. There is nothing buggy about it.

It is absolutely buggy - stopped using it a couple days after first trying (for mining) because of all the bugs.  The only time ODNT has required an update was during the transition from 18.x to 19.x drivers, due to the introduction of mem profiling and some other stuff.
jr. member
Activity: 145
Merit: 1
Quote from: ku4eto
I do not use OverDrivenTool, its annoying as hell. Simply downclocked via Wattman.
It's really the first time EVER I've read the above.
If anything is annoying as hell, and buggy to death and beyond, it's Wattman. Overdriventool is the easiest, most straightforward and logical piece of software to set clocks for AMD. The first thing I do when I install new drivers is to make 300% sure "Radeon Settings" is unchecked.

Sorry, but i do not rely a lot on 3rd party tools, that i would need to wait for a new version, if they suddenly stop working because of the new drivers. Wattman is easy to use and has all the bells and whistles i need. If you do not like it, do not use it. There is nothing buggy about it.

It is impossible you tried OverdriveNTool you would not have said such foolishness Smiley
jr. member
Activity: 194
Merit: 4
Quote from: ku4eto
I do not use OverDrivenTool, its annoying as hell. Simply downclocked via Wattman.
It's really the first time EVER I've read the above.
If anything is annoying as hell, and buggy to death and beyond, it's Wattman. Overdriventool is the easiest, most straightforward and logical piece of software to set clocks for AMD. The first thing I do when I install new drivers is to make 300% sure "Radeon Settings" is unchecked.

Sorry, but i do not rely a lot on 3rd party tools, that i would need to wait for a new version, if they suddenly stop working because of the new drivers. Wattman is easy to use and has all the bells and whistles i need. If you do not like it, do not use it. There is nothing buggy about it.
hero member
Activity: 1274
Merit: 556
Quote from: ku4eto
I do not use OverDrivenTool, its annoying as hell. Simply downclocked via Wattman.
It's really the first time EVER I've read the above.
If anything is annoying as hell, and buggy to death and beyond, it's Wattman. Overdriventool is the easiest, most straightforward and logical piece of software to set clocks for AMD. The first thing I do when I install new drivers is to make 300% sure "Radeon Settings" is unchecked.
jr. member
Activity: 194
Merit: 4
Boy, dumping the memory down to P0 saves A LOT of power.

RX 580, at 1240/1750 does 49.6Mh/s at ~100W per GPU (as per GPU-Z).
Rig has 3x 580, 1x570 and was doing ~530W at wall.

Entered memory P0 state, and lost ~20W per 580 according to GPU-Z. Wall power consumption dropped from 530 to 440W.
Performance dropped with ~0.6MH/s per card.

Best performance/power consmption seems to be around 1200-1250Mhz.

Getting 190.8Mh/s for 440W at wall with 4 cards.

RX 570 - ~45.9MH/s
3x RX 580 - ~49.08MH/s.
Core clocks are all 1240Mhz. Core voltage is ~0.875V-0.893V (2x 0.875, 1x0.887, 1x0.893V).

Raising core voltage to sustain 1280Mhz core raises performance to 50.45MH/s per RX 580, but raises power consumption by ~30W (from 440 to 470). So, 10% power increase for 1% performance increase.

How do you actually prevent it to go to anything higher than P0? Do you just add ";0" at the end of P1, P2 and P3 lines in Overdriventool? Will it even start if you do that? Mem clock is set at something ludicrously low (167 MHz) at P0...
I do not use OverDrivenTool, its annoying as hell. Simply downclocked via Wattman. Seems like going below 1750Mhz on memory forces the driver to use P0 if the load is sufficiently low for some reason.

Boy, dumping the memory down to P0 saves A LOT of power.

RX 580, at 1240/1750 does 49.6Mh/s at ~100W per GPU (as per GPU-Z).
Rig has 3x 580, 1x570 and was doing ~530W at wall.

Entered memory P0 state, and lost ~20W per 580 according to GPU-Z. Wall power consumption dropped from 530 to 440W.
Performance dropped with ~0.6MH/s per card.

Best performance/power consmption seems to be around 1200-1250Mhz.

Getting 190.8Mh/s for 440W at wall with 4 cards.

RX 570 - ~45.9MH/s
3x RX 580 - ~49.08MH/s.
Core clocks are all 1240Mhz. Core voltage is ~0.875V-0.893V (2x 0.875, 1x0.887, 1x0.893V).

Raising core voltage to sustain 1280Mhz core raises performance to 50.45MH/s per RX 580, but raises power consumption by ~30W (from 440 to 470). So, 10% power increase for 1% performance increase.


Yeah this algo isn't about memory it seems. I also dumped my Vegas at 500 MHz and RX series at 300 MHz. No big difference in hashrate.

My rig have the following cards;
3 x RX 560 4 GB 18 MH/s
4 x RX 570 4 GB 39 MH/s
2 x RX 580 8 GB 43-44 MH/s
2 x Vega 56 85-86 MH/s

My total rig wattage is exactly 1000W at 470 MH/s. (Lower power consumption than at CryptoNight V8!). Because I have quite expensive electricity I have quite aggressive undervoltating, 820 mV at core for RX 570/580 and memory all down to 600 mV. The Vega's have like 880 mV at core and 800 mV at memory (can't set lower because restriction in drivers apperantly. At this rates the rig is rock solid stable, havn't crashed one single time since like the fork of Vertcoin.

Till now, with my expensive electricity 0.1268$ kWh it have been profitable, like 1.5$-0.3$ (yesterday), but not anymore. So now the fun is over Smiley
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.

You can always mod the BIOS and set the IMC voltage lower. Although, i wouldnt recommend going too low.
jr. member
Activity: 145
Merit: 1

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.

It doesn't change anything, same comsuption at 600 than 820.
sr. member
Activity: 1484
Merit: 253
Boy, dumping the memory down to P0 saves A LOT of power.

RX 580, at 1240/1750 does 49.6Mh/s at ~100W per GPU (as per GPU-Z).
Rig has 3x 580, 1x570 and was doing ~530W at wall.

Entered memory P0 state, and lost ~20W per 580 according to GPU-Z. Wall power consumption dropped from 530 to 440W.
Performance dropped with ~0.6MH/s per card.

Best performance/power consmption seems to be around 1200-1250Mhz.

Getting 190.8Mh/s for 440W at wall with 4 cards.

RX 570 - ~45.9MH/s
3x RX 580 - ~49.08MH/s.
Core clocks are all 1240Mhz. Core voltage is ~0.875V-0.893V (2x 0.875, 1x0.887, 1x0.893V).

Raising core voltage to sustain 1280Mhz core raises performance to 50.45MH/s per RX 580, but raises power consumption by ~30W (from 440 to 470). So, 10% power increase for 1% performance increase.


Yeah this algo isn't about memory it seems. I also dumped my Vegas at 500 MHz and RX series at 300 MHz. No big difference in hashrate.

My rig have the following cards;
3 x RX 560 4 GB 18 MH/s
4 x RX 570 4 GB 39 MH/s
2 x RX 580 8 GB 43-44 MH/s
2 x Vega 56 85-86 MH/s

My total rig wattage is exactly 1000W at 470 MH/s. (Lower power consumption than at CryptoNight V8!). Because I have quite expensive electricity I have quite aggressive undervoltating, 820 mV at core for RX 570/580 and memory all down to 600 mV. The Vega's have like 880 mV at core and 800 mV at memory (can't set lower because restriction in drivers apperantly. At this rates the rig is rock solid stable, havn't crashed one single time since like the fork of Vertcoin.

Till now, with my expensive electricity 0.1268$ kWh it have been profitable, like 1.5$-0.3$ (yesterday), but not anymore. So now the fun is over Smiley
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.
hero member
Activity: 1274
Merit: 556
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.
hero member
Activity: 1274
Merit: 556
Boy, dumping the memory down to P0 saves A LOT of power.

RX 580, at 1240/1750 does 49.6Mh/s at ~100W per GPU (as per GPU-Z).
Rig has 3x 580, 1x570 and was doing ~530W at wall.

Entered memory P0 state, and lost ~20W per 580 according to GPU-Z. Wall power consumption dropped from 530 to 440W.
Performance dropped with ~0.6MH/s per card.

Best performance/power consmption seems to be around 1200-1250Mhz.

Getting 190.8Mh/s for 440W at wall with 4 cards.

RX 570 - ~45.9MH/s
3x RX 580 - ~49.08MH/s.
Core clocks are all 1240Mhz. Core voltage is ~0.875V-0.893V (2x 0.875, 1x0.887, 1x0.893V).

Raising core voltage to sustain 1280Mhz core raises performance to 50.45MH/s per RX 580, but raises power consumption by ~30W (from 440 to 470). So, 10% power increase for 1% performance increase.

How do you actually prevent it to go to anything higher than P0? Do you just add ";0" at the end of P1, P2 and P3 lines in Overdriventool? Will it even start if you do that? Mem clock is set at something ludicrously low (167 MHz) at P0...
jr. member
Activity: 98
Merit: 6
Boy, dumping the memory down to P0 saves A LOT of power.

RX 580, at 1240/1750 does 49.6Mh/s at ~100W per GPU (as per GPU-Z).
Rig has 3x 580, 1x570 and was doing ~530W at wall.

Entered memory P0 state, and lost ~20W per 580 according to GPU-Z. Wall power consumption dropped from 530 to 440W.
Performance dropped with ~0.6MH/s per card.

Best performance/power consmption seems to be around 1200-1250Mhz.

Getting 190.8Mh/s for 440W at wall with 4 cards.

RX 570 - ~45.9MH/s
3x RX 580 - ~49.08MH/s.
Core clocks are all 1240Mhz. Core voltage is ~0.875V-0.893V (2x 0.875, 1x0.887, 1x0.893V).

Raising core voltage to sustain 1280Mhz core raises performance to 50.45MH/s per RX 580, but raises power consumption by ~30W (from 440 to 470). So, 10% power increase for 1% performance increase.


Yeah this algo isn't about memory it seems. I also dumped my Vegas at 500 MHz and RX series at 300 MHz. No big difference in hashrate.

My rig have the following cards;
3 x RX 560 4 GB 18 MH/s
4 x RX 570 4 GB 39 MH/s
2 x RX 580 8 GB 43-44 MH/s
2 x Vega 56 85-86 MH/s

My total rig wattage is exactly 1000W at 470 MH/s. (Lower power consumption than at CryptoNight V8!). Because I have quite expensive electricity I have quite aggressive undervoltating, 820 mV at core for RX 570/580 and memory all down to 600 mV. The Vega's have like 880 mV at core and 800 mV at memory (can't set lower because restriction in drivers apperantly. At this rates the rig is rock solid stable, havn't crashed one single time since like the fork of Vertcoin.

Till now, with my expensive electricity 0.1268$ kWh it have been profitable, like 1.5$-0.3$ (yesterday), but not anymore. So now the fun is over Smiley
jr. member
Activity: 194
Merit: 4
Boy, dumping the memory down to P0 saves A LOT of power.

RX 580, at 1240/1750 does 49.6Mh/s at ~100W per GPU (as per GPU-Z).
Rig has 3x 580, 1x570 and was doing ~530W at wall.

Entered memory P0 state, and lost ~20W per 580 according to GPU-Z. Wall power consumption dropped from 530 to 440W.
Performance dropped with ~0.6MH/s per card.

Best performance/power consmption seems to be around 1200-1250Mhz.

Getting 190.8Mh/s for 440W at wall with 4 cards.

RX 570 - ~45.9MH/s
3x RX 580 - ~49.08MH/s.
Core clocks are all 1240Mhz. Core voltage is ~0.875V-0.893V (2x 0.875, 1x0.887, 1x0.893V).

Raising core voltage to sustain 1280Mhz core raises performance to 50.45MH/s per RX 580, but raises power consumption by ~30W (from 440 to 470). So, 10% power increase for 1% performance increase.
jr. member
Activity: 120
Merit: 4
Lyra2REv3 TEST

VEGA 56 84mh/s 1408/900 950/910 200w

VEGA 64 air coole 96mhs/s 1408/900 1000/900 200w

rx570 45mh/s 1290/900 2000/880  110w

Wow, really good rate.
Pages:
Jump to: