Hi, Patrike!
After the last update, the api srbminer 4.7 stopped working. The srbminer 5.01 version does not start, it also looks like something with the API.
Yes and srbminer 5.0.1 works perfect. some things changed, please look in the srbminer thread. Set --cpu-threads in commandline, it must be specify. This is clear. Temperature, hashray, power is not reflected in awesome miner window. Can you please send me the API report (Toolbar: Tools - API Report) for the miner when it's running SrbMiner, but not showing hashrate/temperature? Thanks! The API format changed in SrbMiner 0.5.x and recent Awesome Miner versions have been updated to the new API format. It could however be some case where it isn't working correctly, so I'm more than happy to look into your API Report and see if there is a problem. |
|
|
|
Hi Patrik
The benchmark of Bminer ver. 16.3 deliver a wrong hashrate data (algo CuckaToo32).
I have tested a rig of 6x 1080ti on the 20 min. run on Nicehash. Benchmark show 4.34 H/s, but in reality if i start normal mining on the Nicehash, hashrate is only 3.7 H/s. AM ver. 8.0.1 Check please. Regards
Upd. Now show Bminer normal, like in benchmark. Simple Bminer have very big fluctration in hashrate data on Nicehahsh.
If you run a 20 minute benchmark, Awesome Miner will ignore the first 6 minutes as there are larger variations in the beginning and it also takes some time before all cards are up to speed. For the last 14 minutes, Awesome Miner will measure the hashrate every 5 seconds and calculate an average value. This average value is what will be the benchmark result. As you point out, there can be some variations in the hashrate on certain combinations of pools and algorithms. |
|
|
|
What is everyone running as the OS when using the Linux remote agent?
Ubuntu 20.04 desktop edition or server edition or something completely different?
I'd like to keep my OS install as lean as possible but wasn't sure of it is a pain to install the graphics drivers on the server edition (or if it is even supported).
EDIT: I went ahead and installed 20.04 on a test rig with a single 1070. Added the latest Nvidia driver and screen (not part of base desktop install) and of course the remote agent.
Added the new rig to AM and created a GPU Clocking Profile.
Started mining, which is working fine, but the GPU Clocking Profile is being ignored.
Are GPU clocking profiles not supported on Ubuntu?
EDIT2: Will AM automatically start the ETH pill on rigs with 1080/1080Ti GPUs?
GPU clocking profiles works on Linux but must be re-created if they initially was created on Windows. The clocking properties on are not exactly the same on Windows and Linux. EthPill will unfortunately not be loaded automatically. |
|
|
|
Hey Lolliedieb, Jumping in here.
Just to clarify the curiosity about lolMiner configuration:
Pre 1.0 lolMiner had only one parameter to configure the algorithm - this was --coin and did all the needed stuff in one command: selecting right algo + right personalization plus right stratum.
Issue some users of mine had was when a new coin was added with the same algo or one project changed the personalization parameter. Then the shortcut was not right.
Therefore lolMiner 1.0 and newer added a new parameter --algo (or short -a) that can select the algorithm, while --pers takes the personalization for Equihash based algos. So one old parameter was replaced by two new, but its now cleaner separated and when new projects with same PoW come along they should work out of the box.
--coin is still present in lolMiner 1.0 and up, but only for special functions like algorithm switchers and some often used presets. The standard way for future use and additions should be using --algo and maybe - for Equihash - --pers. It might be that some algos in future will be added that need a 3rd parameter to select the right stratum, but that did not happen yet.
I have the feeling that --algo + --pers is much closer to what other miners do and so hope using this pattern clears most of the configuration confusion.
Thanks for clarifying the lolMiner configuration side of things  The issue I'm having is that with the current Awesome Miner setup, EQUI144_5, ZEL, and EQUI192_7 do not get the --pers parameter added to the generated comandline, (and - for people who are reading along - for those algo's --pers is required, not optional), and I don't know how to setup AM so that it will add it along with the correct argument whilst using profit switching. I don't even know if it is an AM issue, an EBKAC issue, or a combination of both, (which in itself is an EBKAC issue  ), and my google-fu is poo, so I posted the steps I took to find out why I couldn't benchmark those algo's through AM in the hope that someone would point me in the right direction. Have fun! =8^) In the Properties of your Pool in Awesome Miner, where you specify URL and worker name, you will also find the field "Personalization string". If you fill in "BgoldPoW" here, Awesome Miner will add "--pers BgoldPoW" when you start lolMiner. If this doesn't work, can you please send me a few screenshots? Thanks! |
|
|
|
Jumping in here.
Just to clarify the curiosity about lolMiner configuration:
Pre 1.0 lolMiner had only one parameter to configure the algorithm - this was --coin and did all the needed stuff in one command: selecting right algo + right personalization plus right stratum.
Issue some users of mine had was when a new coin was added with the same algo or one project changed the personalization parameter. Then the shortcut was not right.
Therefore lolMiner 1.0 and newer added a new parameter --algo (or short -a) that can select the algorithm, while --pers takes the personalization for Equihash based algos. So one old parameter was replaced by two new, but its now cleaner separated and when new projects with same PoW come along they should work out of the box.
--coin is still present in lolMiner 1.0 and up, but only for special functions like algorithm switchers and some often used presets. The standard way for future use and additions should be using --algo and maybe - for Equihash - --pers. It might be that some algos in future will be added that need a 3rd parameter to select the right stratum, but that did not happen yet.
I have the feeling that --algo + --pers is much closer to what other miners do and so hope using this pattern clears most of the configuration confusion.
Thanks for the clarification. Awesome Miner recently moved from using --coin to use --algo instead. I like the new concept with algorithms instead of coins so thanks for implementing it! Some other mining software supports "--pers auto" for Nicehash and similar profit switching pools. Is there a similar concept with lolMiner without having to use the older --coin concept? Thanks! |
|
|
|
I am having issues where the balance page does not add up correctly - for example, I have 4 litecoin addresses and it shows all 4 with their correct balances however - the total omits one of the balances and thus is wrong.
this issue comes and goes - and with different coins at different times - in an hour the above may be reflected correctly and my bitcoin balances will be wrong instead.
Thanks for the report. I've identified the scenario. If you have multiple addresses and the check for one of them fail, the failure will not be indicated in the user interface. The last balance for the address will still be displayed, but no longer part of the total. I will correct this in the next release, to indicate if there was a failure and let the total value assume the last known balance for the address that failed once. After this change, you will always see the total balance correctly. it seems to error now on anything with more than 2 addresses  Please go to the Options dialog, Balance section, Wallet balance. If you edit your Litecoin entry (or the one with a failure), select the first address in the list and click the Test button - is that working? Then move on to select the next and Test it. Are all working here? |
|
|
|
Thanks, i will do some tests here and report. BTW, what do you think in make a version of linux to boot from pendrive with the Awesome Miner client and AMD/NVIDEA drivers into? So everybody can burn the iso on a pendrive and run the miner... Thanks for the feedback. Yes, this is a feature request I get from time to time and it will probably be something for the future. I agree that it would make sense to have. |
|
|
|
Cant understand why profit statistic data for Cortex coin come and gone randomly? Anyone have the same issue? Is this statistic provider problem or AM problem? This happens only with Cortex. If this behavior come from provider, maybe is a good idea to store last recived statistic data and mark the outdated data with another color till new actual data will be recived from provider. Otherwise this made profit switching process crazy. I see that the mining of Cortex is profitable, but if AM has not recived data, AM switch my rigs to other coin.
Can you please go to the Options dialog, Statistics Provider section and see if "Keep coins even when no longer listed by provider" is enabled? If not, please check it to make sure Awesome Miner keeps coins from being removed. It was always checked. Check or uncheck not help. Just to confirm, the coin is always visible but sometimes the statistics shows all zeros or similar? If that's the case, it doesn't sound like a problem in Awesome Miner itself. This coin isn't part of the main listing at the provider, and the reason might be because of this instability. |
|
|
|
|
Awesome Miner version 8.0.1
GPU mining
- Improved output from Diagnostics
Features
- Heat map for display of temperatures and hashrates of miners. Heat maps can be created from a Miner Group in the Groups tab.
Mining software
- Miniz Miner 1.6v6
- TeamRedMiner 0.7.10
- SrbMiner Multi 0.5.1. This version is configured differently compared to older versions
- Lolminer implementation updated to use algorithm parameter instead of coin parameter
Corrections
- Correction to Fan Speed trigger for ASIC miners
- Correction to wallet balance total in case one of the wallets failed to update correctly
|
|
|
|
Hi Patrik,
I have a question. I have a few rigs left with nVidia GTX 1080 Ti's and MSI Afterburner and wanted them switching finally to the native overclocking like my other RTX rigs.
In Afterburner the first line is "Core Voltage (%)". I have set this on all cards to +100.
In AM in the GPU overclocking panel I cant find such "Core Voltage (%)". Its only the "Core voltage limit" in the lower advanced section, but I think this setting means I set the real numbers directly, like 1075 mV or 1040 mV or so.
In the GPU Clocking Profiles I can find the same "Core voltage limit (mV)" and "Core voltage boost (mV)". But none of them affect the first line in Afterburner. Is it possible somehow in AM to set that "Core Voltage (%)" to a number between +0 to +100? Without, the hashrate is lower and I really like that option.
Thanks for the answer!
Hi Joseph and thanks for your question. I'm not aware how to set Core Voltage (%) like MSI Afterburner. On nVidia 2000-series it isn't supported at all. On the 1000-series nVidia will enforce a number of limits the voltage anyway so you will never get 100% higher voltage even if configured. This is why the nVidia drivers mainly focus on the "Core voltage limit" these days. What kind of voltage behaviors do you get when you set it to +100% compared to 0% in MSI Afterburner? How does that compare to setting a voltage limit in Awesome Miner instead (at keep the setting in MSI Afterburner at 0%)? Hey Patrik, the Core Voltage (%) is just a very small boost, maybe 1% or so with +100. But I really like that option. It will boost the hashrate a little bit with just a bit higher voltage, but the GPU clock stays at the same number. If I just increase the voltage to the same value, the hashrate will be lower. So I have to increase the core clock too to match the higher hashrate. But if the card is already running with the highest clock, I cant increase it any higher. Thats my observations to that setting. Its nothing big here, but a few more cents per hour per card could be worth asking you But if its not possible to edit that setting with the native overclocking, it will be no problem. The native OC is one of the greatest tools inside AM. So keep up the great work! Hi Joseph, Thanks for the additional details. At the moment, I'm not aware of any ways to set this "Core Voltage %". I hope it will run fine anyway using the properties that is supported via Awesome Miner. The Native Overclocking is generally smoother than using the MSI Afterburner integration. |
|
|
|
Cant understand why profit statistic data for Cortex coin come and gone randomly? Anyone have the same issue? Is this statistic provider problem or AM problem? This happens only with Cortex. If this behavior come from provider, maybe is a good idea to store last recived statistic data and mark the outdated data with another color till new actual data will be recived from provider. Otherwise this made profit switching process crazy. I see that the mining of Cortex is profitable, but if AM has not recived data, AM switch my rigs to other coin.
Can you please go to the Options dialog, Statistics Provider section and see if "Keep coins even when no longer listed by provider" is enabled? If not, please check it to make sure Awesome Miner keeps coins from being removed. |
|
|
|
Hi Patrik,
I have a question. I have a few rigs left with nVidia GTX 1080 Ti's and MSI Afterburner and wanted them switching finally to the native overclocking like my other RTX rigs.
In Afterburner the first line is "Core Voltage (%)". I have set this on all cards to +100.
In AM in the GPU overclocking panel I cant find such "Core Voltage (%)". Its only the "Core voltage limit" in the lower advanced section, but I think this setting means I set the real numbers directly, like 1075 mV or 1040 mV or so.
In the GPU Clocking Profiles I can find the same "Core voltage limit (mV)" and "Core voltage boost (mV)". But none of them affect the first line in Afterburner. Is it possible somehow in AM to set that "Core Voltage (%)" to a number between +0 to +100? Without, the hashrate is lower and I really like that option.
Thanks for the answer!
Hi Joseph and thanks for your question. I'm not aware how to set Core Voltage (%) like MSI Afterburner. On nVidia 2000-series it isn't supported at all. On the 1000-series nVidia will enforce a number of limits the voltage anyway so you will never get 100% higher voltage even if configured. This is why the nVidia drivers mainly focus on the "Core voltage limit" these days. What kind of voltage behaviors do you get when you set it to +100% compared to 0% in MSI Afterburner? How does that compare to setting a voltage limit in Awesome Miner instead (at keep the setting in MSI Afterburner at 0%)? |
|
|
|
I am having issues where the balance page does not add up correctly - for example, I have 4 litecoin addresses and it shows all 4 with their correct balances however - the total omits one of the balances and thus is wrong.
this issue comes and goes - and with different coins at different times - in an hour the above may be reflected correctly and my bitcoin balances will be wrong instead.
Thanks for the report. I've identified the scenario. If you have multiple addresses and the check for one of them fail, the failure will not be indicated in the user interface. The last balance for the address will still be displayed, but no longer part of the total. I will correct this in the next release, to indicate if there was a failure and let the total value assume the last known balance for the address that failed once. After this change, you will always see the total balance correctly. |
|
|
|
One of my machines (specifically a 1070 eight card rig) keeps having an intermittent issue where AwesomeMiner says "interface offline" but the machine is still working fine. I uninstalled and re-installed the remote agent and the problem keeps occuring.
Any ideas?
No firewall / anti-virus / etc running. Windows 10 ver 2004.
I have three machines and only this one is having this particular issue.
Thanks!
Thanks for your question. "Interface offline" indicates one of the following: 1) The mining software you are running isn't responding with any monitoring information when requested by Awesome Miner. If this is the case, it's some bug in the mining software that cause the monitoring interface (API) to stop working 2) Awesome Miner do receive the monitoring information from the mining software, but Awesome Miner do something wrong and fail to process and display this information. When this problem happens, can you please select the miner and send me the API report via PM? You can generate the API report via the toolbar: Tools -> API Report. With this API Report I can verify if the mining software is responding with any monitoring details. Thanks! |
|
|
|
I can clearly see that you are running some pirate/hacked version of Awesome Miner that you didn't pay for. 1) Uninstall Awesome Miner and run an anti-virus check on your computer. Hopefully you don't have any viruses at this point 2) Remove your Awesome Miner configuration files. Remove all files in this folder: %appdata%\AwesomeMiner\ 3) Download and install Awesome Miner from our web site: https://www.awesomeminer.com/download4) Sign up for a subscription on our web site: https://www.awesomeminer.com/signup5) Once you have a valid subscription, I'm more than happy to help you. At this point, please create the setup again with your Ethermine pool. If it isn't working correctly, please start the miner with the Diagnostics button and share the output with me via the contact form below: https://www.awesomeminer.com/contactThanks! |
|
|
|
I've updated the mining software definitions for Miniz and TeamRedMiner. For SrbMiner, I've not yet updated because I need to review all changes - just like you pointed out. |
|
|
|
Initialize diagnostics (5000)
Starting Diagnostics (30s). Awesome Miner version: 8.0
OS: Microsoft Windows 10 Enterprise LTSC 2019 64-bit
AMD driver version: 20.4.2
AMD OpenCL Platform ID: 0
GPUs: RX 5700 XT
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Microsoft VC++ 2017 runtime installed: Yes
Microsoft VC++ 2019 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: TeamRedMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\Vladimir\AppData\Local\AwesomeMiner\teamredminer-v0.7.9-win_1\teamredminer-v0.7.9-win\teamredminer.exe -a ethash -o eu1.ethermine.org:4444 -u setof.5 -p x --api_listen=0.0.0.0:4028
====================================================================================================
Mining Engine Process started, PID: 1840
> Team Red Miner version 0.7.9
> Only stratum+tcp and stratum+ssl URLs are supported. Use option --help for usage.
====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed
Please open the Properties for your mining pool. Update the URL to: stratum+tcp://eu1.ethermine.org:4444 without [Awesome Miner] https://ibb.co/zJngbqkPlease try to put your wallet address in the field "Worker name" instead - leave the "Wallet address" field empty. It's a bit different from pool to pool if they expect the wallet to be provided as waller or worker. |
|
|
|
Hello, new here.
I'm having a very strange issue with AM. I am using a paid license for AM and my boss asked me to switch to mining ETH directly a couple of weeks ago. The easiest way to do what he requested was to recreate all of my miners as managed miners. To do this, I had used the network scan to bulk create all the miners based on any machines the manager found on the network running Awesome Miner Remote Agent. However, that plan was short lived and I was soon asked to switch it all back. After removing all of the managed miners I created, I am now having issues getting the original managed profit miners to start properly. I seem to only be able to get a few of them to start at a time and when I tell the ones that are stopped to start, it stops a bunch of the ones that were already mining and this just keeps going around in circles. I have recreated some of the miners but that has had little effect. I've RDP'd into each one and manually restarted the remote agent and I've rebooted each and every mining rig as well as the manager rig and nothing seems to be resolving this problem. Also. the Start and Stop buttons sometimes have absolutely no effect on the miner I actually have highlighted when I click the button. It is absolutely mind-boggling.
Does anyone have any suggestions?
Thanks.
EDIT: On closer examination, it appears that a some of these rigs that AM says are "stopped" are actually mining but it doesn't show up in AM.
If I could just get the Start/Stop buttons to stop appearing to control more than one rig at a time, that would be great.
EDIT AGAIN: It appears that simply changing the description of one of my miners can have a pretty big effect on the rest of the miners, making them stop or start. It makes no sense.
Please go to the Options dialog, Managed Hosts section. I think you have some duplicates of the hosts here (either duplicate IPs, or a combination of hostnames and IP addresses that points to the same Remote Agent). Can you please review this list and make sure there are no duplicate, and once you ensure this, please restart Awesome Miner once. For mining processes that already are running and no longer listed as Mining in Awesome Miner - please stop them manually before you proceed. If the above didn't resolve the problem, please also make sure you only have a single Awesome Miner instance running controlling your Remote Agents. |
|
|
|
Initialize diagnostics (5000)
Starting Diagnostics (30s). Awesome Miner version: 8.0
OS: Microsoft Windows 10 Enterprise LTSC 2019 64-bit
AMD driver version: 20.4.2
AMD OpenCL Platform ID: 0
GPUs: RX 5700 XT
Microsoft VC++ 2013 runtime installed: Yes
Microsoft VC++ 2015 runtime installed: Yes
Microsoft VC++ 2017 runtime installed: Yes
Microsoft VC++ 2019 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: TeamRedMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: False)
====================================================================================================
C:\Users\Vladimir\AppData\Local\AwesomeMiner\teamredminer-v0.7.9-win_1\teamredminer-v0.7.9-win\teamredminer.exe -a ethash -o eu1.ethermine.org:4444 -u setof.5 -p x --api_listen=0.0.0.0:4028
====================================================================================================
Mining Engine Process started, PID: 1840
> Team Red Miner version 0.7.9
> Only stratum+tcp and stratum+ssl URLs are supported. Use option --help for usage.
====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration or crashing software
Diagnostics completed
Please open the Properties for your mining pool. Update the URL to: stratum+tcp://eu1.ethermine.org:4444 |
|
|
|
|
Show Posts
