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

[jebidia]

I now have several Radeon VII doing 98Mhs in Windows, I'm just using the strap 2 option in the driver. Distance between the cards is important as well as fan speed.

Could you share your settings:  core, mem vltg and power usage?  I'm not seeing anything about a strap option in the info files in the miner...I see a "C" option for VII on linux

My clocks with no strap are core 1550 mem 1100 vltg 850 at about 84.7 @ 144 watts on eth Windows

[1715583045]

1715583045

[denialo]

i was running until today teamredminer-v0.7.16c-linux well and stable with 4GB RX580's
now i upgraded to teamredminer-v0.8.0-linux and i'm doomed, everything is killed and OS hangs. disabling oom does not help.
trying to revert to old version ...

Description:    Ubuntu 20.04.2 LTS
Linux bana2 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Jan 29 21:50:07 bana2 kernel: [  102.094797] teamredminer invoked oom-killer: gfp_mask=0x0(), order=0, oom_score_adj=0
Jan 29 21:50:07 bana2 kernel: [  102.094810]  oom_kill_process.cold+0xb/0x10
Jan 29 21:50:07 bana2 kernel: [  102.095002] [   2054]   125  2054   114908     1544   118784        0             0 gsd-rfkill
Jan 29 21:50:07 bana2 kernel: [  102.095069] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/sess
ion-2.scope,task=teamredminer,pid=2669,uid=1000
Jan 29 21:50:07 bana2 kernel: [  102.095121] Out of memory: Killed process 2669 (teamredminer) total-vm:3350016kB, anon-rss:407016kB, file-rss:80040kB, shmem-rss:0kB, UID:1000
 pgtables:1848kB oom_score_adj:0
Jan 29 21:50:14 bana2 kernel: [  109.108747] kworker/3:4 invoked oom-killer: gfp_mask=0x2dc2(GFP_KERNEL|__GFP_HIGHMEM|__GFP_NOWARN|__GFP_ZERO), order=0, oom_score_adj=0
Jan 29 21:50:14 bana2 kernel: [  109.108763]  oom_kill_process.cold+0xb/0x10
Jan 29 21:50:14 bana2 kernel: [  109.109611] [   2054]   125  2054   114908      219   118784        0             0 gsd-rfkill
Jan 29 21:50:14 bana2 kernel: [  109.109683] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-125.slice/sessi
on-c1.scope,task=gnome-shell,pid=1762,uid=125
Jan 29 21:50:14 bana2 kernel: [  109.109863] Out of memory: Killed process 1762 (gnome-shell) total-vm:6155536kB, anon-rss:91148kB, file-rss:1940kB, shmem-rss:40kB, UID:125 pg
tables:1672kB oom_score_adj:0
Jan 29 21:50:15 bana2 kernel: [  109.214566] dbus-daemon invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=-900
Jan 29 21:50:15 bana2 kernel: [  109.214579]  oom_kill_process.cold+0xb/0x10
Jan 29 21:50:15 bana2 kernel: [  109.214795] [   2054]   125  2054   114908      155   118784        0             0 gsd-rfkill
Jan 29 21:50:15 bana2 kernel: [  109.214864] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-125.slice/sessi
on-c1.scope,task=Xwayland,pid=2001,uid=125
Jan 29 21:50:15 bana2 kernel: [  109.214896] Out of memory: Killed process 2001 (Xwayland) total-vm:1329084kB, anon-rss:19808kB, file-rss:0kB, shmem-rss:0kB, UID:125 pgtables:
428kB oom_score_adj:0

[fmz89]

do you think maxout vram on mining will degrade gpu faster, all my 4gb gpus already died and 8gb gpus still running

just wondering because miner utilize all memory and gpu died faster ....

[heavyarms1912]

do you think maxout vram on mining will degrade gpu faster, all my 4gb gpus already died and 8gb gpus still running

just wondering because miner utilize all memory and gpu died faster ....

won't die just caused it used all of memory available.  it might be just more stress on the memory controller or heat.

[JonnyJalapeno]

Getting 11MH/s on ETH with 5700 XT, on older version like 0.7.22 i got 50mh/s. Haven't changed anything.

[profcb]

I'm using TRM  v.0.8.0 for mining ETH on my Vegas 54 & 64.

Can someone explain me how to set the amdmemtweak for  GPUs on HIVEOS to be permanent?
Each time the miner resets or crashes, I have to enter them again.

Any advice would be a great help. Thanks

[JonnyJalapeno]

Im sticking with latest WHQL drivers and 0.7.22 version, works like a charm. I hope you will release hotfix for newest drivers.

[th00ber]

I'm using TRM  v.0.8.0 for mining ETH on my Vegas 54 & 64.

Can someone explain me how to set the amdmemtweak for  GPUs on HIVEOS to be permanent?
Each time the miner resets or crashes, I have to enter them again.

Any advice would be a great help. Thanks

I have the same problem.
It would be great if TRM allow to run a pre-mining script like T-Rex does.
But to be honest, my rig is really stable and and the command are in the quick access of the HiveOS "run command" dashboard, so it's not so bad ... but it could be a really cool feature

[Yirvenpaeae]

hi,

i tried to flash my vega 64 nitro with the 56 bios on hiveos.
its going wrong and my card didnt get recognized,
can anyone help me to flash it back?
or with the correct 56 bios, and how to see the card?
thx

