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

[kerney666]

I manage about 30 amd rigs in the birmingham area of the uk.

really like your miner - it does all you claim and is slightly better than the competition.
its especially good on radeon VII and rx5700 .

at present the rigs all have the following set in the config.txt file
core clock
mem clock
core volts
mem volts
fixed fan speed
max temp before gpu throttles (this is vital)

theres other stuff but those 6 things are the main ones.

if your miner could set those 6 things within its config - i would dump the competition and use your miner on all rigs.
yes i know about overdriventool and msi afterburner but in my experience on rigs with 470, 570,480,580,5500, 5700, radeon vii -
those tools are hit and miss and too much trubble .
we use windows 10 ghost spectre (no updates, bloat or telemetry) and mostly amd driver 20.9.1
the one rig that isnt 20.9.1 - has a vega frontier edition 16gb water cooled - i should do a video on
that rig - what a palaver to get that card mining. but we did it with driver 19.7.1 and the registry hack

ghost spectre rocks - you will be amazed. no updates . rock solid . tiny ram usage . tiny disk usage.
best wishes from manchester uk

Clocks/voltage support is being worked on, most probably windows only in the first release.

Fan support already exists, see --fan_control in the USAGE.txt docs (incl tracking core and/or mem temp, using a static speed, defined min/max range and more), but we've also fixed some Navi fan control issues for the next release.

For temps, we don't throttle per se to keep the gpu running close to the limit, it's assumed the user should make sure to keep temps within the expected range and the protection is rather against broken fans or similar incidents. We do a hard cutoff at 85C (default) and stop mining until the gpu reaches 65C again. See --temp_limit and --temp_resume for more info.

Last, I'm sure you're well aware that VIIs do excel under linux with our C-mode becoming available after a few kernel parameter tweaks, just mentioning it just in case. I'm guessing running is homogeneous environment is more important for you guys.

[kerney666]

Anybody knows why TR miner on Polaris cards (470/480/570/580/590) builds DAG so long?
TR miner build it in about 12-13 sec. on my 580 8Gb cards. 1st of all I'm thought that it's only 1st time after launching (cache, etc.). But every time when DAG changes it take so long as at launch.
But other miners (Claymore, lol, Phoenix) builds DAG about 7-8 seconds.

Well, we just got tired of reports of aggressive (and in some aspects suboptimal) Polaris straps that caused the DAG build read/write pattern to crash gpus, so we defaulted to a very slow and safe version. For continuous ethash mining it's 4-5 secs extra every 4.5 days, 0.0016% penalty, but naturally worse if you switch between epochs more often for some reason, or crash every 2-3h and restart the miner.

I honestly don't remember exactly what type of cap we ended up with, but try adding --eth_dag_slowdown=0 and check the DAG build time.

[UnclWish]

Anybody knows why TR miner on Polaris cards (470/480/570/580/590) builds DAG so long?
TR miner build it in about 12-13 sec. on my 580 8Gb cards. 1st of all I'm thought that it's only 1st time after launching (cache, etc.). But every time when DAG changes it take so long as at launch.
But other miners (Claymore, lol, Phoenix) builds DAG about 7-8 seconds.

Well, we just got tired of reports of aggressive (and in some aspects suboptimal) Polaris straps that caused the DAG build read/write pattern to crash gpus, so we defaulted to a very slow and safe version. For continuous ethash mining it's 4-5 secs extra every 4.5 days, 0.0016% penalty, but naturally worse if you switch between epochs more often for some reason, or crash every 2-3h and restart the miner.

I honestly don't remember exactly what type of cap we ended up with, but try adding --eth_dag_slowdown=0 and check the DAG build time.

Oh, sorry. I didn't read usage.txt. Thanks for an option - I will try different variants of it.

EDIT: With -eth_dag_slowdown=0 DAG creation time decreased to 8.8 sec. It's faster but still slower than other miners (7.8-8.0 sec.). I'm use nicehash - his pool often changes DAG's, so for me DAG rebuilding time is important...

[voodoop]

I installed the latest AMD drivers (21.6.1) and I get :
failed to initialize device idx 0 (-13) .

On previous drivers it worked correctly .

LE : one Vega 56 .

[dastardlyman12]

strange request

I have access to a vega frontier edition water cooled
it has 16gb of hbm2
the card looks great - but thats about it. LOL.

to get it to mine i have to use the amd driver 19.7.1 and do the "is gaming mode driver" registry hack.
then apply some trick timings using amdmemtweakxl ive got it to 45 megahash
with core at 1050 and mem at 1060

but B mode will not enable
the 45 megahash is using A mode or the competition's miner

you cannot use a modern driver with this card because it forces professional creator  mode and you lose ALL
control of clocks etc. it defaults to high core clock and low hbm clock exactly what you DONT want for mining

ive not tried linux but i dont think its any better

can i force B mode on amd driver 19.7.1 or is it a lost cause??
many thanks

[DrX]

Hi,

any other fixes for HW errors than
--eth_dag_alloc_patch

Using Asrock H81 Pro BTC / Bios 2.4. and HiveOS (AMD driver 20.20)

Did try also different PCI-e slots but after about 24h, one of the XFX RX570 starts pushing errors and not one valid shares after that?
Also have tried different voltages and clocks.
only fix seems to be restart miner? is auto-restart timer on miner?

 

[demian198]

i am having issues after updating amd gpu driver to 21.6.1 with navi14 card "failed to initialize device idx0 (-13)"

[DrX]

Hi,

any other fixes for HW errors than
--eth_dag_alloc_patch

Using Asrock H81 Pro BTC / Bios 2.4. and HiveOS (AMD driver 20.20)

Did try also different PCI-e slots but after about 24h, one of the XFX RX570 starts pushing errors and not one valid shares after that?
Also have tried different voltages and clocks.
only fix seems to be restart miner? is auto-restart timer on miner?

Reply to myself, fixed the problem by changing to lolminer...

[oblione]

To the Teamredminer development team:

Is it possible to put in the Power throttle limit control to slow down the mining itself in order to protect GPU does not over temp under GPU temp/ Junction temp/ Vram temp , pls consider

Such a feature isnt there at the moment, but check if these commands help in your case to protect GPUs

Code:

--temp_limit=TEMP     Sets the temperature at which the miner will stop GPUs that are too hot.
                        Default is 85C.
--temp_resume=TEMP    Sets the temperature below which the miner will resume GPUs that were previously
                        stopped due to temperature exceeding limit.  Default is 60C.

Are those temps the edge temps? or is there a way to turn a gpu off based on the TMEM temperate until it cools down?

[bghaemi]

Hello, since the v0.8.2 update I keep getting "GPU 2 : detected DEAD" every hour on my stable rig.
When I look at the log, the card is still at normal hashrate when detected DEAD
Tried to reduce overclock and increase voltage, still having this issue.

Can this be caused by the miner detecting the card DEAD when it's not? Thanks 

you can check the usb cables, riser and finally reinstall the driver

I got the same issue on GPU0, despite of changed all hardware (Rizer, Cable, Motherboard, Power Supply) also the AMD driver from 18.6.1 to 20.11.2 but still was getting Dead GPU message.
Finally downgraded to v0.8.2 and continue mining ETH without hassle.

[jiang80s]

Hi,
I have some issues when using for xhv coin under linux ( RaveOS) comparing with windows.
Under linux my baffin cards like RX 550 2Gb, RX 560 2Gb works only 300 h/s. But it will get 500 h/s more in windows, with same core, mem, and voltage.
Let me know the problem and how to solve it.
Thank you.

[Cryptoseekert]

Hello guys i hope you are all doing good

one question:

for ravencoin mining on windows 10, amd rx 570 4gb, what is the best way to control fans, voltages and clocks?

