On a few of my miners (2 out of 11) the NVidia drivers version shown in the Summary tab is not showing the most recent installed version.
I have installed NVidia version 416.34 as reported in Device Manager and by MSI Afterburner but the Summary tab shows older versions.
Awesome Miner is reading the version numbers from the Registry: HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} Can you see if there are multiple entries here with different version numbers? Awesome Miner might pick the first one. First entry is 0000 - Intel Driver 2nd entry 0001 is correct - Nvidia DriverVersion 25.21.14.1634 last entry 0005 is what is shown in Summary - 23.21.13.91.24 In my second case AM picks the first entry from 0000, but the correct entry is from entry 0004. Thanks for sharing the details. I assume that both 0001 and 0005 had a property called "ProviderName" set to nvidia in this case. What I will do for the next version is to look not only for one entry saying "nvidia", but actually selecting the one with the highest version number - assuming this is the correct one. |
|
|
|
Please add the total power consumption for the algorithm to the coins and Online Services tab, just like the common hashrate.
Thank.
Thanks for the suggestion - this will be included in the next release. |
|
|
|
Any hints or tips on setting up A.M. for SRBMiner auto switching on MoneroOcean pool? I have SRBMiner auto switching working through the config files and start-algo-switching.bat file of SRBMiner but now I'm trying to figure out the best way to use A.M. to run this.
EDIT: I got it working by setting the command line in A.M. to the same as what's in the start-algo-switching.bat file and overriding the v8 config and blanking it out. Works ok but is there a better way? The biggest drawback here is every time A.M. has a new version of SRBMiner I will have to manually update some of the files on the miner such as the pools list and algos.txt
Please consider how to add better support for SRBMiner's auto switching to A.M.!
Thanks for the update. It's a quite mining software specific feature we have here, so I'm not sure if it this feature is popular enough to justify the implementation time required to support it. |
|
|
|
patrikeAfter the SIA fork, three coins were added, the site has an API (including the API market place) I could not get the balance API https://siamining.com/chainsalgo blake2b Thanks for the update. SIA is very difficult to figure out balance for with the Block Explorers that has been available so far. Unless there is a block explorer that has an easy-to-use API where Awesome Miner can get the balance, it will not be supported. |
|
|
|
On a few of my miners (2 out of 11) the NVidia drivers version shown in the Summary tab is not showing the most recent installed version.
I have installed NVidia version 416.34 as reported in Device Manager and by MSI Afterburner but the Summary tab shows older versions.
Awesome Miner is reading the version numbers from the Registry: HKLM\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318} Can you see if there are multiple entries here with different version numbers? Awesome Miner might pick the first one. |
|
|
|
Thanks for the reply...
I try, but it does not work.
Rules -->User defined rules --> Add
Triggers --> Miner Revenue --> Less Then or Equals --> 2,3 Eu --> 60s
Actions --> Execute remote command --> Miner Command --> Shutdown.exe parrametrs /s NOT WORK
or
Action --> Execute remote command --> Miner Command --> Stop miner NOT WORK
Please for help !
Use miner profit instead miner revenue. [Miner profit = Miner revenue - power cost (if configured)] I understand that... Miner stop/start work but shutdown not work.... Hi, 1) Please verify that the rule is enabled (the checkbox is checked) 2) Could you send me a few screenshots (via mail) of this trigger configuration and the miner list where the revenue/profit is being display? |
|
|
|
Hello, Is there a way to get coin balance from http://explorer.btcd.io for bitcoin diamond ? I made some tests without success... They didn't provide any API documentation, but by looking at the network requests made by the web browser, they use the following that can be entered as Block Explorer URL in Awesome Miner http://20.184.13.116/v2/addr/[address] Then it turns out that they report the balance in unites of "1E-7", so if you select the 1E-8 setting in Awesome Miner you will get a balance 10 times too low. I will add a new setting for selecting 1E-7 in the next release. |
|
|
|
Thanks! I will include more icons in the next release. |
|
|
|
|
Awesome Miner version 5.7.5
GPU mining
- NOTE: Some mining software will require CUDA 10.0, included with recent versions of the nVidia GPU drivers
- Updated predefined pools for the profit switcher to make x22i and more pools available
Features
- SUQA block explorer for wallet balance
Rules
- Device Temperature trigger allows configuration to trigger on an exact device temperature of 0 C.
Mining software
- SrbMiner 1.6.9
- DSTM Zcash CUDA miner 0.6.2
- T-Rex miner 0.7.2 (CUDA 10.0)
- CryptoDredge 0.9.4 (CUDA 10.0)
- WildRig Multi Miner 0.12.5.1 beta
Corrections
- Zjazz miner GPU selection corrected
- Coins per day calculation corrected for the coin XSG
|
|
|
|
Patrike, I have a Geforce RTX 2080 FE card, I've noticed that the fan speed is not being reported in Awesome Miner in the lower window, any chance for that to be addressed ? Thanks. https://1drv.ms/u/s!AoT9lvLcOWd_h10KRd7JHRHQgwFzP.S This might be a limitation of the miner programs, maybe the Devs for these can fix that as well. I don't have a solution for this right now, as Awesome Miner uses a third-party library for getting GPU information. I do however plan to investigate this further to see if it's possible to find a workaround. |
|
|
|
I have several cards in groups. I can not see how much they have the total power consumption, only the hashrate is visible.
Please add to the Coins tab in the profile hashrate column also the total power. It will be just great. Thank.
Thanks - good point. |
|
|
|
A suggestion about T-rex, I should add two different ones, the optimized one for cuda 9.2 which is the one that brings by default AM and the one optimized for Cuda 10, I have all my rigs in cuda 10
The next release of Awesome Miner will include T-rex 0.7.2 for CUDA 10 by default. If there is a demand for the CUDA 9.2 version I can post the link for it. |
|
|
|
Hi,
there's a problem with profit switching, i don't know if is a general issue,
but not always change coin to mine, i have problem with Teamredminer
when the new coin to mine use the same miner (Teamredminer).
Thanks.
Bye.
Thanks for your question. I will require more information about this scenario. Are all Remote Agents up-to-date with the same version as Awesome Miner? Can you please share details on what the profit switcher decision is (right clock on the miner, select View Details) compared to what is actually showing up in the miner list? Thanks! |
|
|
|
hey patrike. many miners report 0 C temperature for GPUs which stopped responding for some reason (became "lost"). I've tried to create a rule that could take care of these cases (perform actions like restart the miner/reboot the rig/etc) without success. the trigger "temp less than 1 C" doesn't work in this case, and for some reason '0 C' temp is not accepted in this trigger. any solutions?  As a workaround you can catch this with "Detect device count, less than or equals: 7". Most time this works, but not when the miner hangs in a damn loop and restarts unlimit time (T-Rex for example always tries to start with the full 8 cards, shows an error and then restart). it could work, but I have 40 miners added to AM and setting up a rule for each one will be a pain for sure. hoping for a better solution. Right now the Device Temperature trigger ignores devices with '0 C' and as you noticed you cannot configure the trigger to a value of 0 either. The idea behind this was that sometimes the temperature is unknown (0) and shouldn't cause trouble for your trigger. I will however make the following changes in the next release: - Device Temperature trigger can be configured for 0 C. - If you use the Equals operator in combination of 0 C in the trigger, it will trigger if the device temperature is 0. It will however not trigger with "less than 1 C", as you must explicitly set it to detect "Equals 0" |
|
|
|
Hello,
Run Batch commands before starting miner HELP. I am trying to run a OverdriveN Tool batch file to set OC and voltage. The file runs perfectly on the machine if i launch it. But when i try from Managed Miner Properties>batch Commands>Execute additional commands before starting the mining software. It appears to open and close the .bat never allowing it to complete and apply the OC Profiles. I must need some type of wait command.
My command
C:\Users\XXXX\Desktop\OverdriveN\RUNONT.bat
Thanks.
@Patrike
Have you checked the box for running this as Administrator? |
|
|
|
Thanks for the update. So when you use the GPU ID mapping and set GPU 3 to have lower clock speed, this doesn't take effect? When using MSI Afterburner UI directly, it works fine?
It's possible to verify the clocking operations that Awesome Miner send to MSI Afterburner Remote Server. Via the Awesome Miner Remote Agent log file (toolbar: Tools -> Log File -> Remote Agent) you can search for "Executing GPU clocking command" and see what numbers Awesome Miner is using. This could be good to get an understanding of where it goes wrong.
Clocking for Remote Agent on Linux will be supported in the future. The idea is to also add support for overdriventool and nvidiainspector on Windows.
Correct, it doesn't appear to work using GPU ID either. I tried disabling MSI Afterburner Remote Server for this particular rig by renaming the folder containing the executable, but that caused the rig to become unresponsive after a few minutes of mining. What's the best way to disable Remote Server Agent on a specific miner for testing purposes? I take a look at the log fine. Great news about clocking for Linux agent and nvidiainspector support! What you could try is to let the Afterburner Remote Server run, but right click on the systray icon for it and change the connection password - then Awesome Miner will send the commands but they will be rejected. |
|
|
|
If you use the GPU name Awesome Miner must be able to get the names from MSI Afterburner, but in your case you only get "GPU 0" and so on without the name. Can you please try to apply the updated fix for MSI Afterburner Remote Server, listed at the bottom of this page? https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclockingI know a few other users that were able to resolve the GPU name problem by applying the updated DLL-file. Thanks Patrik. That took care of the issue with the GPU names not showing up properly. However, Afterburner Remote Server reports all 7 cards as being identical as follows: GPU 0: GeForce GTX 1080Ti GPU 1: GeForce GTX 1080Ti GPU 2: GeForce GTX 1080Ti GPU 3: GeForce GTX 1080Ti GPU 4: GeForce GTX 1080Ti GPU 5: GeForce GTX 1080Ti GPU 6: GeForce GTX 1080Ti And while that is technically true, GPU 3 is very different in that is an EVGA FTW3 Hybrid as opposed to just an EVGA SC2, so it has different PL and Core boost requirements. I use wish Afterburner would allow you to set specific PL and Core clocks like how it is typically done under Linux. Speaking of which, will GPU clock profiles be supported in the Linux Remote Agent at some point? Thanks for the update. So when you use the GPU ID mapping and set GPU 3 to have lower clock speed, this doesn't take effect? When using MSI Afterburner UI directly, it works fine? It's possible to verify the clocking operations that Awesome Miner send to MSI Afterburner Remote Server. Via the Awesome Miner Remote Agent log file (toolbar: Tools -> Log File -> Remote Agent) you can search for "Executing GPU clocking command" and see what numbers Awesome Miner is using. This could be good to get an understanding of where it goes wrong. Clocking for Remote Agent on Linux will be supported in the future. The idea is to also add support for overdriventool and nvidiainspector on Windows. |
|
|
|
one thing I need to understand is why the hell does the miner keep trying to mine neoscrypt when its less profitable by all the oline calculators than x16r
its not the power setting becase I set my power cost to zero
If you right click on the miner and select View Details - is the Profit Switching tab indicating that Neoscrypt is on top based on your profile hashrate? |
|
|
|
Awesome Miner version 5.7.4
GPU mining
- Display warning on the Summary tab for miners with old nVidia drivers not supporting the latest CUDA version
- Diagnostics feature improved and includes OS and driver information
Configuration
- External Miners can be configured with a Profit profile without having to enable profit switching
Rules
- Triggers using the concepts Greater/Less Than or Equals also includes support for Greater/Less Than
Mining software
- Added mining software: Zjazz CUDA miner, for X22i
- WildRig Multi Miner 0.12.5 beta
Corrections
- Correction to the default pool configuration of Antminers
- Correction to revenue calculations for a number of coins based on Equihash variants
SO what do we do with the error : no pool avaiable for benchmark ? I get that for like 9 algos including the new one X22i , sonaa and all the equihash forks How do I fix this ? , I know blockmasters has x22i for sure why does it not allow benchmark , same with the equihash 192 etc because they are not included in default Online Services list yet, but you can add them manually. not same with sonoa and equihash192, predefined pools do not support them. @patrike you can consider adding NLPool, Phi-Phi-Pool and Starpool as predefined Yiimp-type pools in place of Zergpool, which is gone now. they all support autoexchange to BTC wallet. Awesome Miner can automatically populate entries on the Online Services tab when for example Block Masters add support for the X22i algorithm. The feature of predefined pools made available to the profit switcher is however not as dynamic, but I will include these X22i pools by default in the next release. You are correct that some algorithms are simply not supported by any of the predefined pools. I'm also considering adding more of these yiimp-based pools and I think Phi-Phi is next on the list. For those that manually want to add more of these yiimp-based pools, please see the guide: https://support.awesomeminer.com/support/solutions/articles/35000086026-add-custom-yiimp-compatible-pools |
|
|
|
I'm running all my rigs as Managed Profit Miners. Most of my rigs contain identical GPUs, but I do have a few that are mixed, and I'm having a hard time getting different clock profiles to work consistently with them I have my Profit Profiles and Groups already setup, and they are as follows: Profit Profiles GTX 1050Ti GTX 1060 3GB GTX 1070 GTX 1070Ti GTX 1080 GTX 1080Ti Profit Profile Groups (these are my mixed rigs other than one that is a mix of air and water 1080Tis discussed below) 1x 1050Ti 1x 1070Ti 2x 1070 x1 1080Ti 1x 1070 1x 1080 For Profit Profiles, I figured it would not be necessary to distinguish between Air and Water Cooled GPUs. Agreed? For GPU Clocking Profiles on the other hand, I have created different profiles for Air vs. Water cooled GPUs since they require different settings. So I have the following: GTX 1050Ti ETH GTX 1050Ti Standard GTX 1060 3GB ETH GTX 1060 3GB Standard GTX 1070 ETH GTX 1070 Standard GTX 1070 Hybrid ETH GTX 1070 Hybrid Standard GTX 1070Ti ETH GTX 1070Ti Standard GXT 1080 Hybrid ETH GTX 1080 Hybrid Standard GTX 1080Ti ETH GTX 1080Ti Standard GTX 1080Ti Hybrid ETH GTX 1080Ti Hybrid Standard So I have this one rig with a mix of 1080Ti's that are air cooled and one that is a hybrid. The GPUs are as follows according to AM: GPU0 EVGA 1080Ti SC2 GPU1 EVGA 1080Ti SC2 GPU2 EVGA 1080Ti SC2 GPU3 EVGA 1080Ti FTW3 Hybrid GPU4 EVGA 1080Ti SC2 GPU5 EVGA 1080Ti SC2 GPU6 EVGA 1080Ti SC2 I created a Clocking profile group with 6x 1080Ti Standard profiles and 1x 1080Ti Hybrid Standard. I arranged the GPUs in the profile to match what is shown in the table above by simply entering 0 - 6 for each GPU. But apparently I'm doing something wrong since all 7 GPUs share the same clock and power settings and after a short while the miner software is restarted by AM since the FTW3 hybrid keeps falling over because the clocks are too high given the much factory OC of the FTW3 card compared to the SC2's. When I look at this mining rig in the GPU tab, I can clearly see that the clock on the FTW3 is about 80 MHz higher than the other 6 and it also uses about 40 more Watts. When I click GPU settings/settings via Awesome Miner and MSI Afterburner... I can confirm that all 7 GPUs share the exact same power and clock settings, which is why the FTW3 runs higher than the rest. When I click the Profile drop down, the Clocking Profile Group I created is not in the list to choose from. So how do I associate a Clocking profile group to a particular miner? Do I have to create a Profit Profile specifically to this mining rig instead of using the regular GXT 1080Ti Profit Profile that I use for all my 1080Ti Air cooled only rigs? That appears to be the only way I can then select this "custom" 1080Ti Profit Profile, from within which I can then select the Clocking Profile Group I created for individual algos. EDIT: So I went ahead and created a Profit Profile called GTX 1080Ti Mix and within it, I selected my Clocking profile group with 6x 1080Ti and 1x 1080Ti hybrid. I then went to this miner and changed the miner properties to point to the new Profit profile I created. I restarted the miner, but it is still showing all 7 GPUs at 80% and +120 Core. EDIT2: I changed to match on GPU Name instead of ID. Still didn't work. Here are some pic of my config: https://ibb.co/jo0hYAhttps://ibb.co/mLh1RVhttps://ibb.co/iUQufqhttps://ibb.co/nJyrRVhttps://ibb.co/igBNYANote that in the last screenshot above, where I'm showing the "Settings via Awesome Miner and MSI Afterburner", all that is showing GPU 0:, GPU 1:, etc. The actual name you can see in the window behind, do not carry through to the Afterburner window. Could that be the issue? If so, how do I get the GPU names I assigned to show up there? Thanks! If you use the GPU name Awesome Miner must be able to get the names from MSI Afterburner, but in your case you only get "GPU 0" and so on without the name. Can you please try to apply the updated fix for MSI Afterburner Remote Server, listed at the bottom of this page? https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclockingI know a few other users that were able to resolve the GPU name problem by applying the updated DLL-file. |
|
|
|
|
Show Posts
