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

[jimmyD30]

Hi, does anyone know what this error is all about - Vega64 rig, trm 0.7.13.

'Err, cmd 000000000000000000'

last update?

Yes, v0.7.13

[kerney666]

Hi, does anyone know what this error is all about - Vega64 rig, trm 0.7.13.

'Err, cmd 000000000000000000'

last update?

Yes, v0.7.13

Ha, seems that is an error printout from the API that wasn't really expected to be hit (ever). Someone/something is sending a bad command over our API. What is connecting to port 4028 on your rig?

Otherwise, did you ever join our discord? Plenty of people there including myself who can have a go at your getting your Vegas going. Our support here is very limited these days, and I also don't think it's the best place to switch to a DM session, drop you a test build directly in our chat if necessary, etc.

Also, for the record, don't believe all the bs some users are posting. The only money exchange between us and Discord is me having to pay for a Nitro membership to even be able to post our (large) release files in the discord, and that's that. 

[jimmyD30]

Hi, does anyone know what this error is all about - Vega64 rig, trm 0.7.13.

'Err, cmd 000000000000000000'

last update?

Yes, v0.7.13

Ha, seems that is an error printout from the API that wasn't really expected to be hit (ever). Someone/something is sending a bad command over our API. What is connecting to port 4028 on your rig?

Otherwise, did you ever join our discord? Plenty of people there including myself who can have a go at your getting your Vegas going. Our support here is very limited these days, and I also don't think it's the best place to switch to a DM session, drop you a test build directly in our chat if necessary, etc.

Also, for the record, don't believe all the bs some users are posting. The only money exchange between us and Discord is me having to pay for a Nitro membership to even be able to post our (large) release files in the discord, and that's that. 

Ah, I’m using Rig Cards for info reporting, might be that, thank you!

Any idea why miner (v0.7.13) sometimes shuts down on Vega64 rig (see details a page or 2 back)?

[kerney666]

Hi
Failed to initialize device idx 0 (-47)
RX5500XT and RX 5600XT
http://prntscr.com/uofgzi

Check which number of the PCI-E slots your GPUs are connected to.

1. What's the difference in connectors?
If you forcibly disable the device in the parameters, then there will be an error on the second device (1) - Failed to initialize device idx 1 (-47).
2. There are no problems in the ether mining mode.

Your GPU PCI-E slots are 0; 1; 2; 3...(My mobo has 5 PCI-E slots). Did you map them correctly so that TRM is not trying to use a slot where no GPU is connected ?

Also, Is the algo you're trying to mine actually supported by TRM on both of your GPUs ?

1. Claymore ETH OK! - http://prntscr.com/usycrn
2. TeamRedMiner ETH OK! - http://prntscr.com/usyf5s
3. TeamRedMiner HVN NO OK!!! - http://prntscr.com/usyge9
The question is, does the miner support these cards at all or not

Well, apologies for a very late reply here, but sorting it out for others to read as well: we have never ported the CN algo family to Navi, simply because Navis aren't competitive. The error you're seeing is simply due to that algo not being available on those cards. I think our error message could be MUCH clearer .

From our README:

Code:

Some algorithms are not supported on some GPU architectures and/or drivers.  Below is the compatiblity table:

|                          | Navi | Vega | Polaris |
| ------------------------ |:----:|:----:|:-------:|
| Ethash                   |  Y   |  Y   |   Y     |
| Kawpow                   |  Y   |  Y   |   Y     |
| Nimiq                    |  Y   |  Y   |   Y     |
| Cryptonight R            |  N   |  L   |   L     |
| Cryptonight v8 upx2      |  N   |  L   |   L     |
| Cryptonight v8 turtle    |  N   |  L   |   L     |
| Cryptonight v8 half      |  N   |  L   |   L     |
| Cryptonight v8 double    |  N   |  L   |   L     |
| Cryptonight v8 rwz       |  N   |  L   |   L     |
| Cryptonight v8           |  N   |  L   |   L     |
| Cryptonight heavy        |  N   |  L   |   L     |
| Cryptonight haven        |  N   |  L   |   L     |
| Cryptonight saber        |  N   |  L   |   L     |
| Cryptonight conceal      |  N   |  L   |   L     |
| Chukwa-512               |  N   |  L   |   L     |
| x16r                     |  N   |  Y   |   Y     |
| x16rv2                   |  N   |  Y   |   Y     |
| x16s                     |  N   |  Y   |   Y     |
| x16rt                    |  N   |  Y   |   Y     |
| MTP                      |  Y   |  Y   |   Y     |
| Cuckatoo31               |  N   |  Y   |   Y     |
| Cuckarood29              |  N   |  Y   |   Y     |
| Lyra2rev3                |  N   |  L   |   L     |
| Lyra2z                   |  N   |  L   |   L     |
| Phi2                     |  N   |  L   |   L     |

