[ANN] TeamRedMiner - Old Thread

[Elder III]

~4.55 on MTP with a Radeon VII; which is very nice but it's using close to 250 watts at 1.0 volts whereas mining XMR uses about 170 watts at the same settings.  I haven't tried any other tweaks yet to see if the power can be lowered while maintaining hashrate.

[kerney666]

~4.55 on MTP with a Radeon VII; which is very nice but it's using close to 250 watts at 1.0 volts whereas mining XMR uses about 170 watts at the same settings.  I haven't tried any other tweaks yet to see if the power can be lowered while maintaining hashrate.

Unfortunately, the algo is what it is, we've done what we can with this bad boy. As a comparison, a 1080ti pulls > 220W to hit 4.2-4.3 MH/s.  

I'm quite certain you can hit a better efficiency on the VII using a lower core clk, but you'll lose hashrate. Mem isn't very important, pull it down as much as you can, or until you see the hashrate taking a hit. I should really take one of my own VIIs for a tuning trip and see where I end up.

[sharmanov]

Does TRM support CN-GPU Algo?

[250xmining]

Hello,

It would be awesome if TRM could add support for CN_Conceal!!

250xMining

[Dvijuha]

Hello guys! my hashrate on vega 64 LC is down to 1500 on new ver. of miner. in old ver. i have 2200 hashes. What i need to do to up my hashrate? (i dont want to change timings video card firmware because want to save warranty). Why hashrate in new version is down?

[kerney666]

Hello guys! my hashrate on vega 64 LC is down to 1500 on new ver. of miner. in old ver. i have 2200 hashes. What i need to do to up my hashrate? (i dont want to change timings video card firmware because want to save warranty). Why hashrate in new version is down?

Can you be more specific about which versions you mean with “new” and “old” versions of the miner? Also, please specify operating system and driver version.

In short, nothing has changed lately for CN variants, and I haven’t heard of any issues except for one guy that got increased hashrates with 0.5.6 (also shouldn’t happen  ). So, not sure what’s going on really. I have two Vega 64 LCs, run one under win, the other under Linux. I haven’t noticed any issues with CN/r hashrates myself.

[Miner Addict]

Hi Devs,

Have you test Polaris and Vega at Progpow ??

Because U are the Expert on AMD Card

[Dvijuha]

Hello guys! my hashrate on vega 64 LC is down to 1500 on new ver. of miner. in old ver. i have 2200 hashes. What i need to do to up my hashrate? (i dont want to change timings video card firmware because want to save warranty). Why hashrate in new version is down?

Can you be more specific about which versions you mean with “new” and “old” versions of the miner? Also, please specify operating system and driver version.

In short, nothing has changed lately for CN variants, and I haven’t heard of any issues except for one guy that got increased hashrates with 0.5.6 (also shouldn’t happen  ). So, not sure what’s going on really. I have two Vega 64 LCs, run one under win, the other under Linux. I haven’t noticed any issues with CN/r hashrates myself.

sorry in 0.5.6 problem is off. in 0.5.5 or 0.5.4 or 0.5.3 i see this problem.. Yesterday delete bad version with 1500 hashes because update to newest and all became good. Thank you for your good job!

[SigiSinatra]

Grin29 (Cuckarood29) would be awesome cause my little GTX1060 make 3,2sol and vega "only" 3,7sol (nbminer vs lolminer)

i´m sure you can tweak Vega over 4sol

Should we release c29d (pretty good chance we'll do so), I can personally guarantee you it will be > 4 g/s for any Vega at conservative clocks or I'll both eat my shorts and give you a free version.

I'm getting 4.4~4.7 per vega on C29 which is basically nothing comparing to 1,2 on C31.
You need to achieve at least 7.5~8 on C29 to be equal to current 1,2 g/s which vegas provide on C31.

[issie81]

Grin29 (Cuckarood29) would be awesome cause my little GTX1060 make 3,2sol and vega "only" 3,7sol (nbminer vs lolminer)

i´m sure you can tweak Vega over 4sol

Should we release c29d (pretty good chance we'll do so), I can personally guarantee you it will be > 4 g/s for any Vega at conservative clocks or I'll both eat my shorts and give you a free version.

I'm getting 4.4~4.7 per vega on C29 which is basically nothing comparing to 1,2 on C31.
You need to achieve at least 7.5~8 on C29 to be equal to current 1,2 g/s which vegas provide on C31.

How do you get 1.2 on a Vega ( i assume 56/64 and not the latest vii?)

[soothaa]

Is anyone else getting the bug where the "total" hashrate line goes empty? Miner seems to be running..

[kerney666]

Is anyone else getting the bug where the "total" hashrate line goes empty? Miner seems to be running..

Hi soothaa! Never heard of this bug. Is it something with the terminal colors?

[todxx]

Team Red Miner v0.5.7 released

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

Changes in v0.5.7

• Added CN conceal algo for Conceal (CCX).
• Added cuckarood29 algo for grin.

This release brings a couple new algos: CN conceal and cuckarood29!

Cuckarood29 is quite picky about memory timings.  Tight timings are needed to get good performance on this algo, however this algo is very memory heavy and timings that are stable on other algos may not be stable here.
For ballpark hashrates, we've seen 580s run between 3.5g/s and 3.8g/s, and Vega64s range between 6g/s and 7.4g/s depending on clocks and timings.

[Elder III]

Just for reference sake I'm getting about 9.85 hashrate at ~175 watts on a Radeon VII.  Nicely done Team Red.

[sharmanov]

Me too, getting 9.8-10GPS on Radeon VII... Wish C31 would get an uplift for Radeon VII also

[kokodesu]

Using TRMv0.5.7 with algo mtp, d29, c31 causes HW error and crashes.
This does not occur with TRMv0.5.6.
The cause is unknown, but I will report it.

OS HiveOS or mmpOS
LINUX driver 19.2 or 18.40
RIG VEGA56x1, RX570x5, RX580x2

[kerney666]

Using TRMv0.5.7 with algo mtp, d29, c31 causes HW error and crashes.
This does not occur with TRMv0.5.6.
The cause is unknown, but I will report it.

OS HiveOS or mmpOS
LINUX driver 19.2 or 18.40
RIG VEGA56x1, RX570x5, RX580x2

Hi! MTP and c31 didn’t change at all between 0.5.6 and 0.5.7, goes for both gpu and host-side code, so it’s very strange if you see reproducible issues appearing in 0.5.7 for those two . C29d was added in 0.5.7 and can be problematic to tune at times.

Which gpu(s) are crashing? Always the same or random? Always a Vega or Polaris?

[iRonNuke]

I'm having some issues when trying to mine Grin 29/31. Just assigning the GPUs with 8 GB. MTP works fine. If I also exclude the last GPU, it works.

[2019-08-10 12:42:40] Auto-detected AMD OpenCL platform 0
[2019-08-10 12:42:50] Initializing GPU 0.
[2019-08-10 12:42:51] Initializing GPU 1.
[2019-08-10 12:42:52] Initializing GPU 2.
[2019-08-10 12:42:53] Initializing GPU 3.
[2019-08-10 12:42:55] Initializing GPU 4.
[2019-08-10 12:42:56] Initializing GPU 5.
[2019-08-10 12:42:57] Initializing GPU 6.
[2019-08-10 12:42:58] Failed to initialize device idx 10 (-32)
[2019-08-10 12:43:00] Successful clean shutdown.

[kerney666]

I'm having some issues when trying to mine Grin 29/31. Just assigning the GPUs with 8 GB. MTP works fine. If I also exclude the last GPU, it works.

[2019-08-10 12:42:40] Auto-detected AMD OpenCL platform 0
[2019-08-10 12:42:50] Initializing GPU 0.
[2019-08-10 12:42:51] Initializing GPU 1.
[2019-08-10 12:42:52] Initializing GPU 2.
[2019-08-10 12:42:53] Initializing GPU 3.
[2019-08-10 12:42:55] Initializing GPU 4.
[2019-08-10 12:42:56] Initializing GPU 5.
[2019-08-10 12:42:57] Initializing GPU 6.
[2019-08-10 12:42:58] Failed to initialize device idx 10 (-32)
[2019-08-10 12:43:00] Successful clean shutdown.

C29/C31 are true memory hogs. They will use > 7GB per gpu, while MTP is "only" using ~4.3GB. The error above indicates that the driver won't let us allocate vram for GPU 6, and I'm guessing it's because there is no host memory address space to use for the mapping.

How much swap do you have available? Can you make sure it's at least 8GB x NrGPUs?
 

[iRonNuke]

I'm having some issues when trying to mine Grin 29/31. Just assigning the GPUs with 8 GB. MTP works fine. If I also exclude the last GPU, it works.

[2019-08-10 12:42:40] Auto-detected AMD OpenCL platform 0
[2019-08-10 12:42:50] Initializing GPU 0.
[2019-08-10 12:42:51] Initializing GPU 1.
[2019-08-10 12:42:52] Initializing GPU 2.
[2019-08-10 12:42:53] Initializing GPU 3.
[2019-08-10 12:42:55] Initializing GPU 4.
[2019-08-10 12:42:56] Initializing GPU 5.
[2019-08-10 12:42:57] Initializing GPU 6.
[2019-08-10 12:42:58] Failed to initialize device idx 10 (-32)
[2019-08-10 12:43:00] Successful clean shutdown.

C29/C31 are true memory hogs. They will use > 7GB per gpu, while MTP is "only" using ~4.3GB. The error above indicates that the driver won't let us allocate vram for GPU 6, and I'm guessing it's because there is no host memory address space to use for the mapping.

How much swap do you have available? Can you make sure it's at least 8GB x NrGPUs?
 

Thanks! It was that easy, I had a little too little swap, when I extended it works just fine, thanks!