can i do it from the miner (like eth mining on phoenix or old claymore, where i can control temps, fans, etc via a command)

thanks

As far as I know, you cant control voltage and clocks,.. I do it throug OverdriveNTool program.

hi good sir, sorry to bother you.

ive been using overdriveNtool, but when i have a power cut problem or something, and the rig restarts, it will restart on the default clocks, not the overdrive ones.
how can i set them auto at win start?
thanks

[PeaMine]

Any ETA on support for 21.6.2 or 21.7.1 ? It supports Smart Memory and such.
XT series seems to work, but not Radeon VII, failed to initialize device.
Downgrading works though, but I like the new features for gaming.

[SamaelDNM]

Any ETA on support for 21.6.2 or 21.7.1 ? It supports Smart Memory and such.
XT series seems to work, but not Radeon VII, failed to initialize device.
Downgrading works though, but I like the new features for gaming.

i just saw there is an update already, it works for my rx 580 the drive version 21.7.1

https://github.com/todxx/teamredminer/releases/tag/v0.8.4

[MegaVlad]

Hi
Trying to mine on RaveOS (8708-1983), on TRM 0.8.4 and I get "Bus error".
Lol miner, Phoenix work fine on my rig. Can developers explain such behaviour of TRM 0.8.4?
Thank you in advance. 

[micax1]

Hi,
I have some issues when using for xhv coin under linux ( RaveOS) comparing with windows.
Under linux my baffin cards like RX 550 2Gb, RX 560 2Gb works only 300 h/s. But it will get 500 h/s more in windows, with same core, mem, and voltage.
Let me know the problem and how to solve it.
Thank you.

Do you use auto-tune?
Check your auto-tune settings that miner finds. are they same?
if they are not post it here - so we can compare.

[Stanlo]

I'm still getting low hashrate on my Vega 56 with max settings of core 930 mem clock 900  and 840mv any thing higher than this the GPU will crash in hiveOS, my hashrate is 44mH and here is the tweak settings I use

amdmemtweak --cl 18 --ras 23 --rcdrd 22 --rcdwr 11 --rc 34 --rp 13 --rrds 3 --rrdl 4 --rtp 6 --faw 12 --cwl 7 --wtrs 4 --wtrl 4 --wr 11 --rfc 164 --REF 15000

The memory is hynix memory

[GKumaran]

Hello guys i hope you are all doing good

one question:

for ravencoin mining on windows 10, amd rx 570 4gb, what is the best way to control fans, voltages and clocks?

can i do it from the miner (like eth mining on phoenix or old claymore, where i can control temps, fans, etc via a command)

thanks

As far as I know, you cant control voltage and clocks,.. I do it throug OverdriveNTool program.

hi good sir, sorry to bother you.

ive been using overdriveNtool, but when i have a power cut problem or something, and the rig restarts, it will restart on the default clocks, not the overdrive ones.
how can i set them auto at win start?
thanks

You can setup overdriventool via its cli commands, once you have a working bat file, set it to autorun on boot via Windows Task Scheduler

[GKumaran]

Hi
Trying to mine on RaveOS (8708-1983), on TRM 0.8.4 and I get "Bus error".
Lol miner, Phoenix work fine on my rig. Can developers explain such behaviour of TRM 0.8.4?
Thank you in advance. 

It should work fine, i have a feeling raveos is using a diff bus ordering. But it seems like an ez and already solved bug ni rave os if any. Try asking the rave os devs

[smilodon]

Hi,
I have some issues when using for xhv coin under linux ( RaveOS) comparing with windows.
Under linux my baffin cards like RX 550 2Gb, RX 560 2Gb works only 300 h/s. But it will get 500 h/s more in windows, with same core, mem, and voltage.
Let me know the problem and how to solve it.
Thank you.

try    cn_config=6+0AAA  400+ hash its driver bug on baffin.