Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 192. (Read 703146 times)
March 25, 2019, 05:32:21 AM
This could be some incompatibility between a specific GPU, driver and mining software. A good troubleshooting step would be to find out of any other mining software works better on these GPU's.
March 25, 2019, 05:30:58 AM
Hi, Patrick. It seems that the www.coincalculators.io API signals have changed, all the numbers are not correct. Current Revenue (BTC / day) instead of USD
It's correct that there have been API changes and I've received information from the Coincalculators admin about the changes.Right now you will run into problems if you use "CoinCalculators exchange rate" set to either Highest Bid or Lowest Ask, but from what I can see it should work better with Default.
I will adjust Awesome Miner to these changes.
It helped, but not for all coins.
Hello.
Coin SPK. but this is because of the price southXchange 0.22 .... BTC, with complexity normally
DIN also the price is not correct
BZEdge
March 24, 2019, 10:43:07 PM
Patrick
Describe in more detail the process of installing a second agent on a computer to create a manga CPU and GPU on a single computer
Describe in more detail the process of installing a second agent on a computer to create a manga CPU and GPU on a single computer
March 24, 2019, 06:31:37 PM
NATIVE OverClocking NVIDIA
Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
I do not have that problem. Native OC is perfect for me.Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
What drivers are you using?
@patrike besides that I would suggest adding core voltage lock to NVIDIA clocking profiles. that should be easy to implement, with just one NvAPI call.
also I've found a bug with native OC on mixed AMD/NVIDIA rigs - in my case, when applying the profiles for AMD GPUs, some of them like fan speed, fan mode and power limit are applied to NVIDIAs as well.
I have several rigs all nvidia, all with native OC, all with the native auto speed, and I do not have that problem, there are times that are even at 30 or 40%. I have not noticed any problem in that aspect.
Since I use native OC, for me everything is much more stable when the OC and the automatic speed is perfect.
March 24, 2019, 06:29:02 PM
PAtrike this like crazy waiting for your update, where we can specify the url of the Explorer and get the direct difficulty. Today I have been mining a coin, which days ago if the difficulty worked well, but today it stops at a predetermined value and the profit is very high. I have mined badly, that coin has been put and then the difficulty with the coin explorer was more than double
I hope you give priority to that new function, because it is sorely needed. Any function that helps obtain such fundamental data well, will be a great improvement. And I think that right now is the most important for AM, from my point of view.
I hope you give priority to that new function, because it is sorely needed. Any function that helps obtain such fundamental data well, will be a great improvement. And I think that right now is the most important for AM, from my point of view.
March 24, 2019, 12:22:20 PM
NATIVE OverClocking NVIDIA
Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
I do not have that problem. Native OC is perfect for me.Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
What drivers are you using?
@patrike besides that I would suggest adding core voltage lock to NVIDIA clocking profiles. that should be easy to implement, with just one NvAPI call.
also I've found a bug with native OC on mixed AMD/NVIDIA rigs - in my case, when applying the profiles for AMD GPUs, some of them like fan speed, fan mode and power limit are applied to NVIDIAs as well.
Thank you I figured it was normal and I have been using AB just for the fan curve but hoping this can be addressed so we dont need AB. As for amd I notice odd behavior if using latest drivers and have resorted back to ONTool on those rigs. But my AMD w driver 18.6.1 seem good. thanks for clarification.
March 23, 2019, 06:11:16 PM
NATIVE OverClocking NVIDIA
Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
I do not have that problem. Native OC is perfect for me.Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
What drivers are you using?
@patrike besides that I would suggest adding core voltage lock to NVIDIA clocking profiles. that should be easy to implement, with just one NvAPI call.
also I've found a bug with native OC on mixed AMD/NVIDIA rigs - in my case, when applying the profiles for AMD GPUs, some of them like fan speed, fan mode and power limit are applied to NVIDIAs as well.
March 23, 2019, 11:19:01 AM
NATIVE OverClocking NVIDIA
Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
Driver Version 416.34
Anyone notice that while using this feature the gpu core will be throttled well before the fans move to 100%.
Example
Set Temp limit to 65c fan speed auto.
AM will maintain that temp.
Gpu Fan will speed will not go up to 100% because temp is maintained due to throttling Core.
If I move fan speed to 100% remove auto fan Gpu core goes back up and drastically improves hash rate. (20%-30% improvement)
Maybe Im missing something please let me know if I am.
AMD clocking is great because it has the fan target temp and temp Limit
I do not have that problem. Native OC is perfect for me.
What drivers are you using?
March 23, 2019, 10:51:33 AM
http://prntscr.com/n1wdkr
I, too, can not understand why they both do not want to work
I, too, can not understand why they both do not want to work
March 23, 2019, 06:11:53 AM
Hi, Patrick. It seems that the www.coincalculators.io API signals have changed, all the numbers are not correct. Current Revenue (BTC / day) instead of USD
It's correct that there have been API changes and I've received information from the Coincalculators admin about the changes.Right now you will run into problems if you use "CoinCalculators exchange rate" set to either Highest Bid or Lowest Ask, but from what I can see it should work better with Default.
I will adjust Awesome Miner to these changes.
It helped, but not for all coins.
Hello.
Coin SPK. but this is because of the price southXchange 0.22 .... BTC, with complexity normally
DIN also the price is not correct
March 23, 2019, 06:09:45 AM
Hi, Patrick. It seems that the www.coincalculators.io API signals have changed, all the numbers are not correct. Current Revenue (BTC / day) instead of USD
It's correct that there have been API changes and I've received information from the Coincalculators admin about the changes.Right now you will run into problems if you use "CoinCalculators exchange rate" set to either Highest Bid or Lowest Ask, but from what I can see it should work better with Default.
I will adjust Awesome Miner to these changes.
It helped, but not for all coins.
Hello.
Coin SPK. but this is because of the price southXchange 0.22 .... BTC, with complexity normally
DIN also the price is not correct
BZEdge
March 23, 2019, 02:53:24 AM
since last update my miners keep losing API access, when I check the pools directly, the miners are working just that AM cannot see them so I have to reboot them in order for AM to see them. Had this a dozen or so updates ago as well - hope it stops soon. its a pita to restart miners in order to see them in the AM cloud service.
In some cases, this can happen when Antminers mine on a specific pool. It may sound strange, but they can simply stop responding on the API port while they still are mining. Testing with another pool may help.For more details about how to troubleshoot, see:
https://support.awesomeminer.com/support/solutions/articles/35000094734-troubleshooting-antminer-and-asic-miners
I get that but to have to consistently happen 5-10 times a day require a reboot is tedious.
March 23, 2019, 02:47:50 AM
Hi, Patrick. It seems that the www.coincalculators.io API signals have changed, all the numbers are not correct. Current Revenue (BTC / day) instead of USD
It's correct that there have been API changes and I've received information from the Coincalculators admin about the changes.Right now you will run into problems if you use "CoinCalculators exchange rate" set to either Highest Bid or Lowest Ask, but from what I can see it should work better with Default.
I will adjust Awesome Miner to these changes.
It helped, but not for all coins.
March 22, 2019, 09:25:35 PM
since last update my miners keep losing API access, when I check the pools directly, the miners are working just that AM cannot see them so I have to reboot them in order for AM to see them. Had this a dozen or so updates ago as well - hope it stops soon. its a pita to restart miners in order to see them in the AM cloud service.
In some cases, this can happen when Antminers mine on a specific pool. It may sound strange, but they can simply stop responding on the API port while they still are mining. Testing with another pool may help.For more details about how to troubleshoot, see:
https://support.awesomeminer.com/support/solutions/articles/35000094734-troubleshooting-antminer-and-asic-miners
I get that but to have to consistently happen 5-10 times a day require a reboot is tedious.
March 22, 2019, 07:02:26 PM
Hi, Patrick. It seems that the www.coincalculators.io API signals have changed, all the numbers are not correct. Current Revenue (BTC / day) instead of USD
It's correct that there have been API changes and I've received information from the Coincalculators admin about the changes.Right now you will run into problems if you use "CoinCalculators exchange rate" set to either Highest Bid or Lowest Ask, but from what I can see it should work better with Default.
I will adjust Awesome Miner to these changes.
It helped, but not for all coins.
March 22, 2019, 05:45:03 PM
@patrike - Can you please adjust how the rule buttons are clicked on the cloud UI, when using a touch device like an IPad? They don’t click always on touch and don’t give proper feedback, so it’s difficult to make out if they have been clicked.
There will be updates to the Cloud web UI in a few weeks and I can make sure this is improved as well. March 22, 2019, 05:43:03 PM
since last update my miners keep losing API access, when I check the pools directly, the miners are working just that AM cannot see them so I have to reboot them in order for AM to see them. Had this a dozen or so updates ago as well - hope it stops soon. its a pita to restart miners in order to see them in the AM cloud service.
In some cases, this can happen when Antminers mine on a specific pool. It may sound strange, but they can simply stop responding on the API port while they still are mining. Testing with another pool may help.For more details about how to troubleshoot, see:
https://support.awesomeminer.com/support/solutions/articles/35000094734-troubleshooting-antminer-and-asic-miners
March 22, 2019, 05:37:13 PM
Hi, Patrick. It seems that the www.coincalculators.io API signals have changed, all the numbers are not correct. Current Revenue (BTC / day) instead of USD
It's correct that there have been API changes and I've received information from the Coincalculators admin about the changes.Right now you will run into problems if you use "CoinCalculators exchange rate" set to either Highest Bid or Lowest Ask, but from what I can see it should work better with Default.
I will adjust Awesome Miner to these changes.
March 22, 2019, 11:37:51 AM
Probably not useful to very many people, but I've written an Ansible script I use to provision/reprovision my Linux mining boxes with AwesomeMiner
You can execute it with the command: ansible-playbook AM.yml -e "target_host=%YOUR_HOST_NAME%"
You can execute it with the command: ansible-playbook AM.yml -e "target_host=%YOUR_HOST_NAME%"
Code:
--- #Setup AwesomeMiner
- hosts: "{{ target_host }}"
become: yes
gather_facts: yes
tasks:
- name: Run uninstaller
shell: /root/awesomeminer-remoteagent/service-uninstall.sh
- name: Cleanup Previous Installs
shell: rm -rf /home/miner/awesome*
- name: Download AM
get_url:
url: http://www.awesomeminer.com/download/setup/awesomeminer-remoteagent.tar.xz
dest: /home/miner
- name: Extract AM Archive
shell: tar xvJf /root/awesomeminer-remoteagent.tar.xz
- name: Modify Service Script
replace:
path: /root/awesomeminer-remoteagent/awesome.service
regexp: 'home\/user'
replace: 'root'
- name: Run install script
shell: /root/awesomeminer-remoteagent/service-install.sh
args:
chdir: /root/awesomeminer-remoteagent/
- name: Run start script
service:
name: awesome
state: started
enabled: yes
- name: Sync the local filesystem
shell: sync
March 22, 2019, 08:15:40 AM
I can't remove groups under my miners tab. Remove Group is grayed out for every group when I right click the name, even if it's empty with no miners assigned. I'm not trying to remove the default My Miners group, just others.
Screenshot:
Are you sure this isn't the "My Miners" group, but renamed and moved to the bottom?Screenshot:
For the "My Miners" group - Even if you remove all miners from it, rename it and make another group default - you will still be prevented from removing this group.
Is this the only empty group that cannot be removed?
Every group. Every group I try to remove has "Remove" grayed out.
Can you please try:
1) Move the miners from another group you have, for example "top 6-pck", to the group "not". Can you now remove the group "top 6-pck"? If that's the case, "not" was the renamed "MyMiners" group that cannot be removed
2) If the above failed, what happens if you create a new empty group, can you remove that one?
Ok, that worked thanks. That's very un-intuitive, maybe could use an improvement (or inform the user why remove is grayed out). Also, you can't drag and drop miners into an empty group. You have to manually change one miner's group by right clicking and assigning to a group, and then it will let you drop the others under it. That could also use improvement!
Jump to: