Awesome Miner version 9.7.9 ( Development preview of 9.8 )
GPU mining
- Support for Intel Arc GPU on Windows. Intel GPUs will be listed with temperature, fan speed, clock speeds, voltage and power usage. Overclocking is not supported yet.
Features
- The built-in web interface can display Balance, Coins and Online Services pages.
User interface
- Changed device icon color for CPU mining to make room for a blue icon for Intel GPU mining
- Device icon colors explained in tooltip when selecting mining software
Mining software
- Gminer 3.17
- TeamBlackMIner 1.77
Hey patrike, the GPU selection is complete broken in this release. It doesn“t show me any GPU in the GPU selection. Thanks for your report. This will be corrected in an updated release tomorrow. It's related to a number of changes made to support the new Intel Arc GPUs. |
|
|
|
|
Awesome Miner version 9.7.9 ( Development preview of 9.8 )
GPU mining
- Support for Intel Arc GPU on Windows. Intel GPUs will be listed with temperature, fan speed, clock speeds, voltage and power usage. Overclocking is not supported yet.
Features
- The built-in web interface can display Balance, Coins and Online Services pages.
User interface
- Changed device icon color for CPU mining to make room for a blue icon for Intel GPU mining
- Device icon colors explained in tooltip when selecting mining software
Mining software
- Gminer 3.17
- TeamBlackMIner 1.77
|
|
|
|
Hey patrike could you add a way to manually reset performance statistics, like average?
Thanks for your request. Please let me know which ASIC and firmware you have in mind here, as I think there are only a few of them where this feature exists? I meant in AwesomeMiner, not on the miner itself. Under performance category in the miners tab. Unless that's directly linked to the miner firmware? It appears as though it's different from what is displayed on the miner itself. Would be useful if this was a 24/hr rolling average instead of since powerup as well. Also please add support for pause/resume mining for brains OS. The average hashrate in the Performance column is actually a value reported by the ASIC miners. To see the average hashrate as recorded by Awesome Miner, please open the Mining History for the miner. This way you can see the average hashrate for the period of time you want - for example the 24h average hashrate. Maybe a future improvement would be to let you show this 24h average in the miner list as well. This doesn't necessarily seem to be completely true, it doesn't match Braiins 24 hour hashrate for instance (it does eventually with enough time). It seems like Brains discards the warmup period and tuning periods after a certain amount of time where AM does not. The pause functionality for Brains seems to be broken as well. This needs to be done with the BOSminer stop/start command. 1) After mining for 24 hours - is the Braiins 24h avg hashrate different from the hashrate you see in the Mining History in Awesome Miner, when selecting 1 day? 2) The pause/resume feature for BraiinsOS has not yet been integrated with Awesome Miner. I can add it for the next release. 1. Yes, both for Braiins as well as Asicto 24 hour hashrates are off in terms of what average shows on AM vs the dashboard on the miner itself. It will gravitate close to the 24 hour hashrate on the miner within about a decimal, however this takes a decent chunk of time - sometimes a couple days. Hashrate averages over 6 and 12 hours are pretty far off. The instaneous reading also is off, however it might just be when AM is polling the data vs the dashboard. 2. Appreciate adding support! 3. Couple more things here, due to the nature of Braiins and how pause functionality works, it actually consumes much more power then it should. When you stop BOSminer it puts fans at 100% and doesn't completely power down the miner. This leads to around 80w of power usage. I've talked with the developers, but fixing this seems to be a very low priority for them. However, if you remove the pools or the pools are dead, it drops into a very low power mode and the dev fee doesn't work. It will use around 13w of power and of course is much quieter. I can do this myself through some custom rules finagling, but if you could add a bandaid checkbox where AM will 'pause' mining by removing all the pools, then readd them again when you 'unpause' it will save power. Then add a rule to pause/unpause through this functionality. 4. I looked through the rules section and can't find a way to pull in variables from outside of AM. I assume this can be done through a custom script, but looking at a text document for a variable after formatting. IE look for syntax and then variable after syntax in a file. Such as start/stop time. This could be as simple as 1 or 0 in the file. Hi and thanks for all feedback. 1) For the current hashrate it's like you point out - Awesome Miner will request the current hashrate at some point and the ASIC web interface will request the current hashrate at some point. These two requests will never be made at the exact same time so it's expected to be different. This is also the reason why any average values must be calculated over a longer period of time. The ASIC miners providing an average hashrate concept is keeping their own statistics and calculations for this and Awesome Miner will never be able to access it. Awesome Miner is instead sampling the hashrate, temperature and more to create its own statistics database. Over time this should be very close to what the ASIC miner reports. I will however review this to see if there are any issues or possible improvements to make here 3) Thanks for the update. I don't think we will be able to do this workaround in a good way in Awesome Miner as it's a bit risky to remove the pools. Awesome Miner could try to keep track of the removed pools for this miner and add them back later on, but what happens if a user is manually adding back some other pools? Or if the IP address of the miner changes? This workaround is too risky to implement from what I can see. 4) The Awesome Miner HTTP API can be used for this. To get a variable, see this example: https://www.awesomeminer.com/api#tag/Miners/paths/~1api~1miners~1%7Bid%7D~1variables~1%7Bname%7D/getTo update a variable, see this example: https://www.awesomeminer.com/api#tag/Miners/paths/~1api~1miners~1%7Bid%7D~1variables~1%7Bname%7D/postAny external application can make a HTTP GET or POST to Awesome Miner to get and update the variables for a miner. To call these API methods from the command line you can use the tool "curl" to perform the requests. |
|
|
|
|
Version 9.7.8 ( Development preview of 9.8 )
ASIC mining
- BraiinsOS firmware: Support for pause and resume mining. Support for reading all fan speed values.
Features
- New dashboard design with customization possibilities
- Added property filter for miner type (External or Managed)
Mining software
- Gminer 3.15
- Lolminer 1.64
- Miniz 2.0a
- Nanominer 3.7.6
- SrbMiner-Multi 1.1.3
- TeamBlackMiner 1.75
- TeamRedMiner 0.10.6
|
|
|
|
Hey patrike could you add a way to manually reset performance statistics, like average?
Thanks for your request. Please let me know which ASIC and firmware you have in mind here, as I think there are only a few of them where this feature exists? I meant in AwesomeMiner, not on the miner itself. Under performance category in the miners tab. Unless that's directly linked to the miner firmware? It appears as though it's different from what is displayed on the miner itself. Would be useful if this was a 24/hr rolling average instead of since powerup as well. Also please add support for pause/resume mining for brains OS. The average hashrate in the Performance column is actually a value reported by the ASIC miners. To see the average hashrate as recorded by Awesome Miner, please open the Mining History for the miner. This way you can see the average hashrate for the period of time you want - for example the 24h average hashrate. Maybe a future improvement would be to let you show this 24h average in the miner list as well. This doesn't necessarily seem to be completely true, it doesn't match Braiins 24 hour hashrate for instance (it does eventually with enough time). It seems like Brains discards the warmup period and tuning periods after a certain amount of time where AM does not. The pause functionality for Brains seems to be broken as well. This needs to be done with the BOSminer stop/start command. 1) After mining for 24 hours - is the Braiins 24h avg hashrate different from the hashrate you see in the Mining History in Awesome Miner, when selecting 1 day? 2) The pause/resume feature for BraiinsOS has not yet been integrated with Awesome Miner. I can add it for the next release. |
|
|
|
BZminer need dual mine option for Radiant and the GPU selection is missing. You can disable single gpu“s with --disable 0,1 and so on. I think it is possible to integrate it. And can you look into Rigelminer? I will only post his thread from bitcointalk. I think it is a legit miner, virustotal say 0 and some people in Kaspa Discord test this miner as well. https://bitcointalk.org/index.php?topic=5424675.0Thanks for the feedback. The dual mining option has been updated. I will review the GPU selection as well. It's inverted compared to how all other mining software are working. |
|
|
|
I'm alone with problem that Awesome miner does not show any statistics for kaspa (nicehash)? I did put my rig speed for kaspa in settings-algorithms, but still same. Settings in "online services" for nicehash-kaspa is fine, id 62 is fine, cant find what is wrong.
I'm not able to reproduce this issue. 1) On the Online Services tab, I do see Nicehash Kaspa listed. There is a value in the "BTC/GH/day" column and for the Profile Hashrate I've entered I do get a Revenue value based on this. 2) When I start mining, I do see a hashrate and a Revenue based on this Are all these showing zeros in your case or are there any of these values that are correct? |
|
|
|
Hey patrike could you add a way to manually reset performance statistics, like average?
Thanks for your request. Please let me know which ASIC and firmware you have in mind here, as I think there are only a few of them where this feature exists? I meant in AwesomeMiner, not on the miner itself. Under performance category in the miners tab. Unless that's directly linked to the miner firmware? It appears as though it's different from what is displayed on the miner itself. Would be useful if this was a 24/hr rolling average instead of since powerup as well. Also please add support for pause/resume mining for brains OS. The average hashrate in the Performance column is actually a value reported by the ASIC miners. To see the average hashrate as recorded by Awesome Miner, please open the Mining History for the miner. This way you can see the average hashrate for the period of time you want - for example the 24h average hashrate. Maybe a future improvement would be to let you show this 24h average in the miner list as well. |
|
|
|
Awesome miner firmware api(/api/v1/status) returns {"miner_state":"mining","miner_state_time":163.0,"find_miner":false,"restart_required":false,"reboot_required":false,"unlocked":true}and awesome miner api(/api/miners/{id}) [statusInfo] returns {'statusDisplay': 'Mining', 'statusLine3': '0h 4m', 'secondsSinceStart': 252, 'state': 3, 'stateExtra': 0, 'line3Ex': {'type': 'ParamShortTime', 'values': ['0', '4']}}But, after pausing minings with post to awesome mine api(/api/miners/{id}?action=pause) Awesome miner firmware api(/api/v1/status) returns {"miner_state":"stopped","miner_state_time":34.0,"find_miner":false,"restart_required":false,"reboot_required":false,"unlocked":true}and awesome miner api(/api/miners/{id}) [statusInfo] returns {'statusDisplay': 'Mining', 'statusLine3': '0h 0m', 'secondsSinceStart': 59, 'state': 3, 'stateExtra': 0, 'line3Ex': {'type': 'ParamShortTime', 'values': ['0', '0']}}Can you change the awesome miner statusDisplay based on the awesome miner firmware miner_state? Current behaviour is misleading. Thanks for pointing out this behavior. I've actually considered if there should be one additional state in Awesome Miner for scenarios like this - "Paused". In addition to Antminers there is a concept of Paused state for Whatsminers to it could make sense to show this instead of (like today) hide it behind either Disconnected or Mining. |
|
|
|
Hey patrike could you add a way to manually reset performance statistics, like average?
Thanks for your request. Please let me know which ASIC and firmware you have in mind here, as I think there are only a few of them where this feature exists? |
|
|
|
|
Awesome Miner version 9.7.7
ASIC mining
- Goldshell ASIC integration improved with support for IP address configuration
Features
- Create heat maps and automatically populate, including full folder structure
- Improve custom expressions for heat maps
- Expose ASIC network configuration via C# scripts
Integrations
- Prohashing pools updated with region configuration
Mining software
- BzMiner 12.1.1
- Gminer 3.13
- Lolminer 1.62
- Miniz Miner 1.9z5b
- Nanominer 3.7.5
- TeamBlackMiner 1.74
- WildRig Miner 0.34.0
Corrections
- Correction to sleep mode on specific model and firmware combinations of Antminers S19
|
|
|
|
Thanks for your questions. The profit switcher is currently limited to EtHash + secondary coin but we have received a number of requests to improve this and make it more flexible. The plan is to improve the profit switcher to consider all available combinations for dual mining. |
|
|
|
When trying to run SRBMiner (cpu miner) the _awesome-start.bat_ file has by default included '-p minpayout=20' into the command line parameters. This causes SRBMiner to exit with error " incorrect configuration".
If i remove the parameter '-p minpayout=20' from the bat file and then in terminal run _awesome-start.bat_ then SRBMiner runs.
However the next time i auto start the miner the unwanted parameter is automatically re-inserted into the _awesome-start.bat_.
How to permanently remove this unwanted parameter!
Hi, Awesome Miner doesn't add any "minpayout" parameter unless you manually configure it do to so. Can you please check the Properties of both your Managed Miner and your Pool to ensure you didn't add this as a custom command line argument. If you are using the profit switcher, please right click on the miner and select Edit Profit Profile and check here as well. |
|
|
|
Hi Patrike
if mining rig is overclocked with "sudo nvidia-smi -lmc 810" in batch command "before starting" section, in situation when mining process has crashed, this overclocking settings still active and need to be reseted manualy or over rig reboot. My question is, have AM any sollution how to catch this crash situation and execute other "nvidia-smi" command?
Regards
Hello. Just like you have "Before starting" you should be able to make use of "After stopping" as well in order to execute some reset command. The "After stopping" commands will be executed in case you stop the mining software and also in the case when the mining software simply crash by itself. i filled "After stopping" with reset commands, but in case of crash, this commands will not be executed. It should be possible to verify the actions taken by Remote Agent when this happens. Please check the Remote Agent log file and search for "process not running". This is when Remote Agent detected the crash (missing mining software process). A few lines below you should be able to see "Executing batch commands" where it's states your reset commands. Can you please check if you see this information in the log file? |
|
|
|
Thanks for the feedback Jim. Your Awesome Miner will soon pick up the Nicehash Kaspa pool and list it.
Got it. Thanks! Bit of an issue though, could not benchmark it initially. It would run fine with manually entered hashrate and power without a benchmark using this command line: C:\Users\[user]\AppData\Local\AwesomeMiner\gminer_3_12_windows64_1\miner.exe --opencl 0 -a kas -s kheavyhash.auto.nicehash.com -n 9200 -u [walletAddress].Desktop -p x --pers auto -w 0 --api 4028 However, according to the log, it was trying to benchmark Kaspa as a dual algorithm benchmark with daggerhashimoto using this command line: C:\Users\[user]\AppData\Local\AwesomeMiner\gminer_3_12_windows64_1\miner.exe --opencl 0 -a kas -d 0 -s daggerhashimoto.auto.nicehash.com -u [walletAddress].Desktop -p x --pers auto -w 0 -n 9200 --proto stratum --dalgo kas --dserver stratum+tcp://kheavyhash.auto.nicehash.com:9200 --duser [walletAddress] --dworker Desktop --dpass x --dproto stratum --api 4028 I had to re-enable Ethereum in the Profitablility -> Algorithms list, then disable it in the Managed Miners -> Managed Software -> GMiner algorithm list, then disable it again in the Profitablility -> Algorithms list. After that, it benchmarked normally using the above command line. I had never attempted to set up dual mining before, so not sure why it was trying to benchmark it that way. All of the above is FYI. ;-) Thanks, ...jim Thanks for all feedback. It looks like the benchmark feature favors dual mining in a way that causes some issues. I will look for improvements here. |
|
|
|
Hi Patrike
if mining rig is overclocked with "sudo nvidia-smi -lmc 810" in batch command "before starting" section, in situation when mining process has crashed, this overclocking settings still active and need to be reseted manualy or over rig reboot. My question is, have AM any sollution how to catch this crash situation and execute other "nvidia-smi" command?
Regards
Hello. Just like you have "Before starting" you should be able to make use of "After stopping" as well in order to execute some reset command. The "After stopping" commands will be executed in case you stop the mining software and also in the case when the mining software simply crash by itself. |
|
|
|
When Intel ARC support? I can“t choose this cards. Nanominer and BZminer support it.
Intel Arc will be supported at some point and I will get one of these soon in order to investigate. |
|
|
|
Thanks for the feedback Jim. Your Awesome Miner will soon pick up the Nicehash Kaspa pool and list it. |
|
|
|
|
Awesome Miner version 9.7.6
Features
- Rule action for Firmware Mining Profile can now configure the mining fee region
- Property filter for Device Count (number of hash boards or GPUs)
- Include ASIC fan speed in the miner part of the Awesome Miner HTTP API
- Miner status filter for finding disabled miners. The existing filter for finding offline miners will no longer show disabled miners.
User interface
- Tab visiblility configurable in the Windows application, via the Appearance toolbar
- Configurable permission for User Interface adjustments
Mining software
- BzMiner 12.1.0
- WildRig Miner 0.33.6
Corrections
- Correction to Whatsminer monitoring of hash rate in case the miner ends up in a certain state where it produces 0 H/s
- Correction to SrbMiner-Multi dual mining pool password
|
|
|
|
Hello Patrike, hoping you can help with Awesome Miner not updating Nicehash profitability properly. I'm not sure when it started, but the profitability on NiceHash has not been updating like the other pools. I first noticed this after Eth merge when we started looking for other coins to mine. Nicehash has been stuck on the same profitibility stats since at least then. I've found entries like this in the log file: [089] [E]Failed to download string from: https://api2.nicehash.com/main/api/v2/public/stats/global/24h/ System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel. If I browse to that address with Chrome on the same machine, I do receive a valid response. OS is Windows Server 2012 R2, and TLS 1.2 is enabled in SCHANNEL registry settings. Any insight you could provide? I will review this scenario. On more recent OS versions, Awesome Miner can successfully connect to and get the details from Nicehash without this error. When you load this link with Chrome, can you please press F12 to open the Developer Tools? Go to the Security tab and see the "Connection" section. This one will state the TLS version. It could however be that Google tries to connect with QUIC. |
|
|
|
|
Show Posts