[Zealotki11er]

This has been fantastic for my V64 and VII. Was getting much lower numbers with other miners. Not I am at 50 for V64 and 90 with VII.

[N2DCRYPT]

Getting 11MH/s on ETH with 5700 XT, on older version like 0.7.22 i got 50mh/s. Haven't changed anything.

If you have the gpu connected to a monitor, add argument --eth_big_mode_adjust=1024. It's a resolution issue and the miner can overallocate VRAM unless you add this argument. Will be addressed in a future release.

[gyIQ]

Hello,

I moved the rig to another location, where I can feed the net only via a wifi repeater in bridge mode. I have access to the rig, I can modify anything under hiveos but can not connect to the pool. I can also ping the pool.

[2021-02-02 11:07:19] Pool eu-eth.hiveon.net connecting to address 0.0.0.0.                                                                                                                                                                                                                
[2021-02-02 11:07:19] Pool eu-eth.hiveon.net failed to connect to address 0.0.0.0.
[2021-02-02 11:07:19] Pool eu-eth.hiveon.net failed to connect.

Does anyone has an idea why? Earlier, when I connected wired to the net all went fine, rig was mining.

#update
disabled dhcp on the repeater, now all fine.

[m3scott]

So for a multiple GPU rig, I would just set eth config with commas similar to this?   --eth_config=A,B,,,C,B   ?

[N2DCRYPT]

So for a multiple GPU rig, I would just set eth config with commas similar to this?   --eth_config=A,B,,,C,B   ?

Yes.

[joseph32]

Hey Team,

for nVidia cards I use T-Rex, because of this great feature: "--keep-gpu-busy". Which means, if the miner has no internet connection or some trouble with pause-instability, it will still fake mine with full load. Especially now in the winter days and in a colder environment a connection loss wouldn't damage the GPU's because they are always under load.

Is it possible to create a similar feature for the TRM? This would make your miner even better

P.S. Thanks for the 0.8.0 version!

[uninterestedparty33]

Hey Team,

for nVidia cards I use T-Rex, because of this great feature: "--keep-gpu-busy". Which means, if the miner has no internet connection or some trouble with pause-instability, it will still fake mine with full load. Especially now in the winter days and in a colder environment a connection loss wouldn't damage the GPU's because they are always under load.

Is it possible to create a similar feature for the TRM? This would make your miner even better

P.S. Thanks for the 0.8.0 version!

Huh? That sounds horrible. Wasting electricity to do nothing? Mining in the long term does cause degradation, and this has been known since like 2011.

[joseph32]

Huh? That sounds horrible. Wasting electricity to do nothing? Mining in the long term does cause degradation, and this has been known since like 2011.

Maybe you should read it carefully. Its to protect the hardware just in case. This is one of the greatest feature of that miner. A few dollars can save thousands...

[sxemini]

Huh? That sounds horrible. Wasting electricity to do nothing? Mining in the long term does cause degradation, and this has been known since like 2011.

Maybe you should read it carefully. Its to protect the hardware just in case. This is one of the greatest feature of that miner. A few dollars can save thousands...

And how will a loose of internet connection damage your hardware? In my case, my cards are in extra bulding and in winter i have some windows open and many of my cards run with 10 or 20C° and they are running fine. It is better that the cards don´t work if they have no connection. So can you explain how that will protect your hardware?
Colder is always better for gpu´s!!!!!!!

[joseph32]

Huh? That sounds horrible. Wasting electricity to do nothing? Mining in the long term does cause degradation, and this has been known since like 2011.

Maybe you should read it carefully. Its to protect the hardware just in case. This is one of the greatest feature of that miner. A few dollars can save thousands...

And how will a loose of internet connection damage your hardware? In my case, my cards are in extra bulding and in winter i have some windows open and many of my cards run with 10 or 20C° and they are running fine. It is better that the cards don´t work if they have no connection. So can you explain how that will protect your hardware?
Colder is always better for gpu´s!!!!!!!

Iam not talking about running cards, thats a huge difference (and no, its not better). Cards without any workload and below ambient temperature (for whatever reason this happened) will create condensation. Condensation and cold environment is a really bad thing which can kill hardware easily if the load wont return fast enough to heat up the cards. Condensation on watercooled parts will kill the hardware in minutes. If you dont need such option, dont use it, easy and simple. But I bet there are many people outthere which appreciate such an option.

[Yirvenpaeae]

hi,

i tried to flash my vega 64 nitro with the 56 bios on hiveos.
its going wrong and my card didnt get recognized,
can anyone help me to flash it back?
or with the correct 56 bios, and how to see the card?
thx

i got it.

the vega runs with 54 mh/s at 1100 on core and 1028 on mem with 850 mv on both.
tweak timings cl 20 ras 26 rcdrc 12 rcdwr 12 rc 38 rp 12 rrds 3 rrdl 5 rtp 6 faw 12 cwl 8 wtrs 4 wtrl 9 wr 13 ref 15600 rfc 239

is there better settings with the new trm v8.0?
i run it on windows, with 4 vega 56 power coler at 48 mh and 1 vega 56 phantom on 51mhs (morpheus cooler) mem temp set on 62
i've i try to overclock in hive i got many errors with powerplay table.
What do i wrong?
Is there an hashrate increase of switching to hive? when it runs?

thx