[ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More

[kerney666]

Guys what is the command to reorder GPUs by BUS ID? Kerney, todxx, This command is not in the readme or first page of topic, only text "Added option to reorder GPU by BUS ID", can you add it to have it in readme?

Guess we're *nix guys at heart or something, we expect everyone to run the miner with "--help" as argument and read there . That's really the one place we keep up-to-date with all arguments and help descriptions. Should add that to the readme and first page at least!

To answer your question though, it's "--bus_reorder".

[1715037870]

1715037870

[1715037870]

1715037870

[vmozara]

Thanks! Sorry, sometimes I am total idiot when it comes to PCs. Most of these commands i just copy from the forum guys who already got it working and then i try random things until it works the way i want to. But most of the time, I am really bad with software (but at least my rigs look super nice, haha!) Thanks for being nice!  

[vmozara]

Vega 64 16+14
1630 core 1190 hbm
2470 H/s  

Somehow, my watercooled vegas have better hashrate than normal vega 64 even when ODN settings are the same. I have only 2 watercooled vegas so the sample size is not so big, yet if I use for example 1450/1100mhz, normal vega 64 will be around 2150 and liquid vega at around 2250. I will try in following days to flash liquid vega bios to normal vega and see what happens

[joseph32]

Vega 64 16+14
1630 core 1190 hbm
2470 H/s  

Somehow, my watercooled vegas have better hashrate than normal vega 64 even when ODN settings are the same. I have only 2 watercooled vegas so the sample size is not so big, yet if I use for example 1450/1100mhz, normal vega 64 will be around 2150 and liquid vega at around 2250. I will try in following days to flash liquid vega bios to normal vega and see what happens

I also tested the LC vegas. Go with max 1150. Anything above will result in too many HW and rejected, which will drop your effective hashrate below the 1150 results.

[shgth]

New AMD gpu drivers are out and with so many new things I just gotta use them. So far mining speed on teamred seems to be a bit better and now one can undervolt well enough without registery powertables.. Not sure if the combination of new drivers + teamred or just teamred but whole system seems to be laggy while mining. It wasn't before Probably need new CN-values.

Release notes https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-12-2
Download as usual.

Sapphire Pulse Vega 56 & Cryptonight V8 algo.

[BeeDeeEff]

New AMD gpu drivers are out and with so many new things I just gotta use them. So far mining speed on teamred seems to be a bit better and now one can undervolt well enough without registery powertables.. Not sure if the combination of new drivers + teamred or just teamred but whole system seems to be laggy while mining. It wasn't before Probably need new CN-values.

Release notes https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-12-2
Download as usual.

Sapphire Pulse Vega 56 & Cryptonight V8 algo.

Did you try the different memory timing options?  Did they increase your hashrate or lower your stable overclock?

[shgth]

Did you try the different memory timing options?  Did they increase your hashrate or lower your stable overclock?

Well I tried automatic functions like undervolt, oc gpu and oc memory but the increased hashrate is from the same manual settings I used before(just used wattman this time instead of overdriventool). Now I just don't need powertable regfile for it. You need to pick one from the automatic options and I just rather do undervolt + oc memory at once so manual works for me better. Also automatic oc never did over 800mhz on memory(it's max value on default settings but with manual one can adjust like before) and I rather have 900mhz at least. There are two memory timing levels but too busy to test them out now(wouldn't know if it could crash and no time for that).

EDIT: Both memory timing levels give a bit better hashrate for me than default value "Automatic". First tier a bit better, very very little. Tried every other gpu miner I know there is and no OS lag(whole windows and videos) with any of them. I hope this is something that can be fixed within teamred so I can go back to it.

[ku4eto]

Speed is the same with Automatic (my memory straps). Power consumption seems 5-10W lower. Running on Polaris cards only. Fan curve seems to disable the Zero RPM fans...

[alucard20724]

New AMD gpu drivers are out and with so many new things I just gotta use them. So far mining speed on teamred seems to be a bit better and now one can undervolt well enough without registery powertables.. Not sure if the combination of new drivers + teamred or just teamred but whole system seems to be laggy while mining. It wasn't before Probably need new CN-values.

Release notes https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-12-2
Download as usual.

Sapphire Pulse Vega 56 & Cryptonight V8 algo.

i can verify the lagginess with teamread and 18.12.2. drivers with my vega56/64.  hashrate is higher without having to mess with powertables, but there's a substantial lag on the system now.

[todxx]

New AMD gpu drivers are out and with so many new things I just gotta use them. So far mining speed on teamred seems to be a bit better and now one can undervolt well enough without registery powertables.. Not sure if the combination of new drivers + teamred or just teamred but whole system seems to be laggy while mining. It wasn't before Probably need new CN-values.

Release notes https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-12-2
Download as usual.

Sapphire Pulse Vega 56 & Cryptonight V8 algo.

i can verify the lagginess with teamread and 18.12.2. drivers with my vega56/64.  hashrate is higher without having to mess with powertables, but there's a substantial lag on the system now.

Can you elaborate a bit more on your setup?  Are you running the cards with risers?

I just ran my Vega 64 LC on 18.12.2 and did not have any problems.

[alucard20724]

New AMD gpu drivers are out and with so many new things I just gotta use them. So far mining speed on teamred seems to be a bit better and now one can undervolt well enough without registery powertables.. Not sure if the combination of new drivers + teamred or just teamred but whole system seems to be laggy while mining. It wasn't before Probably need new CN-values.

Release notes https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-12-2
Download as usual.

Sapphire Pulse Vega 56 & Cryptonight V8 algo.

i can verify the lagginess with teamread and 18.12.2. drivers with my vega56/64.  hashrate is higher without having to mess with powertables, but there's a substantial lag on the system now.

Can you elaborate a bit more on your setup?  Are you running the cards with risers?

I just ran my Vega 64 LC on 18.12.2 and did not have any problems.

i7-5930k, one vega56 pciex16 slot with monitor connected, two vega56 on risers, one vega64 on riser... all set to 14+14, win10x64

[todxx]

New AMD gpu drivers are out and with so many new things I just gotta use them. So far mining speed on teamred seems to be a bit better and now one can undervolt well enough without registery powertables.. Not sure if the combination of new drivers + teamred or just teamred but whole system seems to be laggy while mining. It wasn't before Probably need new CN-values.

Release notes https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-12-2
Download as usual.

Sapphire Pulse Vega 56 & Cryptonight V8 algo.

i can verify the lagginess with teamread and 18.12.2. drivers with my vega56/64.  hashrate is higher without having to mess with powertables, but there's a substantial lag on the system now.

Can you elaborate a bit more on your setup?  Are you running the cards with risers?

I just ran my Vega 64 LC on 18.12.2 and did not have any problems.

i7-5930k, one vega56 pciex16 slot with monitor connected, two vega56 on risers, one vega64 on riser... all set to 14+14, win10x64

My system is similar except for the risers, so that's something to look into.

If you have a chance, could you try to run the miner on each card individually to see if the lag issue is caused by a particular card or set of cards?

[shgth]

For me it's just a single Vega 56 alone right on pcie 16x. Dual "monitor" setup(144hz freesync + 60hz tv).

Asus Prime B350 Plus / Ryzen 1600 / Win10 Pro 1809(Os Build 17763.194, should be latest) / 2x4GB 3000mhz and 16000MB virtual memory on Samsung EVO850 SSD / CN 16+14(tried few others but no change other than hash speed decreased)

Just ran teamred for the night as I wasn't using the PC; otherwise it works wonderfully except the system lag.

[heavyarms1912]

For me it's just a single Vega 56 alone right on pcie 16x. Dual "monitor" setup(144hz freesync + 60hz tv).

Asus Prime B350 Plus / Ryzen 1600 / Win10 Pro 1809(Os Build 17763.194, should be latest) / 2x4GB 3000mhz and 16000MB virtual memory on Samsung EVO850 SSD / CN 16+14(tried few others but no change other than hash speed decreased)

Just ran teamred for the night as I wasn't using the PC; otherwise it works wonderfully except the system lag.

did you try reducing intensity?

[kerney666]

For me it's just a single Vega 56 alone right on pcie 16x. Dual "monitor" setup(144hz freesync + 60hz tv).

Asus Prime B350 Plus / Ryzen 1600 / Win10 Pro 1809(Os Build 17763.194, should be latest) / 2x4GB 3000mhz and 16000MB virtual memory on Samsung EVO850 SSD / CN 16+14(tried few others but no change other than hash speed decreased)

Just ran teamred for the night as I wasn't using the PC; otherwise it works wonderfully except the system lag.

So, I upgraded my gpu dev workstation to 18.12.2 today, hoping it'd reproduce the system lag issue. Unfortunately, everything is running just fine:

Code:

[2018-12-15 21:02:53] Stats Uptime: 0 days, 07:14:02
[2018-12-15 21:02:53] GPU 0 [60C, fan 60%] cnv8: 1.011kh/s, avg 1.010kh/s, pool 1.007kh/s a:212 r:0 hw:0
[2018-12-15 21:02:53] GPU 1 [64C, fan 17%] cnv8: 1.039kh/s, avg 1.040kh/s, pool 1.086kh/s a:229 r:0 hw:0
[2018-12-15 21:02:53] GPU 2 [54C, fan 29%] cnv8: 2.081kh/s, avg 2.081kh/s, pool 2.109kh/s a:448 r:0 hw:0
[2018-12-15 21:02:53] Total                cnv8: 4.131kh/s, avg 4.132kh/s, pool 4.203kh/s a:889 r:0 hw:0

The box is a pretty standard Dell Win 10 Pro Ryzen 7 1700X, 16GB ram, 48GB overkill swap. It runs a Rx580 at PCIe 3.0 x8, Vega 64 LC at PCIe 3.0 x16 and a Rx570 on a riser at PCIe 2.0 x1.

So, when running the miner using standard configs (8+8,8+8,16+14) and getting the results above after 7h, I experience zero lag or sluggish feeling. No difference logged in remote vs physically. However, there's no chance in hell I can run my Vega 64 at 16+14 when it's driving monitor(s), hashrate drops significantly.

I'd love to be able to reproduce and nail this issue, I have a few ideas about things that could make TRM stick out compared to other miners. Right now we don't have a workstation or rig exhibiting the problems described, but we'll continue the search.

Just curious if any of you guys having this problem could try a compute algo as well and check if you still have the issue? For example, you can just run the provided start_phi2.bat in the 0.3.8 release.

[shgth]

did you try reducing intensity?

I haven't figured out how to change it. I've tried + and - keys from both places of the keyboard with no change.

Not sure if this affects intensity but

CN 16+14(tried few others but no change other than hash speed decreased)

[msTrix]

For who is interested:

Running on a RX570 4GB ITX, CC 1075 MC 775 MC 1910 MV 787, getting 870 h/s reported, maybe 860 h/s at the pool, using 86.5 watt at the wall (minus mobo draw without card installed) (CNv8). (max hash is about 920 h/s or so for this card, but it uses about 112 watt (just without mem errors etc)

about 3 mem errors / hour (2.5 hour test run), non hw in the miner. Voltages are ridiculously low, especially for TRM. Determined these odd clocks and voltages using SRB to give the most hash/watt, (and no mem errors), and then tried them as well for TRM. SRB 1.7.0 gets 9.4 h/w, TRM 0.3.8 almost 10.0 h/w. Was surprised TRM did not crash on these low voltages, as at higher core clocks it needs the power.

Cost wise it would save me 10 dollar/year, as my power is about 0.20 dollar / kWh.

So TRM can be a decent competitor, when some more features will be introduced  , and the dev fee goes down just a tickle more 

 

[heavyarms1912]

Cost wise it would save me 10 dollar/year, as my power is about 0.20 dollar / kWh.

if your power costs $0.2 then you're already losing money mining coins that buying them.

[msTrix]

Cost wise it would save me 10 dollar/year, as my power is about 0.20 dollar / kWh.

if your power costs $0.2 then you're already losing money mining coins that buying them.

You are totally right! although it saves on heating my home. Guess atm you only earn a bit when you got 'free' power from somewhere.

[GordoLui]

Just a small update on how my small farm is doing, I been running this miner for a week now pretty stable with almost no issues. Not sure how I can check for the percentage of rejected and accepted shares, but all the numbers seem to have evened out. All my miners have been running almost all the same across the board. Maybe a few points of difference between them but they can all hit at least 1900 sol/s for my vega 56's.

A few days ago I read a reddit post of a dude saying he was able to hit 2000 sol/s on his vega 56 with an extremely reduced power draw. He was using the recently released adrenalin drivers but didn't give out much more information. So far I have downloaded the second to latest drivers and have been able to closely replicate the results i had with using the soft powerplay table mod and using overdriveN tool. It does feel like there is room for fine tuning but i wouldn't know where to start. Ideally I would like to hit the 2000 sol/s using 115w on gpu-z. Maybe not that low but having a system total power draw of 500w or under for 3 vega 56 would be very nice.