Version 6.5.8 (Development preview of 6.6)
FPGA mining
- Blackminer F1 FPGA supported with temperature display
GPU mining
- Mining software definitions can be updated without upgrading the Awesome Miner or Remote Agent version
- GPU clocking groups can use exact GPU name mapping
- Added algorithm Lyra2z330
User interface
- Added additional coin images
- Description for Windows Uptime changed to System Uptime
Mining software
- CpuMiner-Opt 3.9.4
- SrbMiner 1.9.0
- Improved detection of when 'allcoins 1' needs to be added to the Claymore Ethereum miner command line
Corrections
- Correction to a timing issue where a miner group in Awesome Miner could be lost
- Correction to user defined mining software customization for Remote Agent on Linux
To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.
Direct download links if needed:
https://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
https://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 156. (Read 703563 times)
June 26, 2019, 08:16:34 AM
June 25, 2019, 10:59:41 AM
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it?
Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon.Code:
6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
Unfortunately this still seems to be an issue in 6.5.7.
I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters.
I'm happy to provide any additional info you might need to track this down.
I'm away from my rigs for a day or so, but I will run through some more tests as soon as I can and post the results.
June 25, 2019, 06:02:56 AM
like they said, deactivate the windows update and configure for mining.
you can't blame AM because of that, they are not windows developer and they are not going to create something to do "auto configure" just with 1 click.
Thanks for your comments. You are correct that Awesome Miner cannot do everything to secure that the mining environment is in good shape - but I'm actually open to suggestions about what Awesome Miner could do better in the future. It may not be a one-click that solves everything, but there might still be something to improve.you can't blame AM because of that, they are not windows developer and they are not going to create something to do "auto configure" just with 1 click.
A feature to deploy some good configuration baseline for Windows could be a good feature to add in the future, where Awesome Miner can help you to disable Windows update, increase virtual memory if too low and so on.
June 25, 2019, 05:55:06 AM
I've heard about the forecasts of the warm weather in south Europe.
I do know that you have lowered your OC already because of the warm weather - can you please see if the people in your Telegram group consider that as well? It's quite often users start to experience GPU mining stability issues more frequently in May-June - I get those reports every year.
Two things you could try in Options dialog, Mining Settings:
1) Enable "Use Ctrl+C" as some mining software behave better with the enabled.
2) Consider increasing "Pause when profit switcher starts mining" and "Wait for process stop before terminating" a bit.
Point one that uses CTROL + C, where I activate that in AM, because I do not understand it in any other way. DOndende have to put it?I do know that you have lowered your OC already because of the warm weather - can you please see if the people in your Telegram group consider that as well? It's quite often users start to experience GPU mining stability issues more frequently in May-June - I get those reports every year.
Two things you could try in Options dialog, Mining Settings:
1) Enable "Use Ctrl+C" as some mining software behave better with the enabled.
2) Consider increasing "Pause when profit switcher starts mining" and "Wait for process stop before terminating" a bit.
Have you been able to narrow down the issue with some troubleshooting - for example if you take one of your systems and only run it with one specific mining software and a single algorithm with no customization at all. Do you still get the same stability problems in that case?
June 25, 2019, 05:50:00 AM
Bug - the gpu oc profiles by name , do not differentiate between say a 1660 and a 1660 Ti
Even throug the names are slightly different only the 1660 profile is applied
The name matching is based on partial matching right now. If you define to apply a profile to "1660" it will apply this to a GPU with the name "Geforce GTX 1660" although you didn't have to type the exact name.Even throug the names are slightly different only the 1660 profile is applied
The drawback is that it would also match "1660 Ti" as you point out, because of the partial matching. There will have to be a new matching rule like "GPU Name (exact)" for this scenario. I will look into that.
June 25, 2019, 05:27:53 AM
I've noticed an issue with User-Defined Managed Software for CPU/GPU as it relates to the algorithm/-a parameter. See below for a log from a Linux agent that shows the command line is missing the "-a m7m" parameter, and therefore fails. Has anyone else seen this and have an idea how to address it?
Thanks for the details. I was able to reproduce and correct the issue. It was an issue introduced in the latest development release. There will be a new release available soon.Code:
6/20/19 7:51:24 PM.645 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] : Adding pool: stratum+tcp://m7m.mine.ahashpool.com:6033
6/20/19 7:51:24 PM.645 [014] [S]Set execution permission for: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.651 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] Properties: (WindowMode: ConsoleFormat, EngineType: 20, IsProfitMiner: False)
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030
6/20/19 7:51:24 PM.652 [014] [S][ManagedMiner#89 - HMDNoah1 CPU] ====================================================================================================
6/20/19 7:51:24 PM.757 [014] [S]Set Diagnostics executable: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer
6/20/19 7:51:24 PM.758 [014] [S]Creating start script: /root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/awesome-start.sh, Command:
stdbuf -o L "/root/AwesomeMinerService/cpuminer-opt-3.9.4-linux_3/cpuminer" -o stratum+tcp://m7m.mine.ahashpool.com:6033 -u [redacted] -p c=BTC --api-remote -b 0.0.0.0:4030 &> "/root/AwesomeMinerService/diag.txt"
Unfortunately this still seems to be an issue in 6.5.7.
I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters.
I'm happy to provide any additional info you might need to track this down.
June 25, 2019, 05:22:18 AM
Thanks for the feedback.
It's correct that Linux on Remote Agent doesn't include all features and all mining software. For mining software it's about 20 of them supported and the Claymore miners should work fine.
Can you please let me know the main features you are missing? The goal is of course to continue improving Remote Agent on Linux so all feedback is of course welcome. Thanks!
Hi Patrik.
Thank you for paying attention to me.
I confirm that none of the Caymore`s miners work by default.
Only dances with a tambourine forced Dual miner to work and then only when I registered him completely the launch line in the profile.
With the rest so far did not suffer.
On the tab GPU there is no control of energy consumption.
Its utilites report from my test rig
Code:
========================ROCm System Management Interface========================
================================================================================
GPU Temp AvgPwr SCLK MCLK Fan Perf PwrCap SCLK OD MCLK OD GPU%
0 67.0c 80.0W 1140Mhz 2150Mhz 100.0% manual N/A 0% 0% N/A
1 64.0c 83.0W 1140Mhz 2150Mhz 80.0% manual N/A 0% 0% N/A
2 66.0c 82.0W 1140Mhz 2150Mhz 60.0% manual N/A 0% 0% N/A
3 67.0c 88.0W 1140Mhz 2150Mhz 61.96% manual N/A 0% 0% N/A
4 64.0c 80.0W 1140Mhz 2150Mhz 80.0% manual N/A 0% 0% N/A
5 65.0c 84.0W 1140Mhz 2150Mhz 100.0% manual N/A 0% 0% N/A
6 66.0c 77.0W 1140Mhz 2150Mhz 61.96% manual N/A 0% 0% N/A
================================================================================
==============================End of ROCm SMI Log ==============================
I will be glad to provide all possible assistance in testing the Linux Agent, if necessary.
Sincerely, Vladimir.
p.s. I do not see the possibility to insert screenshots.
1) Could you please send me your Remote Agent log file (toolbar Tools -> Log File -> Remote Agent) for the Linux system where you don't see the power usage.
2) Please also use the Diagnostics button to start the Claymore miner and share the output with me.
Thanks!
June 25, 2019, 04:27:54 AM
I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?
Windows 10 Rig
5x 1070's
Windows 10 Rig
5x 1070's
reduce overclocking and check risers
clean the oxide film from the contacts of the video card and risers
I already answer you. It's not the OC, nor are the risers. It is the damn windows and its updates, something has to improve in AM to control this.
You can not undermine and indicate "miner offline" and reboot rig. It also happens directly by mining, PLASH and reboot if notice. And this already reducing the OC a lot.
Insluso some miners of abnormal form occupy 100% of CPU, so much that it makes the system fail. I have seen several times already Intelibreeeze the remote AM program, hanging using more than 30% of CPU (depends on the model, this almost i3)
It's not me, it's not the other guy, there are many of us who are reporting these errors and it's not my first summer with AM undermining, I know what I'm talking about. Low OC, a lot of ventilation, air extractors, direct air to the platforms, but they can be at 50 degrees and suddenly reboot for no reason or stay in offline miner and restart by the rule.
like they said, deactivate the windows update and configure for mining.
you can't blame AM because of that, they are not windows developer and they are not going to create something to do "auto configure" just with 1 click.
here you have a tutorial...
https://www.youtube.com/watch?v=7Zsv-3QDzJQ
by the way, there are many possibilities for the crash, reboot, stopped, etc. I had that problem too....
June 25, 2019, 03:28:00 AM
I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?
Windows 10 Rig
5x 1070's
Windows 10 Rig
5x 1070's
reduce overclocking and check risers
clean the oxide film from the contacts of the video card and risers
I already answer you. It's not the OC, nor are the risers. It is the damn windows and its updates, something has to improve in AM to control this.
You can not undermine and indicate "miner offline" and reboot rig. It also happens directly by mining, PLASH and reboot if notice. And this already reducing the OC a lot.
Insluso some miners of abnormal form occupy 100% of CPU, so much that it makes the system fail. I have seen several times already Intelibreeeze the remote AM program, hanging using more than 30% of CPU (depends on the model, this almost i3)
It's not me, it's not the other guy, there are many of us who are reporting these errors and it's not my first summer with AM undermining, I know what I'm talking about. Low OC, a lot of ventilation, air extractors, direct air to the platforms, but they can be at 50 degrees and suddenly reboot for no reason or stay in offline miner and restart by the rule.
i have over 10 rigs on Win10 and for several years now I have not received updates from Microsoft on any of the rigs.
what am I doing wrong?
June 25, 2019, 01:13:27 AM
I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?
Windows 10 Rig
5x 1070's
Windows 10 Rig
5x 1070's
reduce overclocking and check risers
clean the oxide film from the contacts of the video card and risers
I already answer you. It's not the OC, nor are the risers. It is the damn windows and its updates, something has to improve in AM to control this.
You can not undermine and indicate "miner offline" and reboot rig. It also happens directly by mining, PLASH and reboot if notice. And this already reducing the OC a lot.
Insluso some miners of abnormal form occupy 100% of CPU, so much that it makes the system fail. I have seen several times already Intelibreeeze the remote AM program, hanging using more than 30% of CPU (depends on the model, this almost i3)
It's not me, it's not the other guy, there are many of us who are reporting these errors and it's not my first summer with AM undermining, I know what I'm talking about. Low OC, a lot of ventilation, air extractors, direct air to the platforms, but they can be at 50 degrees and suddenly reboot for no reason or stay in offline miner and restart by the rule.
Then deactivate windows updates
June 24, 2019, 10:48:39 PM
I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?
Windows 10 Rig
5x 1070's
Windows 10 Rig
5x 1070's
reduce overclocking and check risers
clean the oxide film from the contacts of the video card and risers
I already answer you. It's not the OC, nor are the risers. It is the damn windows and its updates, something has to improve in AM to control this.
You can not undermine and indicate "miner offline" and reboot rig. It also happens directly by mining, PLASH and reboot if notice. And this already reducing the OC a lot.
Insluso some miners of abnormal form occupy 100% of CPU, so much that it makes the system fail. I have seen several times already Intelibreeeze the remote AM program, hanging using more than 30% of CPU (depends on the model, this almost i3)
It's not me, it's not the other guy, there are many of us who are reporting these errors and it's not my first summer with AM undermining, I know what I'm talking about. Low OC, a lot of ventilation, air extractors, direct air to the platforms, but they can be at 50 degrees and suddenly reboot for no reason or stay in offline miner and restart by the rule.
June 24, 2019, 10:39:56 PM
Help me , very hot day 
Apart from dobe OC, both I and most of the people in my telegram have stability problems with the RIGS, are frequently restarted on Offline or simply when the currency changes, depending on what the miners will be, they stay offline and by a rule reboot miner ..... I hardly use the auto profit to avoid currency changes, and just the auto profit is one of the great qualities of AM.
I still think it's a Windows problem, but we'll have to adapt what needs to be fixed.
I've heard about the forecasts of the warm weather in south Europe. Apart from dobe OC, both I and most of the people in my telegram have stability problems with the RIGS, are frequently restarted on Offline or simply when the currency changes, depending on what the miners will be, they stay offline and by a rule reboot miner ..... I hardly use the auto profit to avoid currency changes, and just the auto profit is one of the great qualities of AM.
I still think it's a Windows problem, but we'll have to adapt what needs to be fixed.
I do know that you have lowered your OC already because of the warm weather - can you please see if the people in your Telegram group consider that as well? It's quite often users start to experience GPU mining stability issues more frequently in May-June - I get those reports every year.
Two things you could try in Options dialog, Mining Settings:
1) Enable "Use Ctrl+C" as some mining software behave better with the enabled.
2) Consider increasing "Pause when profit switcher starts mining" and "Wait for process stop before terminating" a bit.
Obviously everything he suggests we have done. and Obviously we have to have a low OC that can withstand the hot hours, but the machines lower temperatures a lot at night and can
take advantage of those cirscuntancias.
You have already seen the temperature graphs the oscillations are 20 degrees less.
Point one that uses CTROL + C, where I activate that in AM, because I do not understand it in any other way. DOndende have to put it?
The pauses are long, since it stops until you mine again, it passes more than 1 minute for the delays to the change of OC, waiting time before mining etc ... We give time for the clocks to return to their place. We already know that high OC = problems, but that is not the case right now. And at a lower temperature lower OC, less mv, but being able to mine 15% more at night, because it seemed a waste not to do it well. PAra that I want now at night the cards to 58 degrees ??, that if, of day they are between 68-76 Degrees, something that I consider acceptable.
We have an OC of summer and another of winter, but we do not have a double OC for these changes brucos that we have in summer in the center of Spain.
June 24, 2019, 06:38:51 PM
I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?
Windows 10 Rig
5x 1070's
Windows 10 Rig
5x 1070's
Which 1070's are you using?
I have 8 Founders Edition cards mining ETH.
Settings are:
Core +60
Memory +675
Power Limit 75
Temperature Limit 80
Fan speed 85%
Core Voltage Limit 800mv
I bring in ~31MH/s at 100W each and it's pretty solid with Claymore.
Perimeters: -strap 4 -sintensity 40
I'm always tinkering with it though but these settings work pretty well for me.
June 24, 2019, 05:28:46 PM
I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?
Windows 10 Rig
5x 1070's
Windows 10 Rig
5x 1070's
reduce overclocking and check risers
clean the oxide film from the contacts of the video card and risers
June 24, 2019, 03:57:49 PM
I've been using AwesomeMiner for a while and haven't had many issues but now I'm getting frequent crashes to the point where the PC just restarts. I'm having a hard time narrowing down which algorithms it's having trouble with. Is there an ideal place I should start to dig or does anyone have any advice?
Windows 10 Rig
5x 1070's
Windows 10 Rig
5x 1070's
June 24, 2019, 03:10:22 PM
Lyra2z330 Algo....
I can include that one. Is there anything in addition to CpuMinerOpt you can use for mining it?Sadly, it looks like it's only CpuMinerOpt
Thanks for adding it
June 24, 2019, 10:53:24 AM
Bug - the gpu oc profiles by name , do not differentiate between say a 1660 and a 1660 Ti
Even throug the names are slightly different only the 1660 profile is applied
Even throug the names are slightly different only the 1660 profile is applied
June 24, 2019, 09:30:15 AM
I have a Linux agent and was able to run Claymore's dual ETH miner using AM's default settings. Although it does appear that the GPU clocking profile is being ignored.
how time used LA?
in new installation not work
epools is clear, manual correction epools not work too - after start LA clear file recreated
I can't use the dev release so as not to disrupt the rest of the rigs
June 24, 2019, 09:24:14 AM
I have a Linux agent and was able to run Claymore's dual ETH miner using AM's default settings. Although it does appear that the GPU clocking profile is being ignored.
how time used LA?
in new installation not work
epools is clear, manual correction epools not work too - after start LA clear file recreated
June 24, 2019, 09:13:58 AM
I have a Linux agent and was able to run Claymore's dual ETH miner using AM's default settings. Although it does appear that the GPU clocking profile is being ignored.
how time used LA?
in new installation not work
epools is clear, manual correction epools not work too - after start LA clear file recreated
Jump to: