Patrike,
Good day -- Antminer Z11 with the latest firmware from Bitmain and AwesomeMiner 8.1.6 seem to be very creative in the performance calculations.
Thanks for your request. I've replied to your support case for this issue. |
|
|
|
The preferred option is to install Awesome Miner Remote Agent on the Linux system and let Awesome Miner be in full control of starting and running mining: https://support.awesomeminer.com/support/solutions/articles/35000086210-remote-agent-for-linuxIf you don't want to run Remote Agent, you will have to manually configure the mining software you run on HiveOS to run with the monitoring API enabled. The details for how to enable it will depend on the mining software you are running. For PhoenixMiner it's enabled using "-cdmport 3333" and in Awesome Miner you configure your External Miner to connect to "192.168.0.110:3333". |
|
|
|
hi patrike,
any news about the ryzen cpu temp? no temps for ryzen 1x00 and ryzen 2x00 cpu´s. Mining software xmrig and srbminer multi.
I've not been able to reproduce this on my Ryzen 3000-series CPU. I have however added additional debug details for the next version to get a better understanding of the issue. Is the case still that you see the CPU temperature (both "Temperature" and "Core Temperature") in the System tab - but nothing on the CPU tab? Phönixminer 5.2c was released.
I've pushed an update with Phoenix Miner 5.2d now. |
|
|
|
In case some mining software file is corrupt (or removed by Anti-virus software), it can make sense to force a cleanup. Next time you start the mining Awesome Miner will automatically download the mining software again before trying to start it.
I have always been on Windows and in the settings "Managed Software" I can specify the path for the Windows version of the miner. But where to specify the path for another version of the miner for Linux? Thanks for your question. 1) Please go to the Options dialog, Managed Software section. 2) Add a "User defined mining software" 3) Define a name like "Custom XmRig" 4) Define Compatibility "Full" and select the Compatible Software you want to use, for example "XmRig" 5) Select Automatic download and specify the Download URL you want to use In your Managed Miner, please select "Custom XmRig" as the mining software to use. It will use the download URL you defined. |
|
|
|
Patrike, for user defined coins if price will be dynamicly updated in USD, this price will not appear in bottom bar. Its appear if price will be defined in BTC. Is this normal or you can improve for both variants?
You can test it self for Conflux coin.
Thanks for the report. I will look into this case. Pls. push updates for Bminer, T-Rex, Nanominer Regards
I've pushed a number of mining software updates now. |
|
|
|
Patrik, new T-Rex 0.18.7 awaiting new param -w for setting rig name. Can you implement this in next releases? Regards.
I will look into this. Was it only for three of the algorithms -w is supported? |
|
|
|
Hi,
Can someone tell me exactly what does the Clean up all downloaded and uploaded mining software option on the System tools menu due?
Thank
Awesome Miner and Remote Agent downloads mining software (like Claymore Ethereum Miner, XmRig, ...) to your computer when needed. When you click on this menu item Awesome Miner will remove all downloaded mining software from disk. In case some mining software file is corrupt (or removed by Anti-virus software), it can make sense to force a cleanup. Next time you start the mining Awesome Miner will automatically download the mining software again before trying to start it. |
|
|
|
Now i see no temps on all of my ryzen (1200, 1600, 2600x, G2400) In system tab it show me the temp, but status and the CPU tab give only 0°C, with v8.1.4 all works fine.
Thanks for the feedback. I will try to reproduce this. Are you using XmRig or any other CPU mining software? Are all CPU cores reported with 0°C? Hi patrike, i use xmrig and srbminer multi, all show 0 for all cores. And what do you mean: User interface - Organize rule actions with group labels to make it easier to find Where i can organize the rules? Or what do you mean. I find no option or something else. Thanks for the update. I will try to reproduce one more time. About the release note entry about the rule. This is just a user interface change where the menu with all actions are re-structured (changed order, use labels to group different kinds of actions to make them easier to find). It's not a new way to organize the rules - although I do plan to allow for that in the future by introducing some group concept. |
|
|
|
https://ibb.co/0YtxTccIs it possible to change the values of MEM and VDDCI? And when rebooting, it does not keep the values of the fans, puts it on the machine all the time These properties cannot be set explicitly by Remote Agent, but I can look into it as a future improvement. In general, you can define a GPU Clocking Profile for your Managed Miner and it will apply your clocking settings as soon as the miner is started. |
|
|
|
|
Awesome Miner version 8.1.6
GPU mining
- Linux GPU mining: The AMD GPU model name will be displayed more exactly (like 'Radeon RX 5700XT' instead of' Radeon RX 5600/5700/5700XT'). Please check any GPU clocking rules based on device name after the upgrade.
Features
- Web interface includes the operation to Enable or Disable an External Miner
User interface
- Organize rule actions with group labels to make it easier to find
Mining software
- Bminer 16.3.4
- NbMiner 33.3
- SrbMiner 0.5.5
- TT-miner 6.0
- TeamRedMiner 0.7.17
Corrections
- Correction to GPU mapping for T-Rex miner
- Correction to API processing for EthMiner
- Correction to display of Core Voltage Limit for GPU Clocking Profiles in the Options dialog
|
|
|
|
ethminer API timing out, but only on remote agent connectionsI have hundreds of messages like this on the remote agent log per day on my miners(which eventually lead to false positive offline detection): 2020/11/01 6:51:23.796 [016] [E]Failed to process API request (localhost, time: 13006 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstatdetail"}
Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.48 hours ago I started running a script I made that reads the API on localhost every 5 seconds on every miner, I also ran the script 3 times on my machine with each instance pointing to the IP of each miner, the script instances never failed to connect and always took just a few milliseconds everywhere(only once in the 48 hours from my machine one instance took around one second to respond but responded correctly). I made this test with firewall disabled and freshly restarted miners. I tried setting the priority of the remote agent process to high, I don't think it made a difference. This is happening with ethminer 0.17.1 (chosen via awesome miner) and ethminer-0.19.0-7+commit.66186f1b (manually uploaded via awesome miner custom software). Although it seems to happen more on the updated version. I'm not using 0.18.0 (chosen via awesome miner) as it that version of ethminer has a bug that prevents the api from responding. I'm using the later version mainly because 0.17.1 won't show any data while mining, I believe the only data missing when using the later version is the individual progress details for each gpu. Any suggestion on what else I could try? thanks Thanks for the detailed description and for your analysis. So at the same time Remote Agent get a timeout after 13 seconds, your tool connecting to the same EthMiner API is receiving a response without any problems? Do you see a timeout error like this and then it works fine for a while and then another timeout and so on? I will have to look into this a bit more because I cannot see any obvious reason why Remote Agent would timeout if the API is in fact working. For the API data processing, I can make a few adjustments to make sure it parses the API response correctly once received. Correct, my tool never failed to get the API data quickly, I'm using the same command I saw on the logs(miner_getstatdetail) Update: I installed the latest updates for windows 1909 on windows update(security, servicing stack, cumulative and a .net 3.5 update but not edge), after about 10 hours the timeouts seem to be less common, one machine had 0, other 12 and other 16(6 consecutive timeouts once which triggered the offline detection that is set to 60 seconds now). The API was fully responsive all the time on all miners when requesting information from my computer with my tool (every 5 seconds never taking more than a few milliseconds). I'll reformat one miner with latest windows to test when I can. Thanks for the update. If you look at the Windows Defender advanced settings, where all applications are listed - are there any difference between Awesome Miner and your tool? For example the Profile (Private, Public)? |
|
|
|
Patrike, pls add for Bminer for algo Octopus param conflux, in ver. 16.3.4 all works good.
I've pushed an update for this as well. Thanks for the feedback. |
|
|
|
ethminer API timing out, but only on remote agent connectionsI have hundreds of messages like this on the remote agent log per day on my miners(which eventually lead to false positive offline detection): 2020/11/01 6:51:23.796 [016] [E]Failed to process API request (localhost, time: 13006 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstatdetail"}
Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.48 hours ago I started running a script I made that reads the API on localhost every 5 seconds on every miner, I also ran the script 3 times on my machine with each instance pointing to the IP of each miner, the script instances never failed to connect and always took just a few milliseconds everywhere(only once in the 48 hours from my machine one instance took around one second to respond but responded correctly). I made this test with firewall disabled and freshly restarted miners. I tried setting the priority of the remote agent process to high, I don't think it made a difference. This is happening with ethminer 0.17.1 (chosen via awesome miner) and ethminer-0.19.0-7+commit.66186f1b (manually uploaded via awesome miner custom software). Although it seems to happen more on the updated version. I'm not using 0.18.0 (chosen via awesome miner) as it that version of ethminer has a bug that prevents the api from responding. I'm using the later version mainly because 0.17.1 won't show any data while mining, I believe the only data missing when using the later version is the individual progress details for each gpu. Any suggestion on what else I could try? thanks Thanks for the detailed description and for your analysis. So at the same time Remote Agent get a timeout after 13 seconds, your tool connecting to the same EthMiner API is receiving a response without any problems? Do you see a timeout error like this and then it works fine for a while and then another timeout and so on? I will have to look into this a bit more because I cannot see any obvious reason why Remote Agent would timeout if the API is in fact working. For the API data processing, I can make a few adjustments to make sure it parses the API response correctly once received. |
|
|
|
Patrike, please add a Progpow-veil algo to AM for T-Rex and WildRig.
Miner works only with CUDA 10.0 lib
Regards
Thanks for the feedback. I've updated the mining definitions to include this algorithm. |
|
|
|
Edit: Its a T-Rex bug! Just started GMiner to check the GPU tab and it shows the correct ID's 7, 9, 11, even with and without the GPU mapping. Back to T-Rex and its again 9, 11, 11.
Maybe it is the --pci-indexing which is not working properly? Cant test without, but I would bet on it. But its a strange bug. Its just on a few rigs, not all. And it seems only on rigs which are splitted into multiple miners, running all T-Rex. Non-Splitted rigs or rigs with multiple mining software running seems not affected.
Can you please send me the following when mining with T-Rex miner: 1) API-Report (toolbar: Tools -> API Report) 2) GPU details (via the GPU tab, View GPU Details) Please send me the information via PM. Thanks! |
|
|
|
Hi Patrik, found some small bugs. GPU Clocking Profiles / Clocking Profiles / Properties Originally the core voltage limit was on auto. Now i switched to a fixed value, in this example 800. AM will apply the correct 800 mV from the profile to the card. But just shows the old "Auto" value in the Clocking Profiles summary. Its clearly just a display error (but annoying  ). Tested with a fresh profile and a value of 800 and AM shows correctly VL: 800 in the Clocking Profile summary.  Thanks, I will correct this one. And below in AM in the GPU tab, dunno why, but on some rigs AM shows the wrong PCI Bus ID's. Even a reload shows the same wrong ID's. All that wrong rigs running on Win 10 with T-Rex, maybe you need that info. Everything in AM is working correctly, it just shows the wrong ID's. Maybe its also just a display error. If you need something to help fixing this, let me know.
Left picture should be ID 7, 9, 11. Right picture should be ID 2, 12.
Edit:
GPU Clocking / View GPU details shows the correct ID's. Map to system monitoring also shows the correct ID's. Its just the summary which shows wrong numbers.
In this case I see you manually defined the GPU order, so the order will depend on what you defined in the GPU mapping dialog. What is the result if you open the GPU mapping dialog and uncheck the first checkbox? In this case Awesome Miner will automatically try to resolve this. Do you still see the same problem after making this change? |
|
|
|
Now i see no temps on all of my ryzen (1200, 1600, 2600x, G2400) In system tab it show me the temp, but status and the CPU tab give only 0°C, with v8.1.4 all works fine.
Thanks for the feedback. I will try to reproduce this. Are you using XmRig or any other CPU mining software? Are all CPU cores reported with 0°C? |
|
|
|
|
Awesome Miner version 8.1.5
GPU mining
- Added the EtcHash algorithm to support the upcoming changes for Ethereum Classic
CPU mining
- Improved detection of number of cores for AMD Ryzen
Mining software
- Lolminer 1.12
- Nanominer 1.12
Corrections
- Correction to Ryzen temperature display
|
|
|
|
|
Awesome Miner version 8.1.4
GPU mining
- Improved clocking and voltage support for older AMD GPUs on Linux
- Display of voltage for more kinds of AMD GPUs on Linux
- GPU Clocking Groups can be configured to match multiple mapping conditions per GPU
- Support for selecting and detecting nVidia CUDA version 11.1
CPU mining
- Update library for reading CPU information to improve temperature reading support for Ryzen CPUs
Features
- Trigger for checking pool shares and hardware errors in percent has been improved to also check for a specific number of hardware errors
- Easier to edit GPU Clocking Profiles via the GPU Clocking tab
Integration
- Wallet balance for SiaPrime (SCP)
Mining software
- TeamRedMiner 0.7.16c
- NbMiner 33.1
- T-Rex miner 0.18.5
Corrections
- Correction to MAC address reading from Whatsminer ASIC
|
|
|
|
Patrike, Managed Software section do not have option to set CUDA 11.1
the driver 450.80.02 supported CUDA 11.1
if i set in Managed Software section CUDA to "Latest available" it will not generate properly download link to miner software compiled for CUDA 11.1
you can see this problem with latest T-Rex 0.18.5
Github offer t-rex-0.18.5-linux-cuda11.1.tar.gz but AM not generate the link to this file. Only help adding a custom link.
I am on AM ver. 8.1.1 Please check. Regards
I noticed the definitions we have for T-Rex didn't include the Cuda 11.1 version. I've pushed a new update for this one. Awesome Miner v8.1.4 will soon be release and this version will also let you specify Cuda 11.1 explicitly if needed. |
|
|
|
|
Show Posts