As you can see, we tend to add support for Navis for all new algos (of course), but the CN family is still unsupported. Might change at some point in the future given enough time, always too much stuff to do...

[kerney666]

Hi, does anyone know what this error is all about - Vega64 rig, trm 0.7.13.

'Err, cmd 000000000000000000'

last update?

Yes, v0.7.13

Ha, seems that is an error printout from the API that wasn't really expected to be hit (ever). Someone/something is sending a bad command over our API. What is connecting to port 4028 on your rig?

Otherwise, did you ever join our discord? Plenty of people there including myself who can have a go at your getting your Vegas going. Our support here is very limited these days, and I also don't think it's the best place to switch to a DM session, drop you a test build directly in our chat if necessary, etc.

Also, for the record, don't believe all the bs some users are posting. The only money exchange between us and Discord is me having to pay for a Nitro membership to even be able to post our (large) release files in the discord, and that's that. 

Ah, I’m using Rig Cards for info reporting, might be that, thank you!

Any idea why miner (v0.7.13) sometimes shuts down on Vega64 rig (see details a page or 2 back)?

I do not, and I can't say I've seen any error reports around that topic that would indicate we have some general issue. I'd love to try and help you sort it out though. First thing would be to ask you to add a log file (unless you already have it) by adding --log_file as a command line argument. It'll write a file trm_ethash_yyyymmdd_hhmmss.log in the miner directory. Then it'd be great if I could get hold of it when you have a crashed/failed instance. Again, imho discord is easier for a 1-on-1 process, dumping log files in the DM chat etc, but you can also dump the file somewhere on the net and send me a link, it's totally up to you.

[ZombieWorm]

Sorry guys, I think you merged the threads now. Does the miner support the BitTube algo yet (cuckaroo29b)?

Thanks

[jimmyD30]

with the latest update, I have constant crashes..

With v0.7.13?

Which version was stable for you and which GPUs?

[kerney666]

with the latest update, I have constant crashes..

With 0.7.14? What's your setup (os, gpus, miner arguments incl pool)? Also, can you define "crash" more carefully, does gpu(s) go dead, does the miner hang or crash etc?

[kerney666]

Sorry guys, I think you merged the threads now. Does the miner support the BitTube algo yet (cuckaroo29b)?

Thanks

Sorry, we don't, the general interest in cuckoo algos from the AMD crowd was really abysmal, so we dropped support. I believe lolminer has it though.

[2Lexx1]

TRM 0.7.14 Epoch 0 - "thread exiting with error"
RX 584 / Win10 / 19.12.2

[2020-10-16 05:11:29] GPU 0 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 1 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 2 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 3 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 4 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 5 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 0 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 2 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 1 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 3 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 4 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 5 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 0 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 2 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 1 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 3 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 4 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 5 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 0 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 0 thread exiting with error.
[2020-10-16 05:11:30] GPU 2 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 2 thread exiting with error.
[2020-10-16 05:11:30] GPU 1 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 1 thread exiting with error.
[2020-10-16 05:11:30] GPU 3 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 3 thread exiting with error.
[2020-10-16 05:11:30] GPU 4 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 4 thread exiting with error.
[2020-10-16 05:11:30] GPU 5 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 5 thread exiting with error.

[Littlegrand]

TRM does not appear to have a target temperature, just a shutdown temp.  How do you all set a target temp, through the drivers?

Thanks

[kerney666]

TRM 0.7.14 Epoch 0 - "thread exiting with error"
RX 584 / Win10 / 19.12.2

[2020-10-16 05:11:29] GPU 0 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 1 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 2 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 3 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 4 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 5 Starting DAG generation for epoch 0.
[2020-10-16 05:11:29] GPU 0 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 2 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 1 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 3 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 4 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 5 Dag progress 51.56%
[2020-10-16 05:11:30] GPU 0 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 2 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 1 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 3 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 4 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 5 Dag progress 76.56%
[2020-10-16 05:11:30] GPU 0 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 0 thread exiting with error.
[2020-10-16 05:11:30] GPU 2 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 2 thread exiting with error.
[2020-10-16 05:11:30] GPU 1 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 1 thread exiting with error.
[2020-10-16 05:11:30] GPU 3 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 3 thread exiting with error.
[2020-10-16 05:11:30] GPU 4 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 4 thread exiting with error.
[2020-10-16 05:11:30] GPU 5 Dag progress 100.00%
[2020-10-16 05:11:30] GPU 5 thread exiting with error.

Sorry, bug in 0.7.14 with the new separate kernels for 4GB gpus, happens for tiny epochs like for ZIL. Will be fixed in 0.7.15, please run 0.7.13 for now.

