Patrike, can you please implement a easy way to execute a linux commands from AM profit profile. At the moment i have a problem if i use miners command --lock-cclock
After using this command and later after switching to other mining programm GPU core clock still have value from last --lock-cclock call. But not ervery mining programm have option to lock core clock. If once core clock was locked, i cant change values with simple overclocking. This state must be reseted. Only a way to use a "nvidia-smi -rgc" command before or after mining process. But at the moment AM not have possibility to run commands on Linux side without opening separate cmd process window. Even this command:
plink -no-antispoof -ssh [email protected] -pw myPassword sudo nvidia-smi -rgc (plink is a part of putty installation package)
not work from "ProfitProfile->Batch commands" section, but work perfect from cmd window.
I have try to execute a simple windows command: C:\Windows\System32\cmd.exe to test if something happens in ProfitProfile->Batch commands. Its happens nothing. CMD window will not be opened. For which commands type this "batch commands fields" is? Cant find documentation for that.
Regards.
Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 43. (Read 703512 times)
July 25, 2021, 08:42:32 AM
July 24, 2021, 04:20:38 PM
Hi Patrike, if i try to download a custom version of MiniZ miner for Linux, the system create wrong file (?smd_process_download=1&download_id=4427_1) instead of normal .gz archive.
Reagards
All built-in versions of MiniZ will give proper ZIP/GZ filenames. If you point to a custom file on the MiniZ web site, they are actually named strangely like in your example. I assume the extract process might fail here.Reagards
July 23, 2021, 09:48:18 AM
Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Hello,The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Can you please try to combine it with the trigger "Mining uptime"? This trigger can be used to ensure the mining software has been running for a few minutes. You can have these two triggers (Device Property + Mining uptime) and "Match all" configured in your rule.
So you have one Managed Miner and one Managed Profit Miner? In case of GPU issues, a reboot will affect both miners. Isn't a reboot what you want in case of GPU issues or what is the behavior you would like to see here?
July 23, 2021, 06:44:05 AM
Hi Patrike, if i try to download a custom version of MiniZ miner for Linux, the system create wrong file (?smd_process_download=1&download_id=4427_1) instead of normal .gz archive.
Reagards
All built-in versions of MiniZ will give proper ZIP/GZ filenames. If you point to a custom file on the MiniZ web site, they are actually named strangely like in your example. I assume the extract process might fail here. Reagards
July 23, 2021, 06:31:44 AM
Thank you for updating L3+ Awesome miner firmware to 3.8.8, the fan fix was very important.
Is there a firmware 3.8.8 changelog? I don't see it anywhere.
The firmware change log isn't listed on the web site but I'm providing it below.Is there a firmware 3.8.8 changelog? I don't see it anywhere.
Antminer L3 + / L3 ++ 3.8.8
1) Fixed configuration of restart timer.
2) Correction to Find Miner (LED Flash)
3) Improved fan speed control
4) Minor corrections
July 23, 2021, 06:22:17 AM
Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Hello,The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Can you please try to combine it with the trigger "Mining uptime"? This trigger can be used to ensure the mining software has been running for a few minutes. You can have these two triggers (Device Property + Mining uptime) and "Match all" configured in your rule.
So you have one Managed Miner and one Managed Profit Miner? In case of GPU issues, a reboot will affect both miners. Isn't a reboot what you want in case of GPU issues or what is the behavior you would like to see here?
July 23, 2021, 12:27:04 AM
Hi Patrike, if i try to download a custom version of MiniZ miner for Linux, the system create wrong file (?smd_process_download=1&download_id=4427_1) instead of normal .gz archive.
Reagards
Reagards
July 22, 2021, 01:30:53 AM
Thank you for updating L3+ Awesome miner firmware to 3.8.8, the fan fix was very important.
Is there a firmware 3.8.8 changelog? I don't see it anywhere.
Is there a firmware 3.8.8 changelog? I don't see it anywhere.
July 21, 2021, 04:26:47 AM
Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Hello,The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Can you please try to combine it with the trigger "Mining uptime"? This trigger can be used to ensure the mining software has been running for a few minutes. You can have these two triggers (Device Property + Mining uptime) and "Match all" configured in your rule.
July 21, 2021, 02:59:59 AM
Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Hello,The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
Can you please try to combine it with the trigger "Mining uptime"? This trigger can be used to ensure the mining software has been running for a few minutes. You can have these two triggers (Device Property + Mining uptime) and "Match all" configured in your rule.
July 20, 2021, 07:52:04 PM
Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.
July 20, 2021, 08:20:13 AM
Why downvolt curve? You can set fixed voltages -> makes more sense 
Old habit, I guess, setting voltages along with freq.
July 20, 2021, 07:56:52 AM
Is it possible to set up a downvolt curve in AM, instead of using power limit?
Hi,This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?
Yes, that's it. Would be a very useful feature.
PS Any progress updates on Nvidia mem temperatures, at least in Windows?
Why downvolt curve? You can set fixed voltages -> makes more sense
July 20, 2021, 03:09:34 AM
Is it possible to set up a downvolt curve in AM, instead of using power limit?
Hi,This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?
Yes, that's it. Would be a very useful feature.
PS Any progress updates on Nvidia mem temperatures, at least in Windows?
July 20, 2021, 03:04:34 AM
Also, while trying to upgrade to 8.6 I receive the message like "the installation package is on the network drive which is unavailable" and process terminates. Starting the installation package instead of upgrading from within the software gives the same result. How can I fix this? Everything is on the local drive, of course.
I think this is the uninstall part of the upgrade. The Awesome Miner installer is based on the Windows Installer concept, where the uninstallation requires Windows to keep track of the installed software. In case Windows is unable to perform an upgrade or uninstallation, please use this tool from Microsoft to force the removal.https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed
After removing, run the installer again. All settings will be kept even if you uninstall.
July 20, 2021, 02:32:03 AM
Also, while trying to upgrade to 8.6 I receive the message like "the installation package is on the network drive which is unavailable" and process terminates. Starting the installation package instead of upgrading from within the software gives the same result. How can I fix this? Everything is on the local drive, of course.
July 19, 2021, 05:46:35 AM
Is it possible to set up a downvolt curve in AM, instead of using power limit?
Hi,This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?
Yes, that's it. Would be a very useful feature.
PS Any progress updates on Nvidia mem temperatures, at least in Windows?
July 19, 2021, 02:05:39 AM
Is it possible to set up a downvolt curve in AM, instead of using power limit?
Hi,This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?
July 18, 2021, 12:25:02 PM
Is it possible to set up a downvolt curve in AM, instead of using power limit?
July 17, 2021, 04:19:41 PM
with last update my blackminers f1 cannot connect anymore .
Are the miners showing up as Disconnected or as Mining, but without any details? Have you tried to reboot the miner once to ensure it isn't a miner problem?If you still experience this issue, please send me the API report for this miner via the toolbar Tools -> API Report. Thanks!
Jump to: