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

[heavyarms1912]

hi,

i'm new on TRM. i have 4 vega red evil 56 card hynix ,with my settings from claymore i get a hashrate on 43mh/s
930mhz mem 1050 core on 900mv can't get the mem higher.
 i try modded the mem timings with the amdmemorytweakxl tool.

i always get the 43mh/s
i'm not sure i've im doing it right. try the changes from the ethgenreraltuning list in tweak tool. apply.

does TRM auto tuning reset this settings? or do i have to add anything in the command line?

thy

The 43 MH/s is the classic limit at stock timings, so it really sounds like the changed timings aren't being applied properly for you. The miner doesn't touch anything related to clocks/voltages/timings, only the fan curve if you have fan control enabled.

It's hard to say why the timings aren't being applied. If you start the miner and let it run for a few mins, then open amdmemtweakxl and e.g. boost tREF to 17000 or make a slight adjustment down for tRCDWR and apply the changes, does the hashrate move in the miner? If not, what timing are displayed of you close+reopen amdmemtweakxl, are your changes there?

hi, thx

now i got 46 mh/s with 1700 on ref and 20rcdrd and 4 rcdwr. there was no diference with rcdwr starts on 10.

does the settings from tweak tool reset after pc restart? watchdog is enabled with restart the system.
can i set a target temp for fan with command line ? or just settingfan speed?

My bad, I wrote rcdwr but really meant rcdrd. That's the one you want to lower slowly. Also, did you do 1700 or 17000 for ref?

For fan control, you can target a core temp, junction temp, or mem temp, set the initial fan speed or a static fan speed. Use --fan_control --fan_default_vega=::70:60 to target 70C mem temp with fans initially at 60%.

I start with 17000 on ref an go down to 18 on rcdrd but it was  not stable. ref is now on 15600 and rcdrd 20 is stable for a few hours. hashrate is 46mh/s. i set the target temp on 55
But on restart the settings are lost.

monitor your hbm2 temperatures.  Also you don't need 900mV on core.

[1713938771]

1713938771

[1713938771]

1713938771

[1713938771]

1713938771

[jimmyD30]

Hey Folks, with the help of TRM (Kerney, et al.) I made a TRM monitoring and alerting system app for iOS. It's FREE for 1 miner with local and remote monitoring - check it out and let me know what you think!

MINERTRON™ Comprehensive Miner Monitoring & Alerting System App for iOS: https://apps.apple.com/us/app/minertron/id1541270467

Bitcoin talk thread: https://bitcointalk.org/index.php?topic=5298800.new#new

[pp55]

Hi!
Is there any free way to monitir 20-30 rigs mining under Windows?
Thometing like this tool - Claymore's Ethereum Dual Miner Manager Connector https://bitcointalk.org/index.php?topic=4324950 or standalone?

[turtleminor13]

kerney666 - thanks for moving the ETH Cfg values into the upper table of detail stats with the v0.7.19 release.  Was going to request something like that, so ETH Cfg didn't take up it's own section of extra lines per gpu, but now it's already nice and compacted.

[kerney666]

kerney666 - thanks for moving the ETH Cfg values into the upper table of detail stats with the v0.7.19 release.  Was going to request something like that, so ETH Cfg didn't take up it's own section of extra lines per gpu, but now it's already nice and compacted.

Yeah I moved it since it became even more ridiculous when the new (optional) high score list was added, using even more vertical space . I also enjoy this version much more myself, should have moved it with the last rewrite of the stats output really.

[batsonxl]

Hi guys,
Does any one know how to set core memory speed and voltage on bat file?thanks

[kerney666]

Hi guys,
Does any one know how to set core memory speed and voltage on bat file?thanks

Hi! Sorry, we don't support setting clocks/voltages/timings in the miner, we're relying on mining os distros and tools like OverdriveNTool or MSI Afterburner on win. We do have it on the roadmap, but it most probably won't happen before the ongoing crazy 4GB period has slowed down.

[peteycamey]

api_listen=127.0.0.1:3333 doesnt seem to work with claymores miner manager 4.0

[andrew82]

Hello Miners!

Can you please tell me if there any way to decrease mining intensity when particular card is overheating, like options "-ttli" and "-tstop" in claymore?

Thank you, and "May the Profit be with you"

[livada]

[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com received new job. (job_id: 0x3bef404a660..., diff 0.250 / 1074 MH)
[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com share rejected. (GPU3) Error code: 23 - Low difficulty (a:126 r:1u) (356 ms) (diff 4.98 GH)

What is this error? i see this error every 2-3 hour and reject

miner is stable and work fine 3-4 days but have 1% reject

other ring identical. work fine but 1% reject for error code 23

[batsonxl]

Hi guys,
Does any one know how to set core memory speed and voltage on bat file?thanks

Hi! Sorry, we don't support setting clocks/voltages/timings in the miner, we're relying on mining os distros and tools like OverdriveNTool or MSI Afterburner on win. We do have it on the roadmap, but it most probably won't happen before the ongoing crazy 4GB period has slowed down.

ok understood. will be very cool if you can add this. thanks for your time

[pp55]

And yes, support for Claymore's Miner Manager is on the TODO list. Will probably be read-only.

Can't wait for it
This is the only thing that stops me from switching to TRM from Phoenixminer

[Yirvenpaeae]

hi,

i'm new on TRM. i have 4 vega red evil 56 card hynix ,with my settings from claymore i get a hashrate on 43mh/s
930mhz mem 1050 core on 900mv can't get the mem higher.
 i try modded the mem timings with the amdmemorytweakxl tool.

i always get the 43mh/s
i'm not sure i've im doing it right. try the changes from the ethgenreraltuning list in tweak tool. apply.

does TRM auto tuning reset this settings? or do i have to add anything in the command line?

thy

The 43 MH/s is the classic limit at stock timings, so it really sounds like the changed timings aren't being applied properly for you. The miner doesn't touch anything related to clocks/voltages/timings, only the fan curve if you have fan control enabled.

It's hard to say why the timings aren't being applied. If you start the miner and let it run for a few mins, then open amdmemtweakxl and e.g. boost tREF to 17000 or make a slight adjustment down for tRCDWR and apply the changes, does the hashrate move in the miner? If not, what timing are displayed of you close+reopen amdmemtweakxl, are your changes there?

hi, thx

now i got 46 mh/s with 1700 on ref and 20rcdrd and 4 rcdwr. there was no diference with rcdwr starts on 10.

does the settings from tweak tool reset after pc restart? watchdog is enabled with restart the system.
can i set a target temp for fan with command line ? or just settingfan speed?

My bad, I wrote rcdwr but really meant rcdrd. That's the one you want to lower slowly. Also, did you do 1700 or 17000 for ref?

For fan control, you can target a core temp, junction temp, or mem temp, set the initial fan speed or a static fan speed. Use --fan_control --fan_default_vega=::70:60 to target 70C mem temp with fans initially at 60%.

I start with 17000 on ref an go down to 18 on rcdrd but it was  not stable. ref is now on 15600 and rcdrd 20 is stable for a few hours. hashrate is 46mh/s. i set the target temp on 55
But on restart the settings are lost.

thanks a lot!

one more question. i now run the vegas with ref 15600 rc 35 rcdrd 19 get 47 mh/s hashrate when auto tune set konfig on a1024.
but autotune set is not erverytime the same for example now 1 card is on eth config a736 and there are only 44mh's hashrate . Same cards with the same settings.

Can i set the eth config fix in the command line? or start autotune new?
and i need help with a batch file for amd tweak tool for startup i've the amdtweaktoolxl and i wrote

(folder of tweak toolxl...).exe --i 0,1,2,3,4,5 --rcdrd 19 --REF 15600 --rfc 164 --rc 35

it opens the tweak tool but didn't set any settings?

thx

[calvinwch]

Hi guys, i try to use teamredminer but every time when i run the batch the screen just disappear.  Any one know why this happen?  Windows 10 with AMD 580 card.

[kerney666]

[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com received new job. (job_id: 0x3bef404a660..., diff 0.250 / 1074 MH)
[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com share rejected. (GPU3) Error code: 23 - Low difficulty (a:126 r:1u) (356 ms) (diff 4.98 GH)

What is this error? i see this error every 2-3 hour and reject

miner is stable and work fine 3-4 days but have 1% reject

other ring identical. work fine but 1% reject for error code 23

Pretty high accept roundtrip time on that share, looks like a Nicehash reject as well. Is this a rental period or are you falling back to Nicehash between rentals? Nicehash are horrible with their reject policy, they pump out jobs and reject anything for "old" jobs from 200ms ago. You can see that you just received a new job right before the share was rejected, so my guess is simply that the share was for the prev job, and the underlying pool (Nicehash or not) rejects it.

[kerney666]

api_listen=127.0.0.1:3333 doesnt seem to work with claymores miner manager 4.0

We'll add a built-in adapter to our own API so it'll work with Claymore's old stuff shortly, one-two versions away.

[kerney666]

Hello Miners!

Can you please tell me if there any way to decrease mining intensity when particular card is overheating, like options "-ttli" and "-tstop" in claymore?

Thank you, and "May the Profit be with you"

Sorry, not atm. The plan is to tie it to our fan control, i.e. you provide the target temp for the fans, if we can't manage to hold the target temp even with fans blasting, we'll revert to throttling the intensity instead.

For hard start/stop limits (more for protection against broken fans) we have:

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.

[kerney666]

thanks a lot!

one more question. i now run the vegas with ref 15600 rc 35 rcdrd 19 get 47 mh/s hashrate when auto tune set konfig on a1024.
but autotune set is not erverytime the same for example now 1 card is on eth config a736 and there are only 44mh's hashrate . Same cards with the same settings.

Can i set the eth config fix in the command line? or start autotune new?
and i need help with a batch file for amd tweak tool for startup i've the amdtweaktoolxl and i wrote

(folder of tweak toolxl...).exe --i 0,1,2,3,4,5 --rcdrd 19 --REF 15600 --rfc 164 --rc 35

it opens the tweak tool but didn't set any settings?

thx

Use --eth_config=A1024 to make all cards use A1024. If you have a mixed rig, you might need to specify each gpu individually with --eth_config=A1024,A288,A1024 for a Vega+Polaris+Vega setup. The autotune shouldn't really miss that much though, I wonder if you were throttled or something during the tuning, hmm.

For the mem tweaks, you need to download the command line tool, not the xl tool. Grab it here: https://github.com/Eliovp/amdmemorytweak/releases/tag/0.1.9.1. Download WinAMDTweak.exe, IOMap.sys, IOMap64.sys. Then, you need to go to version 0.1.8.1 and download EIO.dll as well. ElioVP missed including that file in the 0.1.9.1 release. Last, run WinAMDTweak.exe as Administrator using your arguments listed above and it should work.

[livada]

[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com received new job. (job_id: 0x3bef404a660..., diff 0.250 / 1074 MH)
[2020-12-12 18:37:57] Pool eu-01.miningrigrentals.com share rejected. (GPU3) Error code: 23 - Low difficulty (a:126 r:1u) (356 ms) (diff 4.98 GH)

What is this error? i see this error every 2-3 hour and reject

miner is stable and work fine 3-4 days but have 1% reject

other ring identical. work fine but 1% reject for error code 23

Pretty high accept roundtrip time on that share, looks like a Nicehash reject as well. Is this a rental period or are you falling back to Nicehash between rentals? Nicehash are horrible with their reject policy, they pump out jobs and reject anything for "old" jobs from 200ms ago. You can see that you just received a new job right before the share was rejected, so my guess is simply that the share was for the prev job, and the underlying pool (Nicehash or not) rejects it.

not NH. NH have 2-3% reject with identical error. i dont konow what pool is this. this is rentals rig and user use pool but i not see wich pool.
but i see this error code 23 and on ethermine and nanopool. 0,5-1%

[jiang80s]

The RX 550 Baffin cards are running on Linux based RAVE OS with low hashrate comparing with the RX 550 Lexa cards.
Baffin only gets 300 H/s, but Lexa gets 520 H/s at CN haven using TRM newest version.
All cards are elpida memory and using memory straps from SRB. 1150/870mV core and 1900/870mV memory.
When I run baffin cards rigs on win 10, it gets 480 H/s each.

Can anyone help me to solve this problem ?

Thank you.