[kerney666]

TRM does not appear to have a target temperature, just a shutdown temp.  How do you all set a target temp, through the drivers?

Thanks

Hi! We currently don't support setting clocks/voltages and fan control in the miner, might do a project around that in the future though.

Windows users typically use the built-in AMD Wattman, Afterburner or OverdriveNTool (most common) to establish fan levels. Under linux most users are running a mining os that includes fan control. If not, they typically set a static fan level using the sysfs overdrive api.

[turtleminor13]

Hello gents, I have a feature request to make TRM even better.  Similar to "--temp_limit=TEMP", please add config setting for a Navi memory temperature limit.  I have a few 5700's that sometimes push upper 90's for mem temp, even with fans at 100%.  Would be awesome if TRM did gradual intensity ramp down to stay under the temp limit.

Alternatively, if the existing --temp_limit would accept a list to customize per GPU, could (indirectly) keep Navi mem temps roughly under a target.

[kerney666]

Hello gents, I have a feature request to make TRM even better.  Similar to "--temp_limit=TEMP", please add config setting for a Navi memory temperature limit.  I have a few 5700's that sometimes push upper 90's for mem temp, even with fans at 100%.  Would be awesome if TRM did gradual intensity ramp down to stay under the temp limit.

Alternatively, if the existing --temp_limit would accept a list to customize per GPU, could (indirectly) keep Navi mem temps roughly under a target.

Hi! I can add it to the list. It would be better from an efficiency perspective to adjust clocks instead though, but I get your point. There are also more advanced tuning options available for Navi not available in the standard Overdrive API, you need to work with the powerplay table directly. On Windows this is doable with the tools from Igor's lab, Linux is a little more annoying.

For example, lowering MVDD (mem voltage) from 1.35 to 1.3 and VDDCI to what the gpu can handle but still remain stable will probably shave off -4-5C on your mem temp. Silicon lottery involved, need to test yourself to find what your specific gpus can handle. Moreover, lowering SoC voltage while you're at it will also shave off a few watts of power and help keep overall temps under control.

[evgens1777]

TRM 0.7.14

Please support R9 390 Havaji  ETH

     
Hello there!
 
Miner Phoenix collapses, on the miner Lolminer 1.11 - 16 MH only...   
One hope - for YOU!!!
 
Sincerely. 

[fmz89]

i have issue rig stil mining but ethermine status 0 mhs reported sometimes in 2-3days mining, randomly happen

share continue nothing change but reported hashrate gone and avegare & current status  slowly downturn, seems weird, no error happening on console/miner

right now i tried different dns, something weird happen lately

this happen atleast when defi craze start, at first september, i.m using 0.6.1 btw, skipped 0.7.9 cause using 2% more power consumption

any idea new version trm will come out?

[evgens1777]

i have issue rig stil mining but ethermine status 0 mhs reported sometimes in 2-3days mining, randomly happen

share continue nothing change but reported hashrate gone and avegare & current status  slowly downturn, seems weird, no error happening on console/miner

right now i tried different dns, something weird happen lately

this happen atleast when defi craze start, at first september, i.m using 0.6.1 btw, skipped 0.7.9 cause using 2% more power consumption

any idea new version trm will come out?

TRM 0.7.15
https://github.com/todxx/teamredminer/tree/5a7ce1ec7fbfda947de3d267979b536ffc6fd99b

[livada]

i have issue rig stil mining but ethermine status 0 mhs reported sometimes in 2-3days mining, randomly happen

share continue nothing change but reported hashrate gone and avegare & current status  slowly downturn, seems weird, no error happening on console/miner

right now i tried different dns, something weird happen lately

this happen atleast when defi craze start, at first september, i.m using 0.6.1 btw, skipped 0.7.9 cause using 2% more power consumption

any idea new version trm will come out?

TRM 0.7.15
https://github.com/todxx/teamredminer/tree/5a7ce1ec7fbfda947de3d267979b536ffc6fd99b

why not see this version on first page on this topic?
i see 0.7.9 last version.

[todxx]

i have issue rig stil mining but ethermine status 0 mhs reported sometimes in 2-3days mining, randomly happen

share continue nothing change but reported hashrate gone and avegare & current status  slowly downturn, seems weird, no error happening on console/miner

right now i tried different dns, something weird happen lately

this happen atleast when defi craze start, at first september, i.m using 0.6.1 btw, skipped 0.7.9 cause using 2% more power consumption

any idea new version trm will come out?

TRM 0.7.15
https://github.com/todxx/teamredminer/tree/5a7ce1ec7fbfda947de3d267979b536ffc6fd99b

why not see this version on first page on this topic?
i see 0.7.9 last version.

My apologies. I've been slacking a bit on updating the main page.
It is now up to date.