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

[bobymoore]

gyus i mine with a 5700 xt but i get low hashrate about 18 mhs why?i mine in win 10,team red miner 0.8.

[nik-qz]

How to use this option in SMOS

--fan_control(=CFG1,CFG2,...)

example
--fan_control=61:::50:1:100 --fan_default_polaris=61:::50:1:100 --fan_default_navi=61:80:80:50:1:100

--fan_control=core:junc:mem:start fan:min fan:max fan

[fmz89]

dang rig drop 50watt on 8 vegas config with small bump on hashrate, need new ont v3.1b to support newer amd driver

lets see how stable this new version, hopefully no weird happen, any news on rx6000 series from TRM support?

[catfish78]

Hello everyone!

First day with TRM 
Can I use Phoenix settings with my RX470 8GB Samsung rigs or can I get more energy saving & shares with different settings?
Atm using B-mode  1106/2100 @ 868mV  (was rock stabla with Phoenix)

And what about RX470 4GB Elpida/Hynix rig?
Atm using max_alloc 4076   1106/1900 @ 850mV

OS: SMOS 5.4.52-sm10
Driver: amd20.30r5.6.7

[rigomortis]

Upgraded to TRM 0.8.0, then discovered I had to upgrade my AMD driver from 20.4.2, too, in order to get the new config mode B work with my RX5700s.
Then discovered I had to upgrade Overdriventool from 0.2.8 to 0.2.9, since the old version didn't work with the newer driver.  
I tried AMD driver version 20.9.1, since that was the lowest recommended, but found this to be flaky.  And overdriventool would not apply settings.  In the end I reverted back to AMD driver 20.4.2 and am now running the miner with A576 config on all my RX5700s.

amd driver 20.5.1 works with overdriventool 0.2.9.  So this will all work with TRM 0.8.0

[Lucky - Luciano]

Have anyone got any gains on RX5700? I find Poenix to be better here

For me, the hashrate has remained the same, but electricity consumption has been reduced. I have 310 MH / s for 6 x MSI 5700XT GAMING X, the power consumption measured in the socket is about 770 - 780 W.

[mineypiney]

I cannot seem to start TRM with my setup. I have a mixed rig, I wanted to use TRM and T-REX respectively for each set of cards. Right now I am using lolminer that is handling all cards with no issues, but perhaps unoptimally.

I get a failed to initialize device error. If I list devices I seem to get them all.

          Team Red Miner version 0.8.0
[2021-01-27 00:52:56] Auto-detected AMD OpenCL platform 1
[2021-01-27 00:53:04] Initializing GPU 0.
[2021-01-27 00:53:04] Failed to initialize device idx 0 (-13)
[2021-01-27 00:53:04] Successful clean shutdown.

.\teamredminer.exe --list_devices
          Team Red Miner version 0.8.0
[2021-01-27 00:54:25] Auto-detected AMD OpenCL platform 1
[2021-01-27 00:54:30] Detected 3 devices, listed in pcie bus id order:
[2021-01-27 00:54:30] Miner Platform OpenCL BusId    Name          Model                     Nr CUs
[2021-01-27 00:54:30] ----- -------- ------ -------- ------------- ------------------------- ------
[2021-01-27 00:54:30]     0        1      1 03:00.0  gfx900        Radeon RX Vega                64
[2021-01-27 00:54:30]     1        1      2 06:00.0  gfx1010       AMD Radeon RX 5700 XT         20
[2021-01-27 00:54:30]     2        1      0 10:00.0  gfx1030       AMD Radeon RX 6800 XT         36
[2021-01-27 00:54:30] Successful clean shutdown.

Any idea what's up?

[VasilyS]

I'm using Claymore monitoring API and every few days on several LInux rigs I have error "CM API Maximum connection limit reached, closing new connection". Miner is working but monitoring is stopped. What is the problem?

[pp55]

I'm using Claymore monitoring API and every few days on several LInux rigs I have error "CM API Maximum connection limit reached, closing new connection". Miner is working but monitoring is stopped. What is the problem?

Get this error on Windows too

[_javi_]

I cant get proper hashrate on the GPU connected to the monitor.
That one gets 1mhs, while the others get 53mh/s.

(3x 5700xt, win10, latest amd driver)

[scryptr]

I'm using Claymore monitoring API and every few days on several LInux rigs I have error "CM API Maximum connection limit reached, closing new connection". Miner is working but monitoring is stopped. What is the problem?

Get this error on Windows too

CM API MAXIMUM CONNECTION LIMIT REACHED ERROR--

I get this same error.  The result is a redline in EthMan, reporting a dead miner.  However, TRM is functional and mining on the reported rig.  This is a bug!  Can it be removed, or turned off with a command line flag?

--scryptr

[miner29]

I cant get proper hashrate on the GPU connected to the monitor.
That one gets 1mhs, while the others get 53mh/s.

(3x 5700xt, win10, latest amd driver)

If you have an igpu on the proc/mobo use it and mine on the gpus. 

[N2DCRYPT]

I cant get proper hashrate on the GPU connected to the monitor.
That one gets 1mhs, while the others get 53mh/s.

(3x 5700xt, win10, latest amd driver)

If you have to leave the gpu connected to the 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.

[catfish78]

2-nd day mining ETH with TRM:

Polaris 8GB - uptime 30h @ 30+ MH/s and power consumption is low!  Good job!

Polaris 4GB - crash after crash after hang after crash and so on...
Rig is not broken: tested it with ETC and all good.
Can someone please share basic Linux command line and oc/uv settings for 4GB RX470/570 cards to mine ETH?

[iRonNuke]

2-nd day mining ETH with TRM:

Polaris 8GB - uptime 30h @ 30+ MH/s and power consumption is low!  Good job!

Polaris 4GB - crash after crash after hang after crash and so on...
Rig is not broken: tested it with ETC and all good.
Can someone please share basic Linux command line and oc/uv settings for 4GB RX470/570 cards to mine ETH?

For mining Ethereum on 4 GB cards I recommend lolminer. My rig also crashes random within 5-15 mins with TRM on 4 GB cards.

[_javi_]

I cant get proper hashrate on the GPU connected to the monitor.
That one gets 1mhs, while the others get 53mh/s.

(3x 5700xt, win10, latest amd driver)

If you have to leave the gpu connected to the 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.

Thanks for the command. It solved the issue.

[Deafran]

2-nd day mining ETH with TRM:

Polaris 8GB - uptime 30h @ 30+ MH/s and power consumption is low!  Good job!

Polaris 4GB - crash after crash after hang after crash and so on...
Rig is not broken: tested it with ETC and all good.
Can someone please share basic Linux command line and oc/uv settings for 4GB RX470/570 cards to mine ETH?

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

[Semtex72]

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.

[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

[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