Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More - page 20. (Read 211432 times)

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...

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.

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!

Yes.

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

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.

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.

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.

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 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

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

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

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

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

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 ....

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

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

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.

i am using ethos with TRM

all good for my amd cards 8gb and 4gb

60°C  Fan: 2.2    Hash: 14.23    01 Ellesmere RX 470 113-D0000301_101 Samsung
61°C  Fan: 2.5    Hash: 15.00    02 Ellesmere RX 480 113-2E3471U.S5K Elpida
57°C  Fan: 2.7    Hash: 29.07    04 Ellesmere RX 480 113-2E3470U.X51 Samsung
59°C  Fan: 2.8    Hash: 30.20    05 Ellesmere RX 480 113-2E3470U.S52 Samsung
61°C  Fan: 2.9    Hash: 12.67    06 Ellesmere RX 480 113-2E3471U.S66 SK Hynix


with this setting

cor f45xxx 1075 1095 1095 1150
vlt f45xxx 950 950 950 950 950

Thanks for the command. It solved the issue.