[ANN] TeamRedMiner - Old Thread

[ku4eto]

I am observing something weird.

With v0.3.10, i was  getting on Vertcoin (Lyra2rev3), 190.8Mh/s for ~435-440W at wall.
With v0.4.0, i am getting 191.7Mh/s for 450-455W at wall.

The claimed performance increase is 2-3%, but for me, in reality, is ~1%, while getting 2-4% power consumption increase.
Windows 10, AMD 19.2.1, using Memory P0 state.

1x RX 570, 3x RX 580.

Hi! The changelog says +0.5%, which you’re spot on. Not sure where you saw 2-3%? This thread should also have been updated though, our bad.

For the power draw, that is strange. I can leak that the only thing that has changed is the last kernel, so small changes really. We do have some other changes host side, but it feels very odd that they would add 15-20W!?!

Will do some testing of my own shortly!

Okay tested again.

There is difference for sure, but not as big as i initially reported. 447W on 3.10, vs 451-452W on 4.1. Guess the initial big difference was because of the slightly different ambient temperatures...

Aight, so +0.47% perf increase for +1% power, hmm. Well, no disaster really, I haven't had to time to dig into it myself though. Like I sad, we've added a few small things host-side, and some smaller things gpu-side as well. Will try to run those checks myself shortly.

Well, i thought it was bigger. 1% for 1% shouldnt be something to bother with, if you ask me. It was mistake on my side with bad measurements.

[redzep]

Hi got an issue mining phil2 Gway Coin, it did work few months back ok for AGM, cards work ok with X22i & X16r with no reboot after trying teamredminer
nothing has been updated in months on Rig and works fine with other miners

command line below
teamredminer.exe -a phi2 -o stratum+tcp://uk.thepool.life:5124 -u Wallet address -p c=GWAY -d 3,4

miner working fine on my PC to same pool

  Team Red Miner version 0.3.10
[2019-03-13 12:55:19] Auto-detected AMD OpenCL platform 0
[2019-03-13 12:55:22] Initializing GPU 0.
[2019-03-13 12:55:22] Watchdog thread starting.
[2019-03-13 12:55:22] Pool uk.thepool.life connecting to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully connected to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully subscribed. (8 ms)
[2019-03-13 12:55:23] Pool uk.thepool.life authorization succeeded.
[2019-03-13 12:55:23] Dev pool connected and ready.
[2019-03-13 12:55:23] Pool uk.thepool.life set difficulty to 1.000000
[2019-03-13 12:55:23] Pool uk.thepool.life received new job. (job_id: 1b0e)
[2019-03-13 12:55:23] Pool uk.thepool.life extranonce subscribe succeeded. (944 ms)
[2019-03-13 12:55:52] Stats Uptime: 0 days, 00:00:31
[2019-03-13 12:55:52] GPU 0 [45C, fan 59%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] GPU 1 [48C, fan 25%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] Total                phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:56:06] Pool uk.thepool.life received new job. (job_id: 1b0f)
[2019-03-13 12:56:22] Stats Uptime: 0 days, 00:01:01
[2019-03-13 12:57:02] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:57:12] Pool uk.thepool.life received new job. (job_id: 1b10)
[2019-03-13 12:58:37] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:37] Pool uk.thepool.life received new job. (job_id: 1b11)
[2019-03-13 12:58:37] GPU 0 [38C, fan 25%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] GPU 1 [48C, fan  0%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] Total                phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:47] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:47] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.


Thanks

fixed it saw earlier post about CPU mining which i stopped and working fine now

[todxx]

Hi got an issue mining phil2 Gway Coin, it did work few months back ok for AGM, cards work ok with X22i & X16r with no reboot after trying teamredminer
nothing has been updated in months on Rig and works fine with other miners

command line below
teamredminer.exe -a phi2 -o stratum+tcp://uk.thepool.life:5124 -u Wallet address -p c=GWAY -d 3,4

miner working fine on my PC to same pool

  Team Red Miner version 0.3.10
[2019-03-13 12:55:19] Auto-detected AMD OpenCL platform 0
[2019-03-13 12:55:22] Initializing GPU 0.
[2019-03-13 12:55:22] Watchdog thread starting.
[2019-03-13 12:55:22] Pool uk.thepool.life connecting to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully connected to address 95.179.206.161.
[2019-03-13 12:55:22] Pool uk.thepool.life successfully subscribed. (8 ms)
[2019-03-13 12:55:23] Pool uk.thepool.life authorization succeeded.
[2019-03-13 12:55:23] Dev pool connected and ready.
[2019-03-13 12:55:23] Pool uk.thepool.life set difficulty to 1.000000
[2019-03-13 12:55:23] Pool uk.thepool.life received new job. (job_id: 1b0e)
[2019-03-13 12:55:23] Pool uk.thepool.life extranonce subscribe succeeded. (944 ms)
[2019-03-13 12:55:52] Stats Uptime: 0 days, 00:00:31
[2019-03-13 12:55:52] GPU 0 [45C, fan 59%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] GPU 1 [48C, fan 25%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:55:52] Total                phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:56:06] Pool uk.thepool.life received new job. (job_id: 1b0f)
[2019-03-13 12:56:22] Stats Uptime: 0 days, 00:01:01
[2019-03-13 12:57:02] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:57:12] Pool uk.thepool.life received new job. (job_id: 1b10)
[2019-03-13 12:58:37] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:37] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:37] Pool uk.thepool.life received new job. (job_id: 1b11)
[2019-03-13 12:58:37] GPU 0 [38C, fan 25%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] GPU 1 [48C, fan  0%] phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:37] Total                phi2:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-13 12:58:47] GPU 0: detected DEAD (05:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-13 12:58:47] GPU 1: detected DEAD (08:00.0), no restart script configured, will continue mining.
[2019-03-13 12:58:47] Please use command line argument --watchdog_script to handle dead GPUs.


Thanks

fixed it saw earlier post about CPU mining which i stopped and working fine now

Hi redzep,

It seems that the GPUs are crashing, probably due to the OC/UV profile you are running.
Even though your current settings might be stable on other miners/algos, different miners and algos will behave differently and have different OC/UV limits.
In this case, phi2 is a rather core heavy algo, and will probably require dropping your clocks a bit.
A good sanity check is to see if it works at stock clocks/voltages, and then go from there.

[clousian]

@todxx

You guys planning on supporting cryptonight_conceal at some point?

Cheers

[kristikun]

Hello i would like to give my thanks to whole team red for their hard work , your miner is without a doubt fastest  my uderclocked / biosmoded vegas hash better than when i bought them a year a back   each vega 2kh cryptonightr 175w at wall , lyra2rev3 84-88mh  , my WC vega 2600h cryptonightr, 112 mh lyra2rev3 im really happy to see those same hashrates reported by pools also
I would like to ask for  MTp / cuckoo cycle   algo support since there isnt any properly optimazed amd  miners out there for those new algos which are currently  most profitable , keep up good work

Hey, thanks for the kind words, much appreciated! We'll see what we do after this CN push. We will add a few CN variants, then move on to something else. I'm so surprised there isn't a good Vega MTP miner out by now. We know how to get them to 3-3.5 MH/s on MTP, but the power draw will be higher than Nvidia (that goes for any plain AMD MTP implementation though). C29/C31 might also be something to look at.

I think we already have miners that do 3.5 MH on MTP and on Vega.

Oh they got it working now? Finally, then people might asking for it . I don't see any mentions of it in the mining channel on their discord though. Last I checked they had it working for Polaris but not for Vegas, the Vega perf was much too low.

Nevermind.

EDIT:  I am mixing up MTP with cuckoo here.

there  really isnt any working vega MTP miner outhere  and not even proper cuckoo /too i  tried 2x and  not even third of hashrate that gtx1080ti does

[Mattycoz]

just wondering is there a full list of commands to add to the batfile strings any where as i cannot find it anywhere.

[kerney666]

just wondering is there a full list of commands to add to the batfile strings any where as i cannot find it anywhere.

Hi! The one place that will always always be kept up-to-date and guaranteed to match your miner version is the built-in help text output. You get it by adding —help as a command line argument. If you run it in a bat file and the window closes, add a line with “pause” at the end of the bat file.

[qwep1]

planned to add MPT 

[scryptr]

just wondering is there a full list of commands to add to the batfile strings any where as i cannot find it anywhere.

Hi! The one place that will always always be kept up-to-date and guaranteed to match your miner version is the built-in help text output. You get it by adding —help as a command line argument. If you run it in a bat file and the window closes, add a line with “pause” at the end of the bat file.

CREATE A HELP.TXT FILE--

With most miners, and teamredminer as an example, a "help.txt" file can be generated as follows:

      1) Open a console window (ctrl+alt+t in Linux; in Windows, Windows key+r then type "cmd" and press enter).
      2) Navigate to the miner directory, then enter "teamredminer --help > trm-help.txt" on the command line.

This will pipe the "help" output into a text file.  You should then find "trm-help.txt" in the miner directory.  It can be read with notepad, nano, or any text editor.

If the miner directory is protected, which may be the case in Linux, prefix the pipe command with "sudo".       --scryptr

[mindstorms54]

Would you please add the stale rate count?
I lived in a country surrounded by sea in all directions
It's really hard for me too pick a decent server without the stale rate info
Really needs it
thanks

[CryptoKnight25]

Hey,

Would it be possible to implement some kind of hashmonitor that can trigger a script?
This would be useful for my vega rig. I'm sure you are familiar with the HBCC turning off dropping the hashrate by 600h/s per card.

Would be nice if there was some setting that would trigger a script if the hashrate declined by x% from the average (or a given number).

I'm not a coder so I'm not sure how hard this is to implement, but at the moment I'm using your miner because it works very good. However, because there is no hashrate monitor available for it like there is with XMR-Stak (JJ Hashmonitor / JJ Precious Guardian) I need to check the miner status 2-3 times a day which can get annoying . Adding this feature would make it dope!

EDIT: As mentioned before I'm not a coder so I dont know if this is relevant at all but maybe this could be a way to do it.

--MinimumHash=X:SCRIPT

Here you can enter X, the minimum amount of H/s your system produces when its functioning normally. When it falls below this number, a script (can be watchdog.bat) will be triggered. This function will only set in after 5 minutes of mining so average hashrate has been stabilized.

[joseph32]

Hey,

Would it be possible to implement some kind of hashmonitor that can trigger a script?
This would be useful for my vega rig. I'm sure you are familiar with the HBCC turning off dropping the hashrate by 600h/s per card.

Would be nice if there was some setting that would trigger a script if the hashrate declined by x% from the average (or a given number).

I'm not a coder so I'm not sure how hard this is to implement, but at the moment I'm using your miner because it works very good. However, because there is no hashrate monitor available for it like there is with XMR-Stak (JJ Hashmonitor / JJ Precious Guardian) I need to check the miner status 2-3 times a day which can get annoying . Adding this feature would make it dope!

EDIT: As mentioned before I'm not a coder so I dont know if this is relevant at all but maybe this could be a way to do it.

--MinimumHash=X:SCRIPT

Here you can enter X, the minimum amount of H/s your system produces when its functioning normally. When it falls below this number, a script (can be watchdog.bat) will be triggered. This function will only set in after 5 minutes of mining so average hashrate has been stabilized.

Try AwesomeMiner, it can do any monitoring stuff you need, simply by creating rules: https://bitcointalk.org/index.php?topic=676942.0

[cecilia1]

Hello,

Can anybody share me script of watchdog.bat to restart the miner when a dead GPU is detected?

Thanks a lot!

[adaseb]

Alright here is an update. I finally managed to get 1000 H/s out of my RX 470 4GB Hynix GPUs with Windows 7 using the Blockchain drivers and memory strapped with "Pimp my straps".

However I am getting a weird issue. Sometimes all my GPUs hash at 1000 H/s however if I close the program and restart right away, some hash slower like 850 H/s. If I restart windows, it sometimes goes back to 1000 H/s however sometimes it does not. I basically need to power cycle it a few times to get all the GPUs to hash at their max speed. Anyone ever get this issue?

[tipo70]

Alright here is an update. I finally managed to get 1000 H/s out of my RX 470 4GB Hynix GPUs with Windows 7 using the Blockchain drivers and memory strapped with "Pimp my straps".

However I am getting a weird issue. Sometimes all my GPUs hash at 1000 H/s however if I close the program and restart right away, some hash slower like 850 H/s. If I restart windows, it sometimes goes back to 1000 H/s however sometimes it does not. I basically need to power cycle it a few times to get all the GPUs to hash at their max speed. Anyone ever get this issue?

I confirm. I sometimes have this problem.

[CryptoKnight25]

Hello,

Can anybody share me script of watchdog.bat to restart the miner when a dead GPU is detected?

Thanks a lot!

My watchdog.bat simply a restart command. So:

shutdown -r -t 1

Then when my rig reboots, it runs all the scripts to apply right settings and start the miner.

[adaseb]

Alright here is an update. I finally managed to get 1000 H/s out of my RX 470 4GB Hynix GPUs with Windows 7 using the Blockchain drivers and memory strapped with "Pimp my straps".

However I am getting a weird issue. Sometimes all my GPUs hash at 1000 H/s however if I close the program and restart right away, some hash slower like 850 H/s. If I restart windows, it sometimes goes back to 1000 H/s however sometimes it does not. I basically need to power cycle it a few times to get all the GPUs to hash at their max speed. Anyone ever get this issue?

I confirm. I sometimes have this problem.

What version of windows are you using and what AMD drivers? Also what GPUs does this happen on?

I am trying to find the cause of these issues because it doesn't seem to happen with ETH mining... only XMR.

Also I just noticed now that I posted in the wrong thread... I am referring to the CN R mining algo and not Lyra but assuming people here also have the same issue.

[iRonNuke]

Any plans to support Vega VII? I get this error message when trying to use Lyra2Rev3 algo:

[2019-03-23 14:54:35] Initialize error, unknown device name: 'gfx907'
[2019-03-23 14:54:35] Failed to initialize device idx 4 (-8)

[todxx]

Any plans to support Vega VII? I get this error message when trying to use Lyra2Rev3 algo:

[2019-03-23 14:54:35] Initialize error, unknown device name: 'gfx907'
[2019-03-23 14:54:35] Failed to initialize device idx 4 (-8)

Seems we might be missing the device name for VII when HBCC is enabled.  We'll add it in the next release.
For the time being, if you disable HBCC on your VII it should work.

[iRonNuke]

Any plans to support Vega VII? I get this error message when trying to use Lyra2Rev3 algo:

[2019-03-23 14:54:35] Initialize error, unknown device name: 'gfx907'
[2019-03-23 14:54:35] Failed to initialize device idx 4 (-8)

Seems we might be missing the device name for VII when HBCC is enabled.  We'll add it in the next release.
For the time being, if you disable HBCC on your VII it should work.

Thanks for the help about that.