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

It is certainly ram dependent in that it needs ~4.5GB just to run. Given the mem access patterns, you can clock down memory a ton on Vegas (but not on Polaris cards), just like you've done. I actually think your core clk could be unnecessarily high, but the only way to know for sure is to continue tweaking. Since you're running on 300 memclk, I'm guessing you're already down in lower mem P-states? That is the preferred way since it will drop the soc clk, allowing for a much lower voltage for core + mem (as configured in e.g. OverdriveNTool). I've ran my tests down to 500 MHz memclk, but that's on Vega 64s.

You might already have read it, but I did write a little about the tuning process in the MTP_MINING.txt in the release package.

vega 64 3,5 from wall 280w
vega 56 3,3 from wall 270w
settings like cryptonight r

Is this algo ram dependent? now i am having like 2.6-2.7 on vega 56 with 1350 on core and 300 mem, it is drawing like 200 per card from wall (my guess, i dont have data on this from remote computer).

4gb dont work little video memory

Thank you for testing! However, I must say your results are low compared to expected values, you should be able to hit ~1.6 MH/s (570) and ~1.8 MH/s (580) without too much tuning effort. I'll do a proper benchmark post soon, listing hashrates and settings for range of gpus.

mtp results seems quite impressive - will test today on my rigs!

Thank you for adding MTP Argo.
It's a shame that you can not do it with a 4GB GPU, but it may be difficult.

win10
RX570 8G 1100/1800 about 1Mhz
RX580 8G 1340/2000 about 1.6Mhz

It was described in the wrong thread. I am sorry.

First Impression Results:
Vega 64 : 225 watt = 2.8mh/s
Vega 56, samsung flashed to 64 : 190 watt = 2.62 mh/s
Vega 56, hynix : 180 watt = 2.45 mh/s

Team Red Forever :sunglasses:

Team Red Miner v0.5.3 released

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

Changes in v0.5.3

• Added MTP algo for Zcoin/XZC (please read MTP_MINING.txt before mining).
• Further small stabilization fixes for CN variants, primarily 4MB algos.

Now supporting the MTP algorithm for Zcoin

!!!!! MTP IS EXTREMELY POWER HUNGRY AND HOT !!!!
Please make sure to lower your clocks and have good cooling for your GPUs when testing MTP.
MTP can consume double the power of other algos for un-tuned cards.

Hi Ncarter

thanks for the response i ran the diagnostics and got the following?

Initialize diagnostics (4)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 6.6
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 18.5.2
AMD OpenCL Platform ID: 0
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: TeamRedMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True)
====================================================================================================
C:\Users\LilRedRig\AppData\Roaming\AwesomeMinerService\teamredminer-v0.5.2-win_3\teamredminer-v0.5.2-win\teamredminer.exe  -d 0,1,2 -a phi2 --bus_reorder -d 2,3,4 -o stratum+tcp://lux.pickaxe.pro:8332 -u LNRWWRPD6gGnpLUicpRcFVKUituE5z862w -p C=LUX,d=4 --api_listen=0.0.0.0:4030
Configured command line:
-d 0,1,2
====================================================================================================
>           Team Red Miner version 0.5.2
> [2019-07-01 10:04:59] Only one -d argument allowed.
Failed to start miner process: Process has exited, so the requested information is not available.
Failed to start miner in Diagnostics mode
Diagnostics completed

It appears tho awesome miner or the miner it self it putting in --bus_reorder, how do i stop this so it only uses my command -d 0,1,2

Hello,

I'm running TeamRedMiner 0.5.2 with AMD RX474 GPU on Nicehash x16r but I get about 30% shares rejected with "Share above target" error. Any ideas?

setting the virtual ram t/80gb fixed the failure to connect to device idx 5 (-31). now if i could figure out why this other vega 56 wont work.

Yes the gpu runs in isolation and to be quite honest i never have set up a watchdog to monitor problem matic gpus in the the past when i have tried i have not had any success (im not in the computer buisness this is more like a hobby for me) it takes me time to figure the programing out but have done ok with everything cuase of the plethora of info you can find on the internet. this all started when i tried to bring one of my vega 56 gpus back in the rig when it booted up it would give me a black screen and reset the system none stop. once i removed said gpu and checked the registry the vega 56 was recognized fully but for some reason windows would not boot. after that incident is when i started have issues with the system.

for reference my system:
asrock h110 btc pro+ with p4400 16mb ram
1x asus strix vega 64
3x nitro+ vega 64
1x powercolor vega 56 use to be 2x
1x rx 570 8g msi armor
2x evga 1660ti- i know mixing cards can cause problems but they are out of the system right now and the drivers have been removed with the latest ddu. also the systen ran for two weeks problem free running two different mining programs.
3200 watts of gold rated power supplies evga g3 corsair hxi 2 750 watt server supplies w/break out boards
gpu 5 is currently running issolated at 2340 h/s tmr+amd mem tweak.

p.s. as im writing this i just realized after my clean install i never rest my virtual ram to 80gb let me check if that fixes it.

Hi! That error is a mem buffer allocation error, it fails to allocate the (large) buffer for all the 2MB CN pads for that gpu.

A few questions + things to try:

• Does it work for that gpu if you run that gpu in isolation, i.e. you add "-d 5" to the command line? If so, do you have enough swap space available?
• Can you list the output from "teamredminer.exe --list_devices"?
• Do you run monitors on the problematic gpu?

 

computer crashed after a couple of months of mining. Now when i try to start miner only on cnr algo it says failed to initiate device idx 5 (-31) i have tried going to a previous restore point, reseting my computer and reinstalling drivers w/ddu. all have the same end result. dont know whats up. any help would br much appriciated.

Try running the diagnostic command in the toolbar. It should spit out the cmd line along with the miner start up. From there, you can start seeing where things are failing.

Im running through Awesome miner, so unsure where to find that sorry. All i know is the software will no longer run if i use -d 0,1,2. But if i remove that it runs to the wrong cards e.g. 3,4,5

Hey guys im having a big problem with my xfx vega 64 / x7 rig.
When i start mining everything is fine but after a day or two days or more one of my gpus hashrate falling down and then makes the whole rig crash.
My settings are 1175/925 core 1050/905 memory driver 19.4.1 windows 10 (old TRM 0.4.5 is more stable for my rig)

Paging 80gb and i changed my clocks too much but nothing changed. My friend also has this problem.
Does someone know what should i do or how to troubleshoot this ?

Hmm that is strange, nothing has been (intentionally) changed. Can you post your anonymized full command line?

Hey guys, Ive noticed in the latest updates my command for gpu allocation isnt working anymore, i was using -d 1,2 etc...
any ideas what the new 1 is?