[ANN] TeamRedMiner - Old Thread

[webgkv]

All rigs with ASUS ROG RX580 8Gb have initialization Issues and the miner starts successfully only about one in ten times. Also cards ASUS ROG RX570 work fully successfully.
Please correct!

https://i.ibb.co/d73N0Gt/RX580rig2-amd-rx580-rig2-1.png
https://i.ibb.co/Dk6yVdF/RX580rig2-amd-rx580-rig2-2.png

[kerney666]

All rigs with ASUS ROG RX580 8Gb have initialization Issues and the miner starts successfully only about one in ten times. Also cards ASUS ROG RX570 work fully successfully.
Please correct!

Please run with —debug and dump the output of a failed init run here or in a pm to me. Tbh, the only similar issues I’ve seen have been due to unstable mem oc. Does this happen at all clocks, incl stock? Moreover, do you run anything else on the rig concurrently, any cpu mining etc?

[sharmanov]

Will this miner work on Radeon VII? Trying to find fastest PHI2 and XMR miner for Vega architecture

[webgkv]

Please run with —debug and dump the output of a failed init run here or in a pm to me. Tbh, the only similar issues I’ve seen have been due to unstable mem oc. Does this happen at all clocks, incl stock? Moreover, do you run anything else on the rig concurrently, any cpu mining etc?

Thanks for the answer! Looks like the problem was in CPU mining. The RX470 rigs haves more powerful processors from Intel are installed - Intel Pentium G4400, since there are 6 cards each, and the RX580 rigs have processors from AMD - Athlon X4 845 (work with 4 cards) and Phemon II X2 B59 (work with 2 cards).

I understand it, if run the lyra2rev3, it can not use the CPU mining?

[kerney666]

Will this miner work on Radeon VII? Trying to find fastest PHI2 and XMR miner for Vega architecture

I have ran TRM on Radeon VII, but we need to release a new version that recognizes the new device string. Also, ROCm is a little messier than Windows and amdgpu-pro. We will try to get that out shortly. However, CN will need to be optimized for the VII, the current kernels run ok but not optimally. That will most probably not be included in a first release supporting Radeon VII.

[kerney666]

Please run with —debug and dump the output of a failed init run here or in a pm to me. Tbh, the only similar issues I’ve seen have been due to unstable mem oc. Does this happen at all clocks, incl stock? Moreover, do you run anything else on the rig concurrently, any cpu mining etc?

Thanks for the answer! Looks like the problem was in CPU mining. The RX470 rigs haves more powerful processors from Intel are installed - Intel Pentium G4400, since there are 6 cards each, and the RX580 rigs have processors from AMD - Athlon X4 845 (work with 4 cards) and Phemon II X2 B59 (work with 2 cards).

I understand it, if run the lyra2rev3, it can not use the CPU mining?

It’s only an init thing, we have a somewhat special init procedure compared to other miners. When the gpu miner is running you should be able to start and run the cpu miner just fine.

Also, I think it could work if you give the gpu miner highest or real-time priority as well.

[dragonmike]

Will this miner work on Radeon VII? Trying to find fastest PHI2 and XMR miner for Vega architecture

I have ran TRM on Radeon VII, but we need to release a new version that recognizes the new device string. Also, ROCm is a little messier than Windows and amdgpu-pro. We will try to get that out shortly. However, CN will need to be optimized for the VII, the current kernels run ok but not optimally. That will most probably not be included in a first release supporting Radeon VII.

My friend, maybe you shouldn't waste too much time on Monerov8 with the imminent fork... Your efforts would probably be better spent on the new algo... and that other family of algos I believe I have mentioned to you a couple of times in the past...

[Pe_Da]

The miner (Nicehash - lyra2rev3) crashes regularly my Vega64 and with that my rig. Some driver, voltage and clocks tested, unfortunately no change.
Other algorythm like Beam and Ethereum works quite stable about weeks.

Please fix it, the performance is incredible.

[joseph32]

The miner (Nicehash - lyra2rev3) crashes regularly my Vega64 and with that my rig. Some driver, voltage and clocks tested, unfortunately no change.
Other algorythm like Beam and Ethereum works quite stable about weeks.

Please fix it, the performance is incredible.

Try to run your Vega64 with P4, which gives nearly same hashrate as P7, but saves you ~50W per card. Runs 100% stable with 0 crashes.

[sharmanov]

Radeon VII support any time soon? Not sure what happened to my earlier post asking this.

[Pe_Da]

The miner (Nicehash - lyra2rev3) crashes regularly my Vega64 and with that my rig. Some driver, voltage and clocks tested, unfortunately no change.
Other algorythm like Beam and Ethereum works quite stable about weeks.

Please fix it, the performance is incredible.

Try to run your Vega64 with P4, which gives nearly same hashrate as P7, but saves you ~50W per card. Runs 100% stable with 0 crashes.

What do you mean exactly, should I set the clocks to P4 level? I tried this already, no solution.

[kerney666]

Radeon VII support any time soon? Not sure what happened to my earlier post asking this.

https://bitcointalk.org/index.php?topic=5027811.msg49799677#msg49799677

Five posts above this.

[sharmanov]

Radeon VII support any time soon? Not sure what happened to my earlier post asking this.

https://bitcointalk.org/index.php?topic=5027811.msg49799677#msg49799677

Five posts above this.

Well I feel dumb... 😳 thanks for the info

[wacholek]

The miner (Nicehash - lyra2rev3) crashes regularly my Vega64 and with that my rig. Some driver, voltage and clocks tested, unfortunately no change.
Other algorythm like Beam and Ethereum works quite stable about weeks.

Please fix it, the performance is incredible.

Try to run your Vega64 with P4, which gives nearly same hashrate as P7, but saves you ~50W per card. Runs 100% stable with 0 crashes.

What do you mean exactly, should I set the clocks to P4 level? I tried this already, no solution.

Your problems are normal because your overheating Vega on standard clocks. This algo is core-intensive so it have to be tuned carefully.
I have 4 Vega's 64 LC in room temp 18*C.
Configuration is very problematic and it need a lot of afford.
Settings for my vegas:
https://ibb.co/6RkwHNB

That sets my cards to P2/P3 (0.950V) and boost the clock up to 1500Mhz.
That consumes 212W of power and give me 108Mh/s per cards.


My max results where at 1.050V and 1630Mhz. Cards power where 265W and give me 120Mh/s.
But those settings gave to much stress to the core and cause instability (hot spot at 70*C on water)
Temps are:
GPU thermal diode 38*C
GPU HBM temperature 36*C
GPU Hot Spot temperature 62*C
https://ibb.co/1TV7JWj

All of this where my settings and works for me and I do not encourage anyone to use it.

By the way. Miner 0.3.10 is rock-stable on my equipment.

[joseph32]

Your card runs in P7, not P2/3. And I think you will consume more Watt at the wall in P7 than just 200.

[Pe_Da]

The miner (Nicehash - lyra2rev3) crashes regularly my Vega64 and with that my rig. Some driver, voltage and clocks tested, unfortunately no change.
Other algorythm like Beam and Ethereum works quite stable about weeks.

Please fix it, the performance is incredible.

Try to run your Vega64 with P4, which gives nearly same hashrate as P7, but saves you ~50W per card. Runs 100% stable with 0 crashes.

What do you mean exactly, should I set the clocks to P4 level? I tried this already, no solution.

Your problems are normal because your overheating Vega on standard clocks. This algo is core-intensive so it have to be tuned carefully.
I have 4 Vega's 64 LC in room temp 18*C.
Configuration is very problematic and it need a lot of afford.
Settings for my vegas:
https://ibb.co/6RkwHNB

That sets my cards to P2/P3 (0.950V) and boost the clock up to 1500Mhz.
That consumes 212W of power and give me 108Mh/s per cards.


My max results where at 1.050V and 1630Mhz. Cards power where 265W and give me 120Mh/s.
But those settings gave to much stress to the core and cause instability (hot spot at 70*C on water)
Temps are:
GPU thermal diode 38*C
GPU HBM temperature 36*C
GPU Hot Spot temperature 62*C
https://ibb.co/1TV7JWj

All of this where my settings and works for me and I do not encourage anyone to use it.

By the way. Miner 0.3.10 is rock-stable on my equipment.

Thanks for the tipp, my last try, I will increase the voltage again and test the setup.

Stay tuned.

[bbvedf]

...

I do not have Vegas (ive 4x RX580), but I really appreciate your post: Configuration, step by step, captures, ... very complete!

[jimmyD30]

Hello, does anyone know if this miner on Win10 requires a large page file like some other miners with other algos?

[wacholek]

Hello, does anyone know if this miner on Win10 requires a large page file like some other miners with other algos?

My page file is set on 64GB for my 4 Vega 64 rig. I have absolutely no problem with this or any other miner.

Your card runs in P7, not P2/3. And I think you will consume more Watt at the wall in P7 than just 200.

It is not that simple with the P-states on Vega. Theoretically you are right. Cards is running on p7. But the core/voltage ratio is set like on P2 state.
Vega sets core clock based on the core voltage. This is a major principle in all known reference Vegas. So setting core voltage on 1.2V you can do what ever you wont with the clock and set clock will be more less the same. Limit is the power.
But when you set core voltage at 1.000V and clock at 1600Mhz will result only about 1300Mhz on the core because this is the clock for P3 state as default.
So lower the core voltage value on P7 will result lower core clock corresponding to that voltage. In my case set 1.000V but in reality cards keeping 0.950V which results about 1500Mhz even if my P7 core clock is set to 1700Mhz.
All my 4 Vegas consumes 986W of power at the wall and that include PCI-E slot power and PCI-E 2x8pin socket power. I use 2 1200W HSTNS-PD19 Platinum PSU because at that power level it is only worm and  very quiet. So 214W from HWinfo is not that inaccurate since it is not at the wall power.

[joseph32]

You are right. Did a self-test and was surprised

Played a bit around and ended up with nearly same settings as yours. Everything above 110 MH/s will be less stable in the long run.