[ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 4.

GKumaran

member

Activity: 204

Merit: 10

Quote from: ayiphelmy on October 03, 2019, 09:06:59 PM

Quote from: kerney666 on October 03, 2019, 05:44:32 PM

Quote from: ayiphelmy on October 02, 2019, 05:59:31 PM

miner cant run on 2miner pool algo mtp and x16rv2 please fix this

Hi! Can you describe your issues please? I don't have any problems with 2miners myself when testing.

miner stop when initialize gpu... i use this miner with awesome miner...

I myself use TeamRedMiner with awesome miner on 2miner for MTP.
Right click the miner in awesome miner and run diagnostics and check/post the error.

ayiphelmy

copper member

Activity: 416

Merit: 105

Quote from: kerney666 on October 03, 2019, 05:44:32 PM

Quote from: ayiphelmy on October 02, 2019, 05:59:31 PM

miner cant run on 2miner pool algo mtp and x16rv2 please fix this

Hi! Can you describe your issues please? I don't have any problems with 2miners myself when testing.

miner stop when initialize gpu... i use this miner with awesome miner...

kerney666

member

Activity: 658

Merit: 86

Quote from: sockpuppet1911 on October 03, 2019, 01:47:51 AM

Thank you for adding $CCX Wink

Outperforming everything else I've tried so far with my vegas.

Awesome, thanks for the feedback!

kerney666

member

Activity: 658

Merit: 86

Quote from: ayiphelmy on October 02, 2019, 05:59:31 PM

miner cant run on 2miner pool algo mtp and x16rv2 please fix this

Hi! Can you describe your issues please? I don't have any problems with 2miners myself when testing.

sockpuppet1911

sr. member

Activity: 994

Merit: 278

Thank you for adding $CCX Wink

Outperforming everything else I've tried so far with my vegas.

GKumaran

member

Activity: 204

Merit: 10

Quote from: ayiphelmy on October 02, 2019, 05:59:31 PM

miner cant run on 2miner pool algo mtp and x16rv2 please fix this

Running for weeks on 2miner for MTP and can confirm it works fine. What errors are you getting?

Elder III

sr. member

Activity: 1246

Merit: 274

I get about 32.5 on a Radeon VII, uses ~220 watts average power with a modest undervolt. It was quite nice on RVN for the first 24 hours or so.

ayiphelmy

copper member

Activity: 416

Merit: 105

miner cant run on 2miner pool algo mtp and x16rv2 please fix this

GKumaran

member

Activity: 204

Merit: 10

Quote from: joseph32 on October 01, 2019, 12:14:59 PM

Since the hashrate of X16rv2 is a range, has anybody some numbers for Vega64? Just to compare a bit, thanks!

https://ibb.co/vstL6hh

Results on Vega 64:
Cards : 6x Vega 64, Air Cooled, Samsung Memory, Reference Design
Core : 1135mhz(p3)
Mem : 500mhz(p1)
Volt : 825mV
SOC : 599mhz
Timing mod : None, x16rv2 needs no memory tuning

Hashrate : 24.2 mh/s (Average After 43 minutes of mining)
Power : 195-200 watts

kristikun

newbie

Activity: 62

Merit: 0

Quote from: kerney666 on October 01, 2019, 12:35:58 PM

Quote from: joseph32 on October 01, 2019, 12:14:59 PM

Since the hashrate of X16rv2 is a range, has anybody some numbers for Vega64? Just to compare a bit, thanks!

You typically use a benchmark order 0123456789abcdef where all hashes are represented once to produce quoted hashrate(s), since this order will be close to your long term average.

A Vega 64 can do 28 MH/s or more if you don't care about power. Running with efficiency in mind, you should clock down core to 1130-1175 MHz and mem to 500 MHz, and also make sure you get a soc clk drop. When you see your soc clk (in HWiNFO64) is down to 600 or 800 MHz (and def not at 1107 MHz), you will be able to pull power all the way down to 800mV. A properly tweaked Vega 64 can do 150-153 kh/s/w, but not all people have been able to reproduce this setup.

Im using veg56 flashed to 64 , with those setting i get insta crash any stable safe settings i could use for x16rv2 ? with memory timings or without ?
With my CN settings i get 22-28 mhs but cards die soon

joseph32

member

Activity: 418

Merit: 21

Quote from: kerney666 on October 01, 2019, 12:35:58 PM

Quote from: joseph32 on October 01, 2019, 12:14:59 PM

Since the hashrate of X16rv2 is a range, has anybody some numbers for Vega64? Just to compare a bit, thanks!

You typically use a benchmark order 0123456789abcdef where all hashes are represented once to produce quoted hashrate(s), since this order will be close to your long term average.

A Vega 64 can do 28 MH/s or more if you don't care about power. Running with efficiency in mind, you should clock down core to 1130-1175 MHz and mem to 500 MHz, and also make sure you get a soc clk drop. When you see your soc clk (in HWiNFO64) is down to 600 or 800 MHz (and def not at 1107 MHz), you will be able to pull power all the way down to 800mV. A properly tweaked Vega 64 can do 150-153 kh/s/w, but not all people have been able to reproduce this setup.

Awesome Kerney, thanks! Will test this later with more time.

kerney666

member

Activity: 658

Merit: 86

Quote from: joseph32 on October 01, 2019, 12:14:59 PM

Since the hashrate of X16rv2 is a range, has anybody some numbers for Vega64? Just to compare a bit, thanks!

You typically use a benchmark order 0123456789abcdef where all hashes are represented once to produce quoted hashrate(s), since this order will be close to your long term average.

A Vega 64 can do 28 MH/s or more if you don't care about power. Running with efficiency in mind, you should clock down core to 1130-1175 MHz and mem to 500 MHz, and also make sure you get a soc clk drop. When you see your soc clk (in HWiNFO64) is down to 600 or 800 MHz (and def not at 1107 MHz), you will be able to pull power all the way down to 800mV. A properly tweaked Vega 64 can do 150-153 kh/s/w, but not all people have been able to reproduce this setup.

joseph32

member

Activity: 418

Merit: 21

Since the hashrate of X16rv2 is a range, has anybody some numbers for Vega64? Just to compare a bit, thanks!

Lucky - Luciano

hero member

Activity: 711

Merit: 500

Quote from: kerney666 on September 30, 2019, 04:51:42 PM

Quote from: Lucky - Luciano on September 30, 2019, 04:40:31 PM

What do these errors mean (I mine Veil and I do not have a problem on Suprnova pool but only on BSOD pool.):

Hi! Bsod is a bit more picky with what timestamp you can use since it also determines the hash order. You need to add "--no_ntime_roll" as a cmd line argument (or in your start.bat). From our help:

Code:

      --no_ntime_roll       Prevents the miner from rolling ntime in the block header, only using the value
                              provided by the pool. This needs to be enabled for some pools when mining x16rt.

It works great. Thank you very much .

kerney666

member

Activity: 658

Merit: 86

Quote from: Lucky - Luciano on September 30, 2019, 04:40:31 PM

What do these errors mean (I mine Veil and I do not have a problem on Suprnova pool but only on BSOD pool.):

Hi! Bsod is a bit more picky with what timestamp you can use since it also determines the hash order. You need to add "--no_ntime_roll" as a cmd line argument (or in your start.bat). From our help:

Code:

      --no_ntime_roll       Prevents the miner from rolling ntime in the block header, only using the value
                              provided by the pool. This needs to be enabled for some pools when mining x16rt.

Lucky - Luciano

hero member

Activity: 711

Merit: 500

What do these errors mean (I mine Veil and I do not have a problem on Suprnova pool but only on BSOD pool.):

Ursul0

sr. member

Activity: 857

Merit: 262

Quote from: Grizzly866 on September 29, 2019, 01:16:36 PM

I have a rig of 4 VEGA 56 sapphire on the Samsung dvuhkonturniy. the algo of monero and sumo crashes then one card then the other. the tortoise and console norms plow all 4.what could be the problem? core 1400 memory 930 voltage 900.

you can reduce the voltage Vegas run well below 850(as low as 800) at over 1300MHz core clocks. Also try reducing your memory frequency on the problematic cards. and watch for HBM temps

RebTech-Blockchain

newbie

Activity: 4

Merit: 0

On RX470 8G 0.5.9:
10-11MH/RX470
GPU: 1090
Mem: 2100
VDDC: -850

Is the X15rv2 algo an GPU intensive algo? even at 1200 GPU hash is about the same or lower.

Grizzly866

newbie

Activity: 9

Merit: 0

I have a rig of 4 VEGA 56 sapphire on the Samsung dvuhkonturniy. the algo of monero and sumo crashes then one card then the other. the tortoise and console norms plow all 4.what could be the problem? core 1400 memory 930 voltage 900.

kerney666

member

Activity: 658

Merit: 86

Quote from: uy3srm on September 28, 2019, 01:45:00 AM

Quote from: todxx on September 25, 2019, 05:46:15 PM

Team Red Miner v0.5.9 released

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

Changes in v0.5.9

Added x16rv2 for the upcoming Ravencoin fork.
Optimization work on x16r: +8-10% hashrate depending on clocks.
Optimization work on x16r: mem clock no longer as important.
Issue fix: kernels split into multiple binaries to fix linux amdgpu-pro driver issues.

We've added x16rv2 algo for the upcoming Ravencoin fork! (Also BitCash and a few others)
We've also put a ton of effort to squeeze out as much performance as we could for the x16* algos in this release, with an up to 10% speed-up.

before this version ,teamredminer did not recognize AMD RX 5700.
This version recognize AMD RX 5700 as 'gfx1010' and stop working , log statements are:
{
[2019-09-28 09:45:46] Initialize error, unknown device name: 'gfx1010'
[2019-09-28 09:45:46] Failed to initialize device idx 0 (-9)
[2019-09-28 09:45:46] Successful clean shutdown.
}
Please update teamredminer to utilize AMD RX 5700?

We are still waiting for 3rd party tools to add proper support for Navi. As soon as we can, we’ll start working on Navi ports of eg x16r and MTP.

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