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!

I can include that one. Is there anything in addition to CpuMinerOpt you can use for mining it?

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.

For this user defined Managed Software you added for CpuMiner - have you configured it to have the compatibility mode "Full" with CpuMinerOpt?

I might have identified one more issue specific to the Remote Agent on Linux here, but only related to custom algorithm parameters.

Thanks - I will include this one

Please go to the Options dialog, Statistics Provider section, and define a Minimum Exchange Volume of for example 0.01 BTC. This will remove exchanges with low volume that typically gives unrealistic values.

There can of course be cases where some coin provider is reporting incorrect values for a specific coin even with this configuration made.

Version 6.5.7 (Development preview of 6.6)

 ASIC mining
  - Obelisk SC1 second generation supported with hashrate and temperature information
  - Improved configuration of Antminer API Access to make it easier to only allow connections from the computer where Awesome Miner is running
  - Automatic API Access configuration can be configured to only be applied for specific miners and miner groups
 User interface
  - Network scan improved to display more relevant information about the found miners
  - Network scan indicates the number of scanned IP addresses and the number of found miners
 Mining software
  - GMiner 1.47
  - WildRig Miner 0.17.8
 Corrections
  - Initialize GPU clocking information when Remote Agent on Linux is starting, to speed up clocking operations
  - Correction to algorithm command line argument for user defined mining software

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

Thanks - Yes, that would make sense.

It would however be even more flexible if you could point the Clocking Profile condition to a rule trigger you define. If you would define a Time Trigger that would be for 9 PM - 6 AM, you would have your night mode. You could then modify this rule to only trigger for certain groups of miners - and all of a sudden you have the flexibility to use time, miner and other conditions that are supported by the rules to decide which clocking profile to use. You could of couse have a single rule with a single time interval if you want to keep it simple - but you could have more than one rule if you want different and more complex ways of selecting Clocking Profiles - maybe with different time for different miner groups. Please note that the rules would only be used to decide if a trigger condition is met - they are not intended to execute any actions. Please note that this concept doesn't exist today - it's just an idea.

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.

The plan is to support this in the future.
Thanks!

I've received a few reports that some anti-virus software recently started to mark Awesome Miner as a threat as it's related to mining. It could be that your anti-virus software is blocking the installation.

Please note that these software point out that Awesome Miner is related to "coin mining", and this is the reason it's being marked as a threat. It's completely correct that Awesome Miner is related to "coin mining", but I would of course prefer if they didn't consider it a threat.

I will investigate the anti-virus part in more detail as well. I've worked with AVG / Avast a year ago where they have inspected Awesome Miner in details and white listed the software as safe. Microsoft has also marked it as safe in the past.

A good way to test if you can connect to a specific port on another computer is to use Microsoft PsPing.
https://docs.microsoft.com/en-us/sysinternals/downloads/psping

A standard ping command will only test if the computer replies, but psping will test if you have any application (Gminer in this case) that listen on a specific port.

psping -t 192.168.0.123:4040

Awesome Miner is currently not able to setup or display dual-mining for NBminer.

Is Gminer started with API enabled? The Gminer process should be started with the following command line, the port number can be anything but you need to use the same in Awesome Miner.
--api 4040

If you add an External Miner in Awesome Miner and select Gminer as software, you can specify the address like: 192.168.0.123:4040

Awesome Miner will automatically add all command line parameters needed for the profit switcher or for the specific pool you have configured. In this case you are adding your own command line parameters in addition to what Awesome Miner add, so you will end up having two parameters specifying the pool for example.

Some mining software might pick your parameters and it might work anyway, while others will not work at all or use the parameters that Awesome Miner defined. The issue is that you will most likely end up with duplicated command line arguments so it's really difficult to tell what will happen.

You can start the miner with the Diagnostics button in the toolbar to see the complete command line used to launch the mining software. You will see what Awesome Miner is adding here and you will also see the additional command line arguments you added. I think you will see many duplicates here, so my recommendation is still to let Awesome Miner setup most parameters for you and you only have to add anything extra you would like to see there.

Thanks for your detailed feedback.

First of all it's important to point out that Awesome Miner doesn't take any action to change the API access parameters on the ASIC by itself. As you know, almost all ASIC miners are by default running with Restricted API access, only allowing external applications to monitor the mining. This is also the case when you add your miners to Awesome Miner. As you pointed out in your Edit, Awesome Miner do however provide a feature where the user can make changes to the API access configuration.

