awesome! can you disable or change the watchdog?
What are you looking to do? The watchdog checks for a number of things: shuts on/off a gpu if the temp go out of range, executes your watchdog script if a gpu dies, then some internal checks as well.
Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 29. (Read 85791 times)
November 30, 2018, 09:46:36 AM
What are you looking to do? The watchdog checks for a number of things: shuts on/off a gpu if the temp go out of range, executes your watchdog script if a gpu dies, then some internal checks as well.
November 30, 2018, 09:43:04 AM
What's the command for fan control? (say I want it to set it to 50% all the time)
me too
thanks
me too
thanks
Hey guys! Sorry to disappoint, it's only sensors and watchdog in this release, can't control fans/clocks. We print and react to the temp, but no support for changing fans for now. Fan control is much simpler than clocks though, I'm sure we can slot that in for an upcoming release.
November 29, 2018, 08:50:19 PM
What's the command for fan control? (say I want it to set it to 50% all the time)
me too
thanks
me too
thanks
November 29, 2018, 03:20:52 AM
Hi! I have a following problem with trm 0.3.8 and 0.3.7 and my rx 552. GPU0-2 are saphire rx550 2gb baffin with elpida 1180/1900. GPU3 is gigabyte rx550 2gb with hynix 1200/2000. They working stable with srb.
Windows 8.1 with 18.3.4 driver
Every time strictly after 15min uptime current hashrate becomes too high on all or almost all gpus (the can be different on other rig start). Avg begin to drop. Reportet pool hashrate aim to avg. I've tried to reduce intensity to 3+2, L3+2, reduce overclock to extremely low - 1100/1850 on baffins and 1180/1950 on lexa but problem occures again at same uptime 15min.
Windows 8.1 with 18.3.4 driver
Quote
[2018-11-28 23:13:10] Successfully initialized GPU 0: Polaris with 12 CU (PCIe 01:00.0) (CN 4+3)
[2018-11-28 23:13:10] Successfully initialized GPU 1: Polaris with 12 CU (PCIe 03:00.0) (CN 4+3)
[2018-11-28 23:13:10] Successfully initialized GPU 2: Polaris with 12 CU (PCIe 06:00.0) (CN 4+3)
[2018-11-28 23:13:10] Successfully initialized GPU 3: Polaris with 8 CU (PCIe 04:00.0) (CN L4+3)
...
[2018-11-28 23:27:38] Stats Uptime: 0 days, 00:14:30
[2018-11-28 23:27:38] GPU 0 [50C, fan 19%] cnv8: 515.7 h/s, avg 519.3 h/s, pool 495.5 h/s a:43 r:0 hw:0
[2018-11-28 23:27:38] GPU 1 [54C, fan 19%] cnv8: 520.5 h/s, avg 517.9 h/s, pool 472.5 h/s a:41 r:0 hw:0
[2018-11-28 23:27:38] GPU 2 [51C, fan 19%] cnv8: 522.9 h/s, avg 518.1 h/s, pool 507.2 h/s a:44 r:0 hw:0
[2018-11-28 23:27:38] GPU 3 [44C, fan 33%] cnv8: 549.7 h/s, avg 548.1 h/s, pool 472.7 h/s a:41 r:0 hw:0
[2018-11-28 23:27:38] Total cnv8: 2.109kh/s, avg 2.103kh/s, pool 1.948kh/s a:169 r:0 hw:0
...
[2018-11-28 23:28:08] Stats Uptime: 0 days, 00:15:00
[2018-11-28 23:28:08] GPU 0 [49C, fan 19%] cnv8: 518.6 h/s, avg 519.5 h/s, pool 490.0 h/s a:44 r:0 hw:0
[2018-11-28 23:28:08] GPU 1 [54C, fan 19%] cnv8: 529.0 h/s, avg 517.7 h/s, pool 467.9 h/s a:42 r:0 hw:0
[2018-11-28 23:28:08] GPU 2 [49C, fan 19%] cnv8: 520.2 h/s, avg 517.3 h/s, pool 512.6 h/s a:46 r:0 hw:0
[2018-11-28 23:28:08] GPU 3 [45C, fan 0%] cnv8: 560.9 h/s, avg 547.9 h/s, pool 456.9 h/s a:41 r:0 hw:0
[2018-11-28 23:28:08] Total cnv8: 2.129kh/s, avg 2.102kh/s, pool 1.927kh/s a:173 r:0 hw:0
...
[2018-11-28 23:28:38] Stats Uptime: 0 days, 00:15:30
[2018-11-28 23:28:38] GPU 0 [50C, fan 19%] cnv8: 518.7 h/s, avg 519.5 h/s, pool 485.0 h/s a:45 r:0 hw:0
[2018-11-28 23:28:38] GPU 1 [53C, fan 19%] cnv8: 841.8 h/s, avg 514.2 h/s, pool 463.5 h/s a:43 r:0 hw:0
[2018-11-28 23:28:38] GPU 2 [49C, fan 19%] cnv8: 839.9 h/s, avg 514.4 h/s, pool 528.3 h/s a:49 r:0 hw:0
[2018-11-28 23:28:38] GPU 3 [46C, fan 33%] cnv8: 941.5 h/s, avg 545.7 h/s, pool 442.2 h/s a:41 r:0 hw:0
[2018-11-28 23:28:38] Total cnv8: 3.142kh/s, avg 2.094kh/s, pool 1.919kh/s a:178 r:0 hw:0
...
[2018-11-29 08:59:08] Stats Uptime: 0 days, 09:46:00
[2018-11-29 08:59:08] GPU 0 [47C, fan 19%] cnv8: 518.1 h/s, avg 520.0 h/s, pool 499.7 h/s a:1757 r:0 hw:0
[2018-11-29 08:59:08] GPU 1 [56C, fan 19%] cnv8: 515.2 h/s, avg 490.7 h/s, pool 477.8 h/s a:1680 r:0 hw:0
[2018-11-29 08:59:08] GPU 2 [48C, fan 19%] cnv8: 835.0 h/s, avg 429.7 h/s, pool 427.2 h/s a:1502 r:0 hw:0
[2018-11-29 08:59:08] GPU 3 [43C, fan 0%] cnv8: 937.9 h/s, avg 458.4 h/s, pool 441.2 h/s a:1551 r:0 hw:0
[2018-11-29 08:59:08] Total cnv8: 2.806kh/s, avg 1.899kh/s, pool 1.846kh/s a:6490 r:0 hw:0
[2018-11-28 23:13:10] Successfully initialized GPU 1: Polaris with 12 CU (PCIe 03:00.0) (CN 4+3)
[2018-11-28 23:13:10] Successfully initialized GPU 2: Polaris with 12 CU (PCIe 06:00.0) (CN 4+3)
[2018-11-28 23:13:10] Successfully initialized GPU 3: Polaris with 8 CU (PCIe 04:00.0) (CN L4+3)
...
[2018-11-28 23:27:38] Stats Uptime: 0 days, 00:14:30
[2018-11-28 23:27:38] GPU 0 [50C, fan 19%] cnv8: 515.7 h/s, avg 519.3 h/s, pool 495.5 h/s a:43 r:0 hw:0
[2018-11-28 23:27:38] GPU 1 [54C, fan 19%] cnv8: 520.5 h/s, avg 517.9 h/s, pool 472.5 h/s a:41 r:0 hw:0
[2018-11-28 23:27:38] GPU 2 [51C, fan 19%] cnv8: 522.9 h/s, avg 518.1 h/s, pool 507.2 h/s a:44 r:0 hw:0
[2018-11-28 23:27:38] GPU 3 [44C, fan 33%] cnv8: 549.7 h/s, avg 548.1 h/s, pool 472.7 h/s a:41 r:0 hw:0
[2018-11-28 23:27:38] Total cnv8: 2.109kh/s, avg 2.103kh/s, pool 1.948kh/s a:169 r:0 hw:0
...
[2018-11-28 23:28:08] Stats Uptime: 0 days, 00:15:00
[2018-11-28 23:28:08] GPU 0 [49C, fan 19%] cnv8: 518.6 h/s, avg 519.5 h/s, pool 490.0 h/s a:44 r:0 hw:0
[2018-11-28 23:28:08] GPU 1 [54C, fan 19%] cnv8: 529.0 h/s, avg 517.7 h/s, pool 467.9 h/s a:42 r:0 hw:0
[2018-11-28 23:28:08] GPU 2 [49C, fan 19%] cnv8: 520.2 h/s, avg 517.3 h/s, pool 512.6 h/s a:46 r:0 hw:0
[2018-11-28 23:28:08] GPU 3 [45C, fan 0%] cnv8: 560.9 h/s, avg 547.9 h/s, pool 456.9 h/s a:41 r:0 hw:0
[2018-11-28 23:28:08] Total cnv8: 2.129kh/s, avg 2.102kh/s, pool 1.927kh/s a:173 r:0 hw:0
...
[2018-11-28 23:28:38] Stats Uptime: 0 days, 00:15:30
[2018-11-28 23:28:38] GPU 0 [50C, fan 19%] cnv8: 518.7 h/s, avg 519.5 h/s, pool 485.0 h/s a:45 r:0 hw:0
[2018-11-28 23:28:38] GPU 1 [53C, fan 19%] cnv8: 841.8 h/s, avg 514.2 h/s, pool 463.5 h/s a:43 r:0 hw:0
[2018-11-28 23:28:38] GPU 2 [49C, fan 19%] cnv8: 839.9 h/s, avg 514.4 h/s, pool 528.3 h/s a:49 r:0 hw:0
[2018-11-28 23:28:38] GPU 3 [46C, fan 33%] cnv8: 941.5 h/s, avg 545.7 h/s, pool 442.2 h/s a:41 r:0 hw:0
[2018-11-28 23:28:38] Total cnv8: 3.142kh/s, avg 2.094kh/s, pool 1.919kh/s a:178 r:0 hw:0
...
[2018-11-29 08:59:08] Stats Uptime: 0 days, 09:46:00
[2018-11-29 08:59:08] GPU 0 [47C, fan 19%] cnv8: 518.1 h/s, avg 520.0 h/s, pool 499.7 h/s a:1757 r:0 hw:0
[2018-11-29 08:59:08] GPU 1 [56C, fan 19%] cnv8: 515.2 h/s, avg 490.7 h/s, pool 477.8 h/s a:1680 r:0 hw:0
[2018-11-29 08:59:08] GPU 2 [48C, fan 19%] cnv8: 835.0 h/s, avg 429.7 h/s, pool 427.2 h/s a:1502 r:0 hw:0
[2018-11-29 08:59:08] GPU 3 [43C, fan 0%] cnv8: 937.9 h/s, avg 458.4 h/s, pool 441.2 h/s a:1551 r:0 hw:0
[2018-11-29 08:59:08] Total cnv8: 2.806kh/s, avg 1.899kh/s, pool 1.846kh/s a:6490 r:0 hw:0
Every time strictly after 15min uptime current hashrate becomes too high on all or almost all gpus (the can be different on other rig start). Avg begin to drop. Reportet pool hashrate aim to avg. I've tried to reduce intensity to 3+2, L3+2, reduce overclock to extremely low - 1100/1850 on baffins and 1180/1950 on lexa but problem occures again at same uptime 15min.
November 29, 2018, 06:17:01 PM
What's the command for fan control? (say I want it to set it to 50% all the time)
thanks
thanks
November 28, 2018, 07:56:04 AM
awesome! can you disable or change the watchdog?
November 27, 2018, 11:36:49 PM
Team Red Miner v0.3.8 released
https://github.com/todxx/teamredminer/releases
Changes in v0.3.8
You can now use this miner to mine phi2 coins other than LUX!
Thank you for fixing. https://github.com/todxx/teamredminer/releases
Changes in v0.3.8
- Added support for fan speed and temperatures.
- Added watchdog function for gpu init stuck, dead gpu, over-temp gpu, and non-responding pool.
- Added new optional 'L' config prefix for low-end cards like lexa/baffin for a 10+% speed-up on some cards
- Added an option for writing out a log file.
- Added cycling through multi-entry dns records when connecting to pools.
- Added a pool-connect timeout.
- Added measurement and displaying of pool response times.
- Added support for 80-byte headers for Phi2 algo (for non-LUX coins).
- Slightly tuned the '+' mode for polaris, some GPUs will show slight performance increase.
- Fixed bug with API interface occasionally getting stuck.
You can now use this miner to mine phi2 coins other than LUX!
November 27, 2018, 07:02:22 PM
Good job again Todxx and Kerney666.
Your Phi2 miner is a whopping 50% faster than FancyIX's attempt at forking Sgminer.
What also needs to be said is that this miner is rock solid. At the same clocks, Sgminer will die a thousand deaths. This just runs. Beautiful.
Your Phi2 miner is a whopping 50% faster than FancyIX's attempt at forking Sgminer.
What also needs to be said is that this miner is rock solid. At the same clocks, Sgminer will die a thousand deaths. This just runs. Beautiful.
Thanks dragonmike! It's always nice to know one's work is appreciated
I personally hope you'll finally release a good x16r miner for AMD. What's out there really doesn't do AMD justice currently.
When a Vega56 only gets 2/3 of the hashrate of a GTX 1080 at 50% more power, you know there's... potential.
November 27, 2018, 06:37:45 PM
Good job again Todxx and Kerney666.
Your Phi2 miner is a whopping 50% faster than FancyIX's attempt at forking Sgminer.
What also needs to be said is that this miner is rock solid. At the same clocks, Sgminer will die a thousand deaths. This just runs. Beautiful.
Your Phi2 miner is a whopping 50% faster than FancyIX's attempt at forking Sgminer.
What also needs to be said is that this miner is rock solid. At the same clocks, Sgminer will die a thousand deaths. This just runs. Beautiful.
Thanks dragonmike! It's always nice to know one's work is appreciated
November 27, 2018, 06:36:17 PM
Will you guys support zcoin MTP algo?
Hey Mashy81,
We will not be supporting MTP, at least initially. Due to the way the Zcoin team decided to setup the MTP proofs, it has created a huge mess for the stratum protocol.
It will take a lot of effort for us to support the new stratum protocol, and we have other higher priority items on our todo list right now.
November 27, 2018, 05:50:59 PM
Good job again Todxx and Kerney666.
Your Phi2 miner is a whopping 50% faster than FancyIX's attempt at forking Sgminer.
What also needs to be said is that this miner is rock solid. At the same clocks, Sgminer will die a thousand deaths. This just runs. Beautiful.
Your Phi2 miner is a whopping 50% faster than FancyIX's attempt at forking Sgminer.
What also needs to be said is that this miner is rock solid. At the same clocks, Sgminer will die a thousand deaths. This just runs. Beautiful.
November 27, 2018, 05:42:07 PM
Team Red Miner v0.3.8 released
https://github.com/todxx/teamredminer/releases
Changes in v0.3.8
You can now use this miner to mine phi2 coins other than LUX!
https://github.com/todxx/teamredminer/releases
Changes in v0.3.8
- Added support for fan speed and temperatures.
- Added watchdog function for gpu init stuck, dead gpu, over-temp gpu, and non-responding pool.
- Added new optional 'L' config prefix for low-end cards like lexa/baffin for a 10+% speed-up on some cards
- Added an option for writing out a log file.
- Added cycling through multi-entry dns records when connecting to pools.
- Added a pool-connect timeout.
- Added measurement and displaying of pool response times.
- Added support for 80-byte headers for Phi2 algo (for non-LUX coins).
- Slightly tuned the '+' mode for polaris, some GPUs will show slight performance increase.
- Fixed bug with API interface occasionally getting stuck.
You can now use this miner to mine phi2 coins other than LUX!
November 26, 2018, 03:37:07 PM
Will you guys support zcoin MTP algo?
November 21, 2018, 12:49:45 AM
Hi, here is temredminer 0.17.0 output: GPU 0 - cnv8: 680.9 h/s, avg 680.0 h/s, pool 779.6 h/s a:69 r:0 hw:2
card rx470 with some moddede bios, intensity 4-4
So hw:2 its good/bad and what it means? Its hradware errors? Need to downclock?
Thank you.
card rx470 with some moddede bios, intensity 4-4
So hw:2 its good/bad and what it means? Its hradware errors? Need to downclock?
Thank you.
Hi! Those would be found shares rejected by cpu verification, so yes, hardware errors. Tweaking clocks would be the advice.
Also, 680 h/s on a 470 is quite low? Even if it's a 4GB driving monitors, have you tried configs such as 7+7, 6+6?
I thought before there was a problem in the monitor and connected the monitor to another card, but now the afterburner does not allow to change the frequensies, and configs more agressive than 4-4 still crashes my driver. Ill try to downklock card and report than.
P.S. Why afterburner disable the frequency control, when i add gt220 card?
It could def be a Win 7 problem, we don’t test/support Win 7, it seems to be working for some though.
At least the issue with hw errors was resolved:GPU 0 - cnv8: 670.2 h/s, avg 669.9 h/s, pool 619.3 h/s a:570 r:0 hw:0. Want to try this miner with linux, than report.
November 20, 2018, 11:42:13 AM
Hey guys,
My RX580 rig works perfect, however i also got a few Hawaii cards (R290 tri-x) and this cards are not supported.
Are u guys on it or will u guys ignore this versions from AMD?
My RX580 rig works perfect, however i also got a few Hawaii cards (R290 tri-x) and this cards are not supported.
Are u guys on it or will u guys ignore this versions from AMD?
November 20, 2018, 09:55:20 AM
Hi, here is temredminer 0.17.0 output: GPU 0 - cnv8: 680.9 h/s, avg 680.0 h/s, pool 779.6 h/s a:69 r:0 hw:2
card rx470 with some moddede bios, intensity 4-4
So hw:2 its good/bad and what it means? Its hradware errors? Need to downclock?
Thank you.
card rx470 with some moddede bios, intensity 4-4
So hw:2 its good/bad and what it means? Its hradware errors? Need to downclock?
Thank you.
Hi! Those would be found shares rejected by cpu verification, so yes, hardware errors. Tweaking clocks would be the advice.
Also, 680 h/s on a 470 is quite low? Even if it's a 4GB driving monitors, have you tried configs such as 7+7, 6+6?
I thought before there was a problem in the monitor and connected the monitor to another card, but now the afterburner does not allow to change the frequensies, and configs more agressive than 4-4 still crashes my driver. Ill try to downklock card and report than.
P.S. Why afterburner disable the frequency control, when i add gt220 card?
It could def be a Win 7 problem, we don’t test/support Win 7, it seems to be working for some though.
November 20, 2018, 02:24:31 AM
Hi, here is temredminer 0.17.0 output: GPU 0 - cnv8: 680.9 h/s, avg 680.0 h/s, pool 779.6 h/s a:69 r:0 hw:2
card rx470 with some moddede bios, intensity 4-4
So hw:2 its good/bad and what it means? Its hradware errors? Need to downclock?
Thank you.
card rx470 with some moddede bios, intensity 4-4
So hw:2 its good/bad and what it means? Its hradware errors? Need to downclock?
Thank you.
Hi! Those would be found shares rejected by cpu verification, so yes, hardware errors. Tweaking clocks would be the advice.
Also, 680 h/s on a 470 is quite low? Even if it's a 4GB driving monitors, have you tried configs such as 7+7, 6+6?
I thought before there was a problem in the monitor and connected the monitor to another card, but now the afterburner does not allow to change the frequensies, and configs more agressive than 4-4 still crashes my driver. Ill try to downklock card and report than.
P.S. Why afterburner disable the frequency control, when i add gt220 card?
November 18, 2018, 08:48:35 AM
My 56 vegas hit 2000H on CV8
But the vega64s hashing 2000 too. I triey many combo 16+14, 16-14 etc
Anybody has a solution?
But the vega64s hashing 2000 too. I triey many combo 16+14, 16-14 etc
Anybody has a solution?
Hi Turcy086! I moved your question to the CN thread, see https://bitcointalksearch.org/topic/m.48014534.
November 18, 2018, 07:18:07 AM
TeamRedMiner v0.3.7 added to https://www.minermonitoring.com/ https://www.ethmonitoring.com/ Join our discord https://discord.gg/aGGaeqq
also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark
also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark
November 18, 2018, 06:54:59 AM
My 56 vegas hit 2000H on CV8
But the vega64s hashing 2000 too. I triey many combo 16+14, 16-14 etc
Anybody has a solution?
But the vega64s hashing 2000 too. I triey many combo 16+14, 16-14 etc
Anybody has a solution?
Jump to: