|
Hi miniZ.
It looks like the SSL certificate on the web site miniz.ch has expired today.
|
|
|
|
Is this a fork of XMrig CPU miner where it also includes a web interface? So from a mining point of view, it's identical to XMrig CPU miner? If it's fully compatible, you can change the download URL for XMrig CPU miner via the Options dialog, Managed Software section. |
|
|
|
I will add Gminer 1.50 right away. It looks like version 1.48 and 1.49 was removed For miniZ it looks like their SSL certificate on the website has expired for HTTPS. I will change all download URL's to HTTP instead. In a few minutes from now you will be able to update the mining software definitions to get these changes. |
|
|
|
Does anyone know if awesome miner can support the futurebit apollo scrypt miner?
I can't seem to gain access to it as Apollos run bfgminer.
thanks!
I don't have any experience with this specific miner. Bfgminer should however be able to provide a monitoring interface where Awesome Miner can connect. Are there any settings in the web interface called "API" or something with related to Bfgminer? Is it possible to SSH to this miner? |
|
|
|
|
Awesome Miner version 6.6.2
ASIC mining
- Feature to send custom web commands to an Antminer
Mining software
- Added mining software: NoncerPro 3.0.2
- Nanominer 1.4.1
- Miniz miner 1.4o
- CpuMiner-Opt 3.9.5.1
- Lolminer 0.8.3
Please note that we make many of the mining software updates available even before these releases - via the 'Update mining software definitions' feature.
|
|
|
|
Hey Patrik,
sometimes rules like "Detect device hashrate, less than or equals: 0 kH/s" or "Detect device count, less than or equals: 2" or similar others will trigger, although actually not necessary because it is just a quick hashrate drop or a miner bug or anything else, but gone in the next second. But the rule is already triggered...
Is it possible to add a trigger like "For X Seconds"?
This doesnt make sense everywhere, but for a few rules it can be a great improvement. The 2 rules above would now look like:
"Detect device hashrate, less than or equals: 0 kH/s" "For: 10 Seconds"
"Detect device count, less than or equals: 2" "For: 30 Seconds"
And it wouldn't have triggered in that case.
For the hashrate, you can actually add multiple "Check statistics" triggers - one that is looking at the current value and one that is looking at the hashrate value 1 or 2 minutes ago. You can then set your rule to only trigger if it matches both these conditions. This makes it possible to not trigger it too frequently. For Device Count there are no feature like this, but I understand your suggestion for this one as well. Thanks! |
|
|
|
I just tried and it works well. If it is true that controls the core for each card to control the maximum temperature. But it does it in a very abrupt way, it goes from 1600 to 900 suddenly, then it goes up to 1200, then it goes down to 900, and so for a while.
As a result the Rig with so abrupt change of core at the end falls and is interrupted continuously. It stops the miner, then starts (without failing notifications), and of course it is worse. I'm talking about a restart every 4 or 5 minutes on a constant basis.
I think the idea is good but it has to be a bit more refined, to do it in a softer way to avoid so many big core changes continuously, and to be able to find a core value quickly that works to maintain the temperature, could make more changes small of core, not 500 mhz of blow, perhaps 100 in 100 and leaving a few seconds in between.
The 1080ti are problematic and very delicate. For example in MTP I invest in 85 90 500, now I am with 70 50 300 and limitation to 76 degrees, but the core of the hot cards changes so much and so fast that it produces multiple falls of the mine, it recovers at the moment, but not It can be like this.
@patrike you could debug this maximum temperature function. The idea is very good but I think the changes are very big and frequent, it could be softer, but little by little. I hope you consider it.
regards
The Temperature Limit you can define is a way to tell the nVidia drivers that they should enforce the limit. Awesome Miner has no control of how this limit is enforced. It's also the same as if you use other overclocking tools, they can also only set the limit but it's up to the nVidia drivers to do the actual work. Like you point out it might be that the clock speed is lowered significantly. I suppose this is a balance between setting a low clock for a shorter period of time vs setting just a little lower clock for a longer period of time. I don't know if there even is a manual way to configure this behavior for nVidia. |
|
|
|
Hello Patrike, I have a doubt in the auto profit mode with the OC.
I have rigs that are multi-brand, each card is a different brand but they are all 1080ti, but there are some brands that go with too much factory OC.
So the problem that I have that only one OC for all the cards is not valid for me. While some are at 65 degrees another one reaches 84 and stops. They are the MSI ARMOR with a special Artic ventilation kit, and I can not use them. They have a very high CORE. If under the core so that only that card is not hot, in the end the rig produces me less, I have a card at 77-78 degrees and the others at 65 or less.
I do not see that there is a way to save OC profiles, in which each card can have its own core, memory, power, limitation. I think in managed if you can, but in Auto profit no.
I think this is a situation that can be given to many people, that one card gets hotter than the rest and you have to lower the general OC, instead of defining for example a profile for "Rig5 MTP" "RIG5 X16R" with which could reduce the core of MSI armor but leave the others with more power because they do not heat up as much.
It would be a perfect scenario to make totally personalized profiles, and it is as easy as making a general one and when you have it, you modify it card by card, going to the one that gets hotter and only that lowering the core enough so that it does not overheat. And the average hash of the Rig would be greater than if under the OC to all the cards.
I have changed the thermal paste, the thermal pads, I have put the best air cooling kits that is Artic Cooler IV with huge rear heat sink. But seeing Clocking in AM, I see that these cards are 100mhz higher in the core than the other models. This is a huge difference.
It is a lot of work to make fully customized profiles to several RIGS for each al-go, but the work does not scare me, so there is no possibility of doing what I ask. It would be the perfect option to finish the OC, even forgetting about the double OC that I asked, because this is a much more serious problem for me. In winter there are no problems with this because the air of the street is very cold, but in summer you can notice that difference of OC in a single card.
You should be able to use Clocking Profile Groups (Options dialog, GPU Clocking Profiles section) to define for which GPU to apply a certain Clocking Profile. In the past you could only specify by GPU ID or GPU Name (like 1080), but in recent version you can also specify by vendor (ASUS, MSI, ...) which might be of help here. You can for example have one overclocking profile set for all ASUS cards and another one for the MSI cards. If you have multiple types of MSI cards (Armor and Gaming) there are however no solution except using GPU ID's. |
|
|
|
Unfortunately I don't have an answer to this - but there might be someone else in the community that are more experienced with extracting data from block explorers. |
|
|
|
Whats the easiest way to run the nano miner as admin through AM? when i turn the software on, it says i should do it.
im also getting 2 different power output readouts on the graphics card. AM says a card will be 90w, but nanominer says 67w. which would be more accurate?
To run a miner as administrator, please right click on the miner, select Properties and then go to the Environment section where you can enable the Admin setting. AMD is not reporting as accurate power usage values as nVidia do. For this reason Awesome Miner is by default adding 35% to the power usage to make it a bit more realistic. You can change this in the Options dialog, GPU settings section. If you set it to 0%, Awesome Miner should show the same value as nanominer - but I also think that would be less realistic. |
|
|
|
If a miner crashes, it does not stop normally. also does the reset of oc?
Yes, no matter if the miner crashes or is stopped manually, the OC parameters will be reset. So if the miner crashes Awesome Miner will first reset the OC, then re-apply the OC settings you have defined for the miner/algorithm as "Start profile" and then start the mining software again. The general problem of OC has gone well, well I still have the OC of outputs set to 90 0 0 1200MV, but I will remove them. Now if we can focus on some small problems that are still better. Here I leave you in the capture, RIG6 "offline interface" but it is working. It is not always like that, sometimes it does not work. But you can throw hours like that, working but at a slow pace. It occupies so much CPU that it does not allow me to enter the RIG remotely. In this case and the lack of information, I only know that it was Gminer but I do not know the al-go that was being mined. But note that neither temperature, nor profit, nor anything, everything in a vacuum but working. I have activated the default rule in AM for devide offline, but sometimes it goes into a loop several times. It is a lesser evil compared to before, now it is possible to work better, but they are problems that a few months ago did not exist, and it is not a rare miner, it is Gminer. The rig is the RTX, but after restart everything goes correctly. But I'm worried that it will stay that way and go at a slower speed, I already commented that it occupies so much CPU that it does not let me enter the RIG by remote, with which its mining performance is also lower when this happens. Good that the overclocking is working better in general. For this scenario you report, can you please send me both the Awesome Miner and Remote Agent log file. Please send via PM or e-mail to not share all log details to the public. Thanks! |
|
|
|
If a miner crashes, it does not stop normally. also does the reset of oc?
Yes, no matter if the miner crashes or is stopped manually, the OC parameters will be reset. So if the miner crashes Awesome Miner will first reset the OC, then re-apply the OC settings you have defined for the miner/algorithm as "Start profile" and then start the mining software again. |
|
|
|
|
Awesome Miner version 6.6.1
GPU mining
- Native overclocking can be configured to automatically reset all overclocking parameters when a miner is stopped. Configurable via the Options dialog, GPU Settings section.
- AMD Radeon VII supported with monitoring and native overclocking on Windows
Configuration
- Bulk edit of pools
- Improved bulk edit of Managed Miners, to include command line parameters
User interface
- Ctrl+C can be used to copy all selected objects (miners, pools and more) from the lists in the Options dialog
Integration
- Modify Zpool API calls to be possible to identify and accept by Zpool
Mining software
- Lolminer 0.8.2
|
|
|
|
Another PAtrike suggestion. In the rules, which come by default use several, one that notifies me from time to time is when an RIG reaches a temperature of 80 degrees, although I stop mining to 84.
I do not feel like putting screenshot, but when it warns you it says something like
Rig5 High temperature warning
But, you can not improve that rule to tell me what AL-GO is. Many times I find that message, and I always think, what protocol would it have been? I do not know, or I'm in front of the computer when it gives the fault and know what protocol was undermining or I do not know anything. I only know that it warmed up a bit and it is already there, but I can not correct anything if I do not know that al-go was that temperature.
Thank you
I understand your point and I've received similar feedback in the past. It would be a concept where the trigger could transfer some information to the action, like algorithm, temperature, which device it was and so on. |
|
|
|
Just asking I guess awesome miner doesn't Support AMD Radeon VII ?. I don't expect it to be added right now just want to know.
it only shows the hash rate no fan speed, temps etc.
I will verify the support within the next few days and get back to you. Thanks patrike if you fixed it, i now see everything with my AMD Radeon VII/Vega rig.!!! Nice that it's working better. Version 6.6 included most of the implementation for Radeon VII, but there are still a few adjustments in the pipeline for the fan speed and native overclocking. The plan is that it will be officially supported in version 6.6.1. |
|
|
|
Hi Patrik,
Need some info on the API calls to Yiimp pools.
Online Services tab -- Update Now
and
Options > Profit Switching - under General settings - Switching interval (minutes / seconds)
Does Awesome Miner send out an Agent Name when it polls the pools API for these, if so, what is it ?
If not, can one be added and give it a name so that pool owners can identify it and not block it.
Thanks.
I've just sent you a PM about this. |
|
|
|
Please do not take long to incorporate the solution please. I've had enough for the last 2 or 3 weeks.
I already found the RESET order, but make sure it also resets the millivolts, and that it is applied BEFORE starting to mine, because as I said, if it crashes, the output OC does not apply.
I personally would add this as something transparent. That is, the user does not have to configure or touch. That by default AM does it before starting to mine. The less the user has to learn, the fewer problems they will ask you.
First the miner reset, a few seconds later, the OC that has been selected for that Al-go is applied. It's something so simple and simple that you should not need a choice. Totally transparent to the user without doing anything, and we removed a lot of problems at once.
Implementing an auto OC reset feature is quite easy so you can expect it soon. I will enable it by default only for new installations. For existing systems you will have to enable it as a global setting in the Options dialog, GPU settings section, once it's available. As it changes the behavior of the OC in Awesome Miner, I cannot introduce this change for everyone as it will be a new behavior. This is the reason why it only can be enabled by default for new installations, while all existings users will have to enable it. |
|
|
|
|
Awesome Miner version 6.6
ASIC mining
- Improved support for Avalon 921 with display of chip temperature and more details
- 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
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 definitions can be updated without upgrading the Awesome Miner or Remote Agent version
- GPU clocking groups improved to also support mapping based on the exact GPU name, GPU vendor and PCI Bus Id
- Improved display of AMD GPU information on Linux with vendor and power usage
- Added additional algorithms
FPGA mining
- Blackminer F1 FPGA supported with temperature display
Configuration
- SSH connection timeout configurable in the Options dialog, Advanced section. Default timeout is now set to 8 seconds.
Features
- Added a backup and restore feature to the toolbar Backup (renamed from Import/Export), intended for a complete backup of all configuration data
- GPU miner diagnostics can be configured to run for up to 5 minutes before terminating
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
- Added additional coin images
- Description for Windows Uptime changed to System Uptime
- Added menu item for launching the web interface for the selected ASIC miner. Available via the toolbar Tools -> Antminer&ASIC.
- Display of total miner commands in queue for External Miners (for large systems only)
Mining software
- Claymore Ethereum Miner 14.7
- Ethminer 0.18.0 rc0
- TeamRedMiner 0.5.2
- T-Rex Miner 0.12.1
- GMiner 1.47
- CpuMiner-Opt 3.9.4
- SrbMiner 1.9.0
- Nanominer 1.4
- WildRig Miner 0.17.9
Corrections
- Added missing Blake2b pools
- Improved detection of xauthority environment variable on Linux for nVidia clocking
- Improved detection of when 'allcoins 1' needs to be added to the Claymore Ethereum miner command line
- 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
- 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
- Correction to z-enemy miner integration on Linux
|
|
|
|
Another failure. If I throw a coin with an OC that has a limitation of millivolts, and this miner crashes, the OC of stopping with the neutral OC does not apply. And therefore the limitation of millivolts of the previous currency remains again. When wanting to start mining again, as you go to another currency that needs more tension, the miner stays in offline miner in the AM interface
I think the most appropriate measure is to apply a neutral OC without limitation in millivolts before mining and before applying the OC that I have chosen. Then it will not matter if it has crashed.
Thanks for sharing your findings. Today Awesome Miner can have a "Stop" profile for the clocking and it's possible to add a "Reset" command here manually if you go to the Options dialog, GPU Clocking Profiles section, add/edit a profile where you can add "Reset". This is supported on both AMD and nVidia and will send a overclocking reset command to the GPU drivers. This will restore all clocking/voltage/fan settings for a GPU to default values. When a miner is either manually stopped or has crashed, Awesome Miner will run the specified "Stop" clocking profile. Although it's possible to have a setup like this - it's a bit time consuming to setup. What I think is the way forward is to have a global setting like "Reset GPU clocking when miner has stopped". If enabled, Awesome Miner could reset the GPU clocking completely via a reset command to the GPU drivers. In your case it would also reset the voltage setting to default. Please let me know if you think a feature like this would make sense to have globally. Thanks! |
|
|
|
Hi Patrik & Fellow Awesome Miners, A few ideas (some might not necessarily be practical / useful) - Ability to Bulk Edit Pool Properties - Especially Worker name, Worker password, Wallet Address, Profit Factor field
- Ability to clone Pool Groups
- In conjuction to above, ability to have the Pool Groups the ability to override the fields in point #1 (which can make the first 1 points obsolete and completelly replaced by this one IMHO), This is particularly useful for pools like Zergpool where one want's to switch between coin addresses/payout coin type/coin targeting/solo or shared mode switching
- Ability to fetch Auto-Exchange Status via pool API and consequently include/exclude from a Pool Group (mining a coin when AE is disabled generally means no reward when payout coin needed to be exchanged)
- Ability to parse Online Services' Actual payout % to individual pools according to their algorithm (Yiimp pools somehow seems to have poor luck, or at least I find mining on Zergpool generally have efforts way > 100% across all algos, shared or solo mining
- Ability to detect and compare coin price delta (daily, 7day, 30day ... etc) and set it as a rule trigger, basically interested in the pairs (BTC/USD, XXX/BTC where XXX is an Alt pair of choice) due to the delaying nature of auto-exchange and correlation between major coins espeically BTC leading entire crypto up and down, sometimes this can automate a more optimal exchange option rather than manual (i.e, sometime it's better to mine and AE to BTC, other times it is better perhaps to be paid in say, LTC for example)
Best Regards, Ability to Bulk Edit Miner Properties command line parameters and environment
This can come very handy on a larger GPU farm
Thanks for all good suggestions. It's all noted. Especially bulk operations should be a priority. Cloning of Pool Groups is already supported. |
|
|
|
|
Show Posts
