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

[UnclWish]

Author, how to force one of GPU use one thread? I tried --cn_config 14, --cn_config 14+0 but these variants causes miner to close after run.
I need that to free some GPU power from one of gpu from mining to other purposes...

Ah, I remember you have one gpu with monitor(?). Sorry to say we don’t include a single-threaded mode since we didn’t anticipate anyone needing it, it’s rather just a risk that people enable it and you get extra support questions . But, we can probably introduce x+0 meaning that we disable the second thread. I’ll check it and schedule it for a future release.

Thanks! I'll wait this. How to lower intensity? Just lower numbers in --cn_config?

[1715386121]

1715386121

[1715386121]

1715386121

[cas333]

Hi,
Please which command can i use for temperature limit of GPU directly in bat file?

[alexmpa]

0.4.2 version has "dead gpu" problem again. One of my two vegas started crashing (underclocked gpu and memory). Latest 3.x version was working fine. Now testing 0.4.1.

Hi alexmpa,

Which algorithm are you comparing between those two versions?

Lira2REv3. Sorry, now I see that I posted in the wrong topic, it might be algo-related.

[adaseb]

Anyone here have success in mining with Windows 7?

Basically I used the stock AMD drivers 19.3 and stock bios and the most I get is like 400 Hs with a RX 470 4GB.

Increasing the settings from 1242/1650 to like 1242/2000 does little change. The AMD drivers in Win 7 don't have a compute option so you can only use those Robinhood drivers from like 2 years ago.

Using those drivers yields like 650 Hs with 1242/2000 and can't go any higher.

Wondering if I need to mod the BIOS from stock straps or is it only possible with Win 10 and Ubuntu?

[NCarter84]

Anyone here have success in mining with Windows 7?

Basically I used the stock AMD drivers 19.3 and stock bios and the most I get is like 400 Hs with a RX 470 4GB.

Increasing the settings from 1242/1650 to like 1242/2000 does little change. The AMD drivers in Win 7 don't have a compute option so you can only use those Robinhood drivers from like 2 years ago.

Using those drivers yields like 650 Hs with 1242/2000 and can't go any higher.

Wondering if I need to mod the BIOS from stock straps or is it only possible with Win 10 and Ubuntu?

Just upgrad to Win10, I'd say.

Is this your daily driver or is it a mining rig?

[P00P135]

Anyone here have success in mining with Windows 7?

Basically I used the stock AMD drivers 19.3 and stock bios and the most I get is like 400 Hs with a RX 470 4GB.

Increasing the settings from 1242/1650 to like 1242/2000 does little change. The AMD drivers in Win 7 don't have a compute option so you can only use those Robinhood drivers from like 2 years ago.

Using those drivers yields like 650 Hs with 1242/2000 and can't go any higher.

Wondering if I need to mod the BIOS from stock straps or is it only possible with Win 10 and Ubuntu?

Just use HiveOS should get 820 hash without any trouble.  Can get over 1k hash with proper straps though.

[adaseb]

I rather not upgrade to Win10 because it would be a headache.

I played around and flashed my ETH bios straps on the GPUs and now I can get 800hs with 1950Mhz memory clock rate.

I assumed you are not suppose to use ETH bios straps with XMR mining because it leads to system hangs? Been a while since I mined XMR.

What are the optimal straps for the Hynix type of RX 470/570 GPUs.

[kerney666]

Author, how to force one of GPU use one thread? I tried --cn_config 14, --cn_config 14+0 but these variants causes miner to close after run.
I need that to free some GPU power from one of gpu from mining to other purposes...

Ah, I remember you have one gpu with monitor(?). Sorry to say we don’t include a single-threaded mode since we didn’t anticipate anyone needing it, it’s rather just a risk that people enable it and you get extra support questions . But, we can probably introduce x+0 meaning that we disable the second thread. I’ll check it and schedule it for a future release.

Thanks! I'll wait this. How to lower intensity? Just lower numbers in --cn_config?

Yes, just use lower numbers in --cn_config. However, "intensity" is such a bad choice of words. It only means we will allocate less memory on the gpu, but the compute and mem bandwidth pressure won't change that much. However, if you're running a monitor, gpu mem might just be exactly the resource you want the miner to use less of, so maybe it's enough for you?

[kerney666]

Hi,
Please which command can i use for temperature limit of GPU directly in bat file?

Hi! I'm not sure I understand what you want to do? The GPU temp watchdog is enabled by default, it will pause mining on a gpu whenever the temp exceeds 85C. If you want to increase this limit you can use e.g. --temp_limit=100 to increase it to 100C. Set that high enough and you effectively disable it. The limit when it starts mining again after a pause is controlled by --temp_resume=TEMP. You can also pass --no_gpu_monitor to disable it, but that also means you won't see any temp and fan data at all in the miner.

[vmozara]

I "hate" this miner for one thing. The more GPU core you push, at least on my vegas, the H/W efficiency increases. Then, I find myself pushing the rigs to the edge of power supply limit. 

That is why i would like to see heavy/haven/sabre... implementation of this miner

[pbfarmer]

@todxx @kerney666 - i'm struggling w/ some stability issues.  linux/0.4.1/cnr/15+15 on an 8x64 rig - can run fine for 1hr or 6 hrs, but seems to always fall over eventually.  I'm definitely at oc/uv thresholds, but where normally I could isolate crashes to specific cards and adjust settings, in this case it's a different card every time.  It's not temps (all under 45c) or hardware errors (none reported by miner or syslog.)  I'm wondering if it's maybe following network hiccups or dev fee switching?  Tho i can't find any messaging in the logs - any way we can get network/dev fee notices in the logs?  I'm also seeing init discrepancies - tho not as bad as 0.4.0 - but sometimes random cards underperform by 10-15h/s run-to-run (was more like 40-50 on 0.4.0), so possibly something to do w/ that?

Also, tried 0.4.2, and it falls over w/in seconds for the same settings - seems much harsher on init for some reason.

[tvukoman]

@todxx @kerney666 - i'm struggling w/ some stability issues.  linux/0.4.1/cnr/15+15 on an 8x64 rig - can run fine for 1hr or 6 hrs, but seems to always fall over eventually.  I'm definitely at oc/uv thresholds, but where normally I could isolate crashes to specific cards and adjust settings, in this case it's a different card every time.  It's not temps (all under 45c) or hardware errors (none reported by miner or syslog.)  I'm wondering if it's maybe following network hiccups or dev fee switching?  Tho i can't find any messaging in the logs - any way we can get network/dev fee notices in the logs?  I'm also seeing init discrepancies - tho not as bad as 0.4.0 - but sometimes random cards underperform by 10-15h/s run-to-run (was more like 40-50 on 0.4.0), so possibly something to do w/ that?

Also, tried 0.4.2, and it falls over w/in seconds for the same settings - seems much harsher on init for some reason.

When switch to CNR algo, same problem with stability. Run 2 or 8 hours but than crash (and watchdog not restart miner). I noticed that always one card is crashing (unlike you).
Put 10 power more on the core 1408/960mV + lower memory to 1050 on problematic Vega 56 reference + 15+15 config solved stability problems.

For that card, 15+15 is better for stability. Normaly best results reference Vega56 flashed to 64 is 14+14.

Now running 1 day and 5 hours without crash. So try go up with core power with all cards...

[NCarter84]

doing some more testing on CN-R, on TRM 0.4.2.

I notice that I have one card just struggling to get shares.... Been running for 6 mins, GPU0 has 35 shares accepted, GPU1 has 14. Also, GPU1 has HW:3 -- I'm assume that HW = Hardware? 1st time I'm seeing this.

Fixed the HW issue, I had it set to 6+8, guess it didn't like that... So, those went away when I went to 6+6 for testing.

However, the GPU1 would stop finding shares within a min or two once I applied the clocks. So, not sure what's going on there... I did run it at stock and saw more shares being accepted...

I did some testing on CN-Heavy with JCE with my OC applied and didn't see the issues where the GPU would stop finding shares.

[cas333]

Hi,
Please which command can i use for temperature limit of GPU directly in bat file?

Hi! I'm not sure I understand what you want to do? The GPU temp watchdog is enabled by default, it will pause mining on a gpu whenever the temp exceeds 85C. If you want to increase this limit you can use e.g. --temp_limit=100 to increase it to 100C. Set that high enough and you effectively disable it. The limit when it starts mining again after a pause is controlled by --temp_resume=TEMP. You can also pass --no_gpu_monitor to disable it, but that also means you won't see any temp and fan data at all in the miner.

Simple,i dont want to leave default temps and lower them,something about 65 limit and 50 resume. I will try the commands. Thank you!

[UnclWish]

Author, how to force one of GPU use one thread? I tried --cn_config 14, --cn_config 14+0 but these variants causes miner to close after run.
I need that to free some GPU power from one of gpu from mining to other purposes...

Ah, I remember you have one gpu with monitor(?). Sorry to say we don’t include a single-threaded mode since we didn’t anticipate anyone needing it, it’s rather just a risk that people enable it and you get extra support questions . But, we can probably introduce x+0 meaning that we disable the second thread. I’ll check it and schedule it for a future release.

Thanks! I'll wait this. How to lower intensity? Just lower numbers in --cn_config?

Yes, just use lower numbers in --cn_config. However, "intensity" is such a bad choice of words. It only means we will allocate less memory on the gpu, but the compute and mem bandwidth pressure won't change that much. However, if you're running a monitor, gpu mem might just be exactly the resource you want the miner to use less of, so maybe it's enough for you?

No, it's not enough. I know about memory amount needed. And know about increasing it on higher cn_config volumes. But I need to run 1st GPU with one thread yet. Please add in next release zero thread possibility (8+0) as you wrote before.

[cas333]

My other question is how to add failover pool in bat file? Thanks

[oxzhor]

What is the correct -a for cnv8_dbl?

teamredminer.exe -a cnv8_dbl not work at windows it close the window at startup.

[kerney666]

My other question is how to add failover pool in bat file? Thanks

Hi! Pool failover support is still missing, somewhat embarassing. It's one of the few remaining features before we remove the "beta" stamp on the miner. Will be added in the near future.

[kerney666]

What is the correct -a for cnv8_dbl?

teamredminer.exe -a cnv8_dbl not work at windows it close the window at startup.

Can you provide your full cmd line? If you have the miner working fine with cnr or cnv8, you should be able to set "cnv8_dbl" as algo and change the pool/wallet/password, and things should work.

[MingMining]

Hi there,

I have a rig with mixed 480 and 580. I used command like:

teamredminer.exe -a cnr -o stratum+tcp://pool.supportxmr.com:7777 -u 84PDXS6PngdBh2XUd28jbN3Sb69RXPq7gdCNVukcrFCj1v6jgb13uEpHrzf6DF9cDjKCToaS842gLx8 sgF1jNCNGfuFgi -p amd:cryptocoins@outlook.com
-d 0,1,2,3,4,5 --cn_config 8+8,8+8,8+8,8+8,8+8,8+8


Here is what I got:

         Team Red Miner version 0.4.2
[2019-03-17 16:37:13] Auto-detected AMD OpenCL platform 0
[2019-03-17 16:37:20] Initializing GPU 0.
[2019-03-17 16:37:20] Watchdog thread starting.
[2019-03-17 16:37:20] Pool pool.supportxmr.com connecting to address 104.140.201.62.
[2019-03-17 16:37:20] Pool pool.supportxmr.com successfully connected to address 104.140.201.62.
[2019-03-17 16:37:20] Pool pool.supportxmr.com login succeeded.(76 ms)
[2019-03-17 16:37:20] Pool pool.supportxmr.com received new job. (job_id: cnLOlcrewGdcVf1XzQRbdhjwp1Vb)
[2019-03-17 16:37:20] Pool pool.supportxmr.com set difficulty to 40000
[2019-03-17 16:37:21] Dev pool connected and ready.
[2019-03-17 16:37:25] Pool pool.supportxmr.com received new job. (job_id: XIB96CLjgQdVKYBbNUaRktOh8rcO)
[2019-03-17 16:37:25] Pool pool.supportxmr.com set difficulty to 68571
[2019-03-17 16:37:50] Stats Uptime: 0 days, 00:00:32
[2019-03-17 16:37:50] GPU 0 [30C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:37:50] GPU 1 [28C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:37:50] GPU 2 [29C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:37:50] GPU 3 [29C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:37:50] GPU 4 [28C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:37:50] GPU 5 [23C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:37:50] Total                cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:20] Stats Uptime: 0 days, 00:01:02
[2019-03-17 16:38:20] GPU 0 [29C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:20] GPU 1 [27C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:20] GPU 2 [29C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:20] GPU 3 [28C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:20] GPU 4 [28C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:20] GPU 5 [23C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:20] Total                cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:25] Pool pool.supportxmr.com received new job. (job_id: i5dMQvSKsNVfeMp9FbvfyScUpeu5)
[2019-03-17 16:38:25] Pool pool.supportxmr.com set difficulty to 45714
[2019-03-17 16:38:50] Stats Uptime: 0 days, 00:01:32
[2019-03-17 16:38:50] GPU 0 [29C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:50] GPU 1 [27C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:50] GPU 2 [29C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:50] GPU 3 [28C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:50] GPU 4 [27C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:50] GPU 5 [23C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:38:50] Total                cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:39:10] GPU 0: detected DEAD (34:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:10] GPU 1: detected DEAD (30:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:10] GPU 2: detected DEAD (31:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:10] GPU 3: detected DEAD (38:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:10] GPU 4: detected DEAD (01:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:10] GPU 5: detected DEAD (35:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:10] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:20] Stats Uptime: 0 days, 00:02:02
[2019-03-17 16:39:20] GPU 0 [29C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:39:20] GPU 1 [27C, fan 55%] cnr:   0.0 h/s, avg   0.0 h/s, pool   0.0 h/s a:0 r:0 hw:0
[2019-03-17 16:39:20] GPU 0: detected DEAD (34:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:20] GPU 1: detected DEAD (30:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:20] GPU 2: detected DEAD (31:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:20] GPU 3: detected DEAD (38:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:20] GPU 4: detected DEAD (01:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.
[2019-03-17 16:39:20] GPU 5: detected DEAD (35:00.0), no restart script configured, will continue mining.
[2019-03-17 16:39:20] Please use command line argument --watchdog_script to handle dead GPUs.