For users that want to make operations on their ASIC miners via Awesome Miner, it's possible to use a feature called Configure API Access where the user can tell Awesome Miner to update the API access settings (api-allow). The user is given the option to select from where connections should be allowed. Either from any IP address or from a specific IP address (or range of IP addresses). There is also one single example on this screen - illustrating how to configure access for local network IP addresses only. In addition, there is a link to our web site where we give several examples of how to configure the API to only allow connections from specific IP addresses.

So from a user interface point of view, we try to suggest how the feature can be used. It's however true that the box selected by default is "Any IP address", and it's of course possible to discuss if that's a good decision. At the same time, given that we present a single example configuration, with limited IP access, and the user still decide to go for "Any IP address", it also indicates that some users just want things to work without having to spend 30 more seconds to make it more secure.

Keep in mind that it's surprisingly common that users leave their ASIC miners running with default web passwords, and I assume that for a user that is fine with running with default web passwords also would be fine with running with "Any IP Address" for the API. Just like Awesome Miner provides the feature to Configure API Access, it also provides features to update the web passwords for many miners to get a non-default password. The bottom line is that Awesome Miner is a toolbox of features that allows you to do operations that both can be used to make your miners more secure, but also less secure.

If you get virus on the Awesome Miner computer and you configured the Cgminer API to only allow privileged API access from this single IP address - you would still be in trouble. If you leave the Cgminer API with the default settings to only allow monitoring, you will be safe. This is also the default when you use Awesome Miner with an ASIC.

I do agree that Awesome Miner could be improved to be better at promoting secure configurations.

For the posts you are referring to it's also interesting to see that it happens to be Whatsminer ASIC. In the past I almost suspected that these ASICs were delivered miners with api-allow set to "W:0/0" from the factory, although I've never been able to confirm that. Also, the feature in Awesome Miner for setting API Access is only designed for Antminers.

Thanks!

Many thanks for the nice review of the new fan curve feature. It's actually a quite basic concept - looking at the individual device temperature and then adjust the fan of each GPU to match the curve you have defined.

Please note that when you enable the fan curve feature, you will no longer be able to adjust the fan in other ways.

The fan curve feature allows a 1% fan speed variation before it changes the fan speed - to reduce the number of fan adjustments. Otherwise you could have changes like 59, 60, 59, 60 very frequently.

If the curve indicates that the fan speed should be 60%, Awesome Miner will not do anything if the current fan speed is between 59% - 61%. It's considered good enough. However, if the current fan speed would be 58% or 62%, Awesome Miner will adjust it to 60%. So if you ever see that the fan speed is 1% different compared to what you expected - this is the reason.

The conditional Clocking Profiles, to support day/night clocking settings, is on the roadmap.

Version 6.5.6 (Development preview of 6.6)

 ASIC mining
  - Improved support for Avalon 921 with display of chip temperature and more details
 GPU mining
  - Improved mining software selection where older mining versions can be selected and the supported nVidia CUDA version can be detected
  - Global fan control using a fan/temperature curve with the native overclocking feature. Configurable in the Options dialog, GPU Settings section.
  - Remote Agent on Linux will report nVidia driver version and system memory usage
 Mining software
  - Claymore Ethereum Miner 14.7
  - Ethminer 0.18.0 rc0
  - TeamRedMiner 0.5.2
  - T-Rex Miner 0.12
  - WildRig Miner 0.17.6
 Corrections
  - Added missing Blake2b pools
  - Improved detection of xauthority environment variable on Linux for nVidia clocking


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

I think this is that you are running with Performance Mode enabled (see Options dialog, Advanced section). This one will force "compact list" when you start the application. When running with really large number of miners, the standard List mode is more heavy to update.

Hi and thanks for your question. If you want to specify mining software and pool yourself you should create a Managed Miner (not a Managed Profit Miner, which is for profit switching only). The general concept would be:
1) Create the Beam pool just like you did. You should however open the Properties for the pool again and go to the Advanced section and add the additional command line "--ssl 1".
2) Go to the Options dialog, Managed Miner section where you can add a new miner (use the Add button).
3) Specify Gminer as software for the Managed Miner and select your pool.
4) Use the GPU selection to select which GPU's to use for mining by clicking on the Configure button (this will generate the --devices command line automatically)

So the only command line parameter you manually had to enter here was the "--ssl 1" part, required by this specific pool.