[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[patrike]

hello, after linux agent update,either MSI or Native Overclocking does not working. This is native OC output.

vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, CoreClockBoost 0 0 -200000 1200000 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, MemoryClockBoost 0 0 -2000000 2000000 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, PowerLimit 100 100 50 133 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, FanSpeed 40 40 0 100 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] GetClockingSettings returning GPU: 6:6:NVIDIA GeForce GTX 1070 Ti, 4                                                                           AbParameters
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, CoreClockBoost 0 0 -200000 1200000 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, MemoryClockBoost 0 0 -2000000 2000000 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, PowerLimit 100 100 50 133 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, FanSpeed 40 40 0 100 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] GetClockingSettings returning GPU: 7:7:NVIDIA GeForce GTX 1070 Ti, 4                                                                           AbParameters
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.949 [032] Updating settings
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Managed Miners:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: [ManagedMiner#3 - AGAT 21 [8x1070Ti] [MSI]]: BMiner
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Clocking Profile:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Active Miners:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: [3] IsAttached: True, PID: 1398, InstanceId: 1
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Saving configuration to: /root/.local/share/AwesomeMiner       Service/ServiceData.xml.tmp
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.953 [032] --> /root/.local/share/AwesomeMinerService/ServiceData.x       ml
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, CoreClockBoost 0 0 -200000 1200000 T       rue
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, MemoryClockBoost 0 0 -2000000 200000       0 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, PowerLimit 100 100 50 133 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, FanSpeed 40 40 0 100 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] GetClockingSettings returning GPU: 0:0:NVIDIA GeForce GT       X 1070 Ti, 4 AbParameters
vas. 19 10:44:40 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:40 AM.456 [032] NV:GetAbGpu GPU: 1, CoreClockBoost 0 0 -200000 1200000 T       rue
vas. 19 10:44:40 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:40 AM.456 [032] NV:GetAbGpu GPU: 1, MemoryClockBoost 0 0 -2000000 200000       0 True

The setting in Awesome Miner for Native Overclocking or MSI Afterburner is only applicable from Windows. On Linux the overclocking is only made in one way no matter how this setting is configured.

Can you please send me the lines where the actual overclocking is performed. It should say something like "NV:SetValues" followed by "NV:ExecuteCommand". The command listed here can be used for troubleshooting. Thanks!

[1713878859]

1713878859

[1713878859]

1713878859

[1713878859]

1713878859

[1713878859]

1713878859

[1713878859]

1713878859

[1713878859]

1713878859

[iceTony]

hello, after linux agent update,either MSI or Native Overclocking does not working. This is native OC output.

vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, CoreClockBoost 0 0 -200000 1200000 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, MemoryClockBoost 0 0 -2000000 2000000 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, PowerLimit 100 100 50 133 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, FanSpeed 40 40 0 100 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] GetClockingSettings returning GPU: 6:6:NVIDIA GeForce GTX 1070 Ti, 4                                                                           AbParameters
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, CoreClockBoost 0 0 -200000 1200000 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, MemoryClockBoost 0 0 -2000000 2000000 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, PowerLimit 100 100 50 133 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, FanSpeed 40 40 0 100 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] GetClockingSettings returning GPU: 7:7:NVIDIA GeForce GTX 1070 Ti, 4                                                                           AbParameters
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.949 [032] Updating settings
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Managed Miners:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: [ManagedMiner#3 - AGAT 21 [8x1070Ti] [MSI]]: BMiner
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Clocking Profile:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Active Miners:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: [3] IsAttached: True, PID: 1398, InstanceId: 1
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Saving configuration to: /root/.local/share/AwesomeMiner       Service/ServiceData.xml.tmp
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.953 [032] --> /root/.local/share/AwesomeMinerService/ServiceData.x       ml
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, CoreClockBoost 0 0 -200000 1200000 T       rue
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, MemoryClockBoost 0 0 -2000000 200000       0 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, PowerLimit 100 100 50 133 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, FanSpeed 40 40 0 100 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] GetClockingSettings returning GPU: 0:0:NVIDIA GeForce GT       X 1070 Ti, 4 AbParameters
vas. 19 10:44:40 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:40 AM.456 [032] NV:GetAbGpu GPU: 1, CoreClockBoost 0 0 -200000 1200000 T       rue
vas. 19 10:44:40 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:40 AM.456 [032] NV:GetAbGpu GPU: 1, MemoryClockBoost 0 0 -2000000 200000       0 True

The setting in Awesome Miner for Native Overclocking or MSI Afterburner is only applicable from Windows. On Linux the overclocking is only made in one way no matter how this setting is configured.

Can you please send me the lines where the actual overclocking is performed. It should say something like "NV:SetValues" followed by "NV:ExecuteCommand". The command listed here can be used for troubleshooting. Thanks!

Ok, managed to setup OC over "Options>GPU Clocking Profile" and set it to "Manage Template >GPU Clocking Profile" its not practical, if need to set up multiple different gpu rigs.
Still having issues when entering GPU Clocking... from main screen. "Miner Service going offline, online 3-4 times, still Couldn't get information about GPU's of selected miner, miner process does not interupt.
4 AbParameters
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.375 [004] [W]TaskTimer::Elapsed
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.717 [017] NV:GetAbGpu GPU: 2, CoreClockBoost 130000 0 -200000 1200000 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] NV:GetAbGpu GPU: 2, MemoryClockBoost 450000 0 -2000000 2000000 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] NV:GetAbGpu GPU: 2, PowerLimit 65 100 50 133 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] NV:GetAbGpu GPU: 2, FanSpeed 40 40 0 100 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] GetClockingSettings returning GPU: 2:2:NVIDIA GeForce GTX 1070 Ti, 4 AbParameters
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.512 [017] NV:GetAbGpu GPU: 3, CoreClockBoost 130000 0 -200000 1200000 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] NV:GetAbGpu GPU: 3, MemoryClockBoost 450000 0 -2000000 2000000 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] NV:GetAbGpu GPU: 3, PowerLimit 65 100 50 133 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] NV:GetAbGpu GPU: 3, FanSpeed 40 40 0 100 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] GetClockingSettings returning GPU: 3:3:NVIDIA GeForce GTX 1070 Ti, 4 AbParameters

[soothaa]

Native overclock is the BEST!

[patrike]

hello, after linux agent update,either MSI or Native Overclocking does not working. This is native OC output.

vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, CoreClockBoost 0 0 -200000 1200000 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, MemoryClockBoost 0 0 -2000000 2000000 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, PowerLimit 100 100 50 133 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] NV:GetAbGpu GPU: 6, FanSpeed 40 40 0 100 True
vas. 19 10:24:12 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:12 AM.44                                                                          7 [011] GetClockingSettings returning GPU: 6:6:NVIDIA GeForce GTX 1070 Ti, 4                                                                           AbParameters
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, CoreClockBoost 0 0 -200000 1200000 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, MemoryClockBoost 0 0 -2000000 2000000 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, PowerLimit 100 100 50 133 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] NV:GetAbGpu GPU: 7, FanSpeed 40 40 0 100 True
vas. 19 10:24:13 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:24:13 AM.69                                                                          4 [011] GetClockingSettings returning GPU: 7:7:NVIDIA GeForce GTX 1070 Ti, 4                                                                           AbParameters
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.949 [032] Updating settings
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Managed Miners:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: [ManagedMiner#3 - AGAT 21 [8x1070Ti] [MSI]]: BMiner
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Clocking Profile:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Current list of Active Miners:
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: [3] IsAttached: True, PID: 1398, InstanceId: 1
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.950 [032] Saving configuration to: /root/.local/share/AwesomeMiner       Service/ServiceData.xml.tmp
vas. 19 10:44:35 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:35 AM.953 [032] --> /root/.local/share/AwesomeMinerService/ServiceData.x       ml
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, CoreClockBoost 0 0 -200000 1200000 T       rue
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, MemoryClockBoost 0 0 -2000000 200000       0 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, PowerLimit 100 100 50 133 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] NV:GetAbGpu GPU: 0, FanSpeed 40 40 0 100 True
vas. 19 10:44:39 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:39 AM.263 [032] GetClockingSettings returning GPU: 0:0:NVIDIA GeForce GT       X 1070 Ti, 4 AbParameters
vas. 19 10:44:40 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:40 AM.456 [032] NV:GetAbGpu GPU: 1, CoreClockBoost 0 0 -200000 1200000 T       rue
vas. 19 10:44:40 aga AwesomeMiner.RemoteAgent.Linux[900]: 2/19/19 10:44:40 AM.456 [032] NV:GetAbGpu GPU: 1, MemoryClockBoost 0 0 -2000000 200000       0 True

The setting in Awesome Miner for Native Overclocking or MSI Afterburner is only applicable from Windows. On Linux the overclocking is only made in one way no matter how this setting is configured.

Can you please send me the lines where the actual overclocking is performed. It should say something like "NV:SetValues" followed by "NV:ExecuteCommand". The command listed here can be used for troubleshooting. Thanks!

Ok, managed to setup OC over "Options>GPU Clocking Profile" and set it to "Manage Template >GPU Clocking Profile" its not practical, if need to set up multiple different gpu rigs.
Still having issues when entering GPU Clocking... from main screen. "Miner Service going offline, online 3-4 times, still Couldn't get information about GPU's of selected miner, miner process does not interupt.
4 AbParameters
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.375 [004] [W]TaskTimer::Elapsed
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.717 [017] NV:GetAbGpu GPU: 2, CoreClockBoost 130000 0 -200000 1200000 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] NV:GetAbGpu GPU: 2, MemoryClockBoost 450000 0 -2000000 2000000 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] NV:GetAbGpu GPU: 2, PowerLimit 65 100 50 133 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] NV:GetAbGpu GPU: 2, FanSpeed 40 40 0 100 True
vas. 19 15:50:56 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:50:56 PM.718 [017] GetClockingSettings returning GPU: 2:2:NVIDIA GeForce GTX 1070 Ti, 4 AbParameters
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.512 [017] NV:GetAbGpu GPU: 3, CoreClockBoost 130000 0 -200000 1200000 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] NV:GetAbGpu GPU: 3, MemoryClockBoost 450000 0 -2000000 2000000 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] NV:GetAbGpu GPU: 3, PowerLimit 65 100 50 133 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] NV:GetAbGpu GPU: 3, FanSpeed 40 40 0 100 True
vas. 19 15:51:01 aga AwesomeMiner.RemoteAgent.Linux[878]: 2/19/19 3:51:01 PM.513 [017] GetClockingSettings returning GPU: 3:3:NVIDIA GeForce GTX 1070 Ti, 4 AbParameters

Thanks for the update on this.

In case you need different clockings per GPU you can create Clocking Profile Groups. See:
https://support.awesomeminer.com/support/solutions/articles/35000086015-gpu-overclocking

Could you please send me the complete Remote Agent log file for this scenario? In the attached lines above, there are still only information related to when Awesome Miner is reading the current clocking settings, not any command to actually set the clocking. Please also send me the Awesome Miner log file (toolbar: Tools -> Log File) for this period of time. Thanks!

[patrike]

Native overclock is the BEST!

Thanks for the very nice feedback. It's supposed to be Awesome - or at least make it easier and faster to perform the common overclocking operations.

[MoparMiningLLC]

Can you please check if the behavior goes away if you take one of the Antminers and change to another pool? Just to confirm if it's the same problem or something else. Thanks!

I forgot that not all miners are on Kano - I do have one miner that is on Slushpool, it has also had the same issue, just less frequently as it is only one miner.

Patrike - I wanted to let you know that I have not had this problem at all since your last update to the AM software. I made no changes to any settings but it has not occurred since the last update.

[trucobit]

Hello Patrike, I have another idea or suggestion.

It would be in COINS when double clicking on a coin, so that there is no doubt I have put a capture.

We can choose in options the order of information providers, but it is a simple list of 4 providers. Who gives more information is that we indicate first. The problem is that some Cointomine coins are wrong, but in Coinscalculator they are fine, and vice versa.

It would be interesting to add a selector and choose for each currency the provider, or that is by default. It would also be nice that even if you choose to use an example for a coin for Coinscalculator, just obtain the mining data, and obtain the data from the supplier's exchanges for more data.

Usually CTM gives many more exchanges than CC, but CTM also has many coins with the wrong calculation, I have to record every day 1 or 2 currency corrections. I can choose the data of CC but the exchanges of which more information gives is CTM. In a more advanced system there would be two selectors, one for the mining data (hash, difficulty, reward, block, ticker, AL-GO) and another selector to choose the supplier for the prices.

However, CC is usually more accurate with the currency data, but bad with the prices, has problems when it comes to scratching the prices of the exchanges, and keeps the same price for hours or days, however that part CTM does fairly good.

You could have a currency with the CC hash data and the CTM price data. But a priori, with only being able to choose for now the exchange for currency and would be a great control of how we mine.

Just think that the more control we have, the better we mine. I give you a practical example. GRIN the hash data is correct in DC more or less, but in CTM KArlo has tried to adjust it by varying the blocking time to 1.5, when the block is 1 minute. Even so and making a test of 24 hours, the profit must be changed to 2 to bring it closer to reality. This calculation was made by extracting samples every 15 minutes of coins per day from AM, to then obtain an average, and then see how many I have obtained, the real profit was 2.1, I left it in 2. And then I have mined and it is quite accurate what estimated by AM and what was actually obtained

So I say that you can get the best of both worlds by choosing exchange as a minimum, and better yet, a selector for the data and another for the prices, in each currency.

I know that I propose things that may be difficult to perform, because it implies a deeper work with the suppliers' apis.

Thanks for the input. I suppose there are two ways forward. The easiest (to understand as a user and to configure as a user) would be to allow you to override the coin stats provider per coin if needed. Mixing properties from multiple providers would be for a very few number of users and would be easy to get wrong.

I will note and consider this feature suggestion.

There is always the option to put it by default, in a special section and with an information icon.

[patrike]

Can you please check if the behavior goes away if you take one of the Antminers and change to another pool? Just to confirm if it's the same problem or something else. Thanks!

I forgot that not all miners are on Kano - I do have one miner that is on Slushpool, it has also had the same issue, just less frequently as it is only one miner.

Patrike - I wanted to let you know that I have not had this problem at all since your last update to the AM software. I made no changes to any settings but it has not occurred since the last update.

Thanks for the update on this. There are however no changes made to Awesome Miner for this. There can still be an issue that the miner, at random times, start to behave like this.

What you could try next time it happens is to use a tool like Microsoft PsPing, where you can test the connection to the monitoring interface (API) port 4028 on the Antminer. It's a good way of testing an Antminer.

[patrike]

Awesome Miner version 6.2.1

 GPU mining
  - Native Overclocking: nVidia target temperature enforced in more scenarios
  - Added additional algorithms
 Integration
  - Nicehash MTP pool included
 Configuration
  - The setting for automatic column size is now applied for the Miners and Balance tabs as well
 Mining software
  - Gminer 1.33
  - XMRig 2.12
  - SrbMiner 1.7.8
  - Grin Pro Miner 1.2
  - Ethminer 0.17.1 rc0
 Corrections
  - Correction to Ubqhash calculations for coins per day

Note: BMiner 15.0 is not yet included because it was a number of users having issues with that release.

[dulama]

Hi,

Can you add Algorithm "Cryptonight GPU" ?

Thanks,
Vlad

[MoparMiningLLC]

Thanks for the update on this. There are however no changes made to Awesome Miner for this. There can still be an issue that the miner, at random times, start to behave like this.

What you could try next time it happens is to use a tool like Microsoft PsPing, where you can test the connection to the monitoring interface (API) port 4028 on the Antminer. It's a good way of testing an Antminer.

maybe you did not do something directly but maybe something else that was adjusted would affect this indirectly? I only had it happen for a few months and then it stopped now 2 updates ago I think. I have not adjusted anything on the miners at all nor affected any changes on their pools.

Remember the miners never stopped working nor did the pool ever stop accepting the miners work, only that AM would lose its connection and thus report the miner offline.

Either way, I am happy to see that the issue is gone.

[trucobit]

Command line arguments:  -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u 3CGJUpDgyez4Zn4QG8M3sa5CYM5p9p87ux.minero5 -p x --no-watchdog  -b 0.0.0.0:4028
there error when mining MTP in nicehash, I believe that 0.0.0.0 is not correct but I can not change it. Anyway, it does not work, neither in tt-miner etc ...

[sxemini]

Command line arguments:  -a mtp -o stratum+tcp://mtp.eu.nicehash.com:3374 -u 3CGJUpDgyez4Zn4QG8M3sa5CYM5p9p87ux.minero5 -p x --no-watchdog  -b 0.0.0.0:4028
there error when mining MTP in nicehash, I believe that 0.0.0.0 is not correct but I can not change it. Anyway, it does not work, neither in tt-miner etc ...

0.0.0.0 is right. It says only that it use the local IP and the 4028 is the port for awesomeminer. What error?

EDIT:

I think it is a problem from the specified mining software (cryptodredge, TTminer) and not from awesomeminer. It cannot handle the BTC address form i think.
See the last post in cryptodredge thread:
https://bitcointalk.org/index.php?topic=4807821.720

[darkneorus]

Awesome Miner version 6.2.1

 GPU mining
  - Native Overclocking: nVidia target temperature enforced in more scenarios
  - Added additional algorithms
 Integration
  - Nicehash MTP pool included
 Configuration
  - The setting for automatic column size is now applied for the Miners and Balance tabs as well
 Mining software
  - Gminer 1.33
  - XMRig 2.12
  - SrbMiner 1.7.8
  - Grin Pro Miner 1.2
  - Ethminer 0.17.1 rc0
 Corrections
  - Correction to Ubqhash calculations for coins per day

Note: BMiner 15.0 is not yet included because it was a number of users having issues with that release.

GMiner 1.33 supports Beam mining on AMD GPUs, now it causes issues on mixed AMD/NVIDIA rigs because it always tries to use all AMD cards too.

[trucobit]

https://github.com/nicehash/Specifications/blob/mtp/MTP_NiceHash_v1.0.txt


how to FIX MTP nicehash

[mnanut]

Gminer 1.33 for Equihash 150.5 (BEAM) no longer works for me on windows 64bit.

Prior to the update it worked.

[atomicrulez]

I can also verify that MTP mining on NiceHash with CryptoDredge or TT-Miner results in only rejected shares. Thanks for trying to update it though. I would suggest using the special version of ccminer that is being run with NiceHash Miner Legacy v1.9.0.15 which says this when you first run it:
*** ccminer 1.1.12-djm34 for nVidia GPUs by djm34 ***
    Built with VC++ 2015 and nVidia CUDA SDK 10.0

Originally based on Christian Buchner and Christian H. project based on tpruvot 1.8.4 release
Include algos from alexis78, djm34, sp, tsiv and klausT.
*** News (07/06/2018): MTP algo for ZCoin

[patrike]

Hi,

Can you add Algorithm "Cryptonight GPU" ?

Thanks,
Vlad

Yes, this one will be added in the next release.

[patrike]

GMiner 1.33 supports Beam mining on AMD GPUs, now it causes issues on mixed AMD/NVIDIA rigs because it always tries to use all AMD cards too.

I noticed the very latest version of GMiner (v1.34) now includes a command line flag where it's possible to disable nVidia or AMD GPU's. On Gminer 1.34 you will be able to use:
1) To only use AMD and disable nVidia CUDA:
--cuda 0
2) To only use nVidi and disable AMD OpenCL:
--opencl 0

I will of course include Gminer 1.34 in the next update. I will also make sure the default profit profiles includes these command line arguments for new installations - however, Awesome Miner will not go in and automatically modify any GMiner command line on existing installations.

[patrike]

I can also verify that MTP mining on NiceHash with CryptoDredge or TT-Miner results in only rejected shares. Thanks for trying to update it though. I would suggest using the special version of ccminer that is being run with NiceHash Miner Legacy v1.9.0.15 which says this when you first run it:
*** ccminer 1.1.12-djm34 for nVidia GPUs by djm34 ***
    Built with VC++ 2015 and nVidia CUDA SDK 10.0

Originally based on Christian Buchner and Christian H. project based on tpruvot 1.8.4 release
Include algos from alexis78, djm34, sp, tsiv and klausT.
*** News (07/06/2018): MTP algo for ZCoin

I've also verified with this Ccminer MTP and it works fine with Nicehash:
https://github.com/zcoinofficial/ccminer

We will most likely see improved Nicehash support for CryptoDredge and TT-Miner soon, based on the discussions in those forum threads.