Thanks for the details. I've just pushed a mining software definition update, where T-Rex 0.18.5 is one of the updates. |
|
|
|
Using awesome miner firmware, I have a target temperature set of 77 C. My fan runs very quiet, temps creep up to 77, then fans kick on full blast for 3 seconds. Temps go back to 72, and quiet again. Repeat every couple minutes. It's very annoying because I usually have my L3+ running in my house. Can you fix the logic to work like Blissz silent profile (fan will slowly increase speed until stable at target temperature). And then don't decrease speed until there's a delta of 2-3 degrees AND 1 hr has elapsed since last increase (to avoid constant changes in fan speed). The key is reducing changes in fan speed as this increases perceptible noise (your brain drowns out white noise perfectly unless it's constantly changing).
Right now the strategy of jumping to 72-77 deg with fan going from 900 rpm to full blast is very bad for electronics in terms of thermal cycling, and bad for airflow since I have multiple antminers connected to same exhaust area (so if one is randomly going to full blast it will backflow to others that are barely at speed). Need them all nice and stable!
Edit:
Did more testing
It appears that no matter what you set your target temperature to, when it hits 77 C, max fan speeds apply and temporarily override everything for 10 sec.
Set target to 80 C, it will only get to 77 before applying max fans, dropping temp back to 72
Set target to 77 C, it will still get to 77 and apply max fans
Set target to 76, it will be ok at first with gentle fan increases, but then barely jump into 77 ...and jump to full blast
Set target to 75, it will be ok most of the time...gentle fan increases to 75-76, and more rarely bump to 77 and then go full blast still.
Set target to 74, it will sometimes overshoot to 75-76, but small fan increases will stop it from hitting 77, so we're always nice and quiet. Adjustments are still +/-200rpm which is noisy and over shoots the low end.
Set target to 70, it makes very quiet, minor fan adjustments (+/- 20rpm), I like this! Perfect behavior. But I wish I could have my system stay warmer (76 C range) with this small adjustment behavior because I prefer slower 76 C fan load compared to to 70 C fan load.
So I think I found the fix: Undo the 77 C hard coded max fan speed. Since the default target is 65, adding 12 to 65 = 77. If I change target temperature, change max fan speed override to (target)+12. So if I set a target of 75, don't start overriding fast fan speeds until it approaches 87.
Hope that makes sense!
Also if fan check is on, the antminer will restart when hitting 77, and the tuning page says "Fan Err! Disable PIC! Fan1 speed is too low 1770 pwm 100". If I disable fan check, the error goes away and no restart happens. Very weird since this shows up when fans go faster.
Can you please let me know the configured temperature for "Chain disable temp" (the overheat feature)? Please also try to increase this value. The firmware will try to make sure you are at least 10 C below this temperature and can increase the fan speed if needed. By increasing this temperature limit it will be less likely you run into a high fan speed. I had Chain disable temp blank (so default 85). Changed it to 95, but still having same problem. I set target temp to 77, it gets to 78, fans go on full blast for a few seconds, it's then at 72, fans go super low back to 900rpm, then it creeps back up to 78, fans go on full blast again. Thanks for the update. We will use your feedback and comments for future improvements. As for today, there are not really any additional parameters to play around with other than those you already used. |
|
|
|
Hi Patrik,
in the Rules / Check Statistics, there is only a Hardware error %. Is it possible to also add a Hardware error (in numbers)? Most of the other statistics also have the choice between % and real numbers.
Most of the popular miners I use like T-Rex or TRM for example showing real numbers, not the percentages. And so I can do some rules to check the errors and maybe restart the rigs or so.
Thank you!
Hi Joseph, Thanks for the suggestion, I will look into this. |
|
|
|
Using awesome miner firmware, I have a target temperature set of 77 C. My fan runs very quiet, temps creep up to 77, then fans kick on full blast for 3 seconds. Temps go back to 72, and quiet again. Repeat every couple minutes. It's very annoying because I usually have my L3+ running in my house. Can you fix the logic to work like Blissz silent profile (fan will slowly increase speed until stable at target temperature). And then don't decrease speed until there's a delta of 2-3 degrees AND 1 hr has elapsed since last increase (to avoid constant changes in fan speed). The key is reducing changes in fan speed as this increases perceptible noise (your brain drowns out white noise perfectly unless it's constantly changing).
Right now the strategy of jumping to 72-77 deg with fan going from 900 rpm to full blast is very bad for electronics in terms of thermal cycling, and bad for airflow since I have multiple antminers connected to same exhaust area (so if one is randomly going to full blast it will backflow to others that are barely at speed). Need them all nice and stable!
Edit:
Did more testing
It appears that no matter what you set your target temperature to, when it hits 77 C, max fan speeds apply and temporarily override everything for 10 sec.
Set target to 80 C, it will only get to 77 before applying max fans, dropping temp back to 72
Set target to 77 C, it will still get to 77 and apply max fans
Set target to 76, it will be ok at first with gentle fan increases, but then barely jump into 77 ...and jump to full blast
Set target to 75, it will be ok most of the time...gentle fan increases to 75-76, and more rarely bump to 77 and then go full blast still.
Set target to 74, it will sometimes overshoot to 75-76, but small fan increases will stop it from hitting 77, so we're always nice and quiet. Adjustments are still +/-200rpm which is noisy and over shoots the low end.
Set target to 70, it makes very quiet, minor fan adjustments (+/- 20rpm), I like this! Perfect behavior. But I wish I could have my system stay warmer (76 C range) with this small adjustment behavior because I prefer slower 76 C fan load compared to to 70 C fan load.
So I think I found the fix: Undo the 77 C hard coded max fan speed. Since the default target is 65, adding 12 to 65 = 77. If I change target temperature, change max fan speed override to (target)+12. So if I set a target of 75, don't start overriding fast fan speeds until it approaches 87.
Hope that makes sense!
Also if fan check is on, the antminer will restart when hitting 77, and the tuning page says "Fan Err! Disable PIC! Fan1 speed is too low 1770 pwm 100". If I disable fan check, the error goes away and no restart happens. Very weird since this shows up when fans go faster.
Can you please let me know the configured temperature for "Chain disable temp" (the overheat feature)? Please also try to increase this value. The firmware will try to make sure you are at least 10 C below this temperature and can increase the fan speed if needed. By increasing this temperature limit it will be less likely you run into a high fan speed. |
|
|
|
Hi Patrike,
i have a difference in CPU temp only 1 rig. AM says 77°C and Coretemp and AMD Ryzen Master says it have 87°C. CPU is a Ryzen 5 2600x. On other rigs there are no problems (Ryzen 5 1600 temp is right, Ryzen 3 1200 temp is right and on all other Intel CPU´s temp is right)
There are multiple temperature sensors on the CPU, so it may not be the exact same we report as Ryzen Master reports. Awesome Miner prioritize the "CPU Core" and "CPU (Tdie)" sensors, but there are more sensors. If you want, please check with the tool OpenHardwareMonitor where you will see the name of many of the CPU temperature sensors and the reported temperature for each of them. I checked the temperature with OpenHardwareMonitor and it says only 89°C and some lower temps under 70°C and awesomeminer shows 79°C. This is only on the ryzen 5 2600x. Another rig with a ryzen 5 1600 shows 75°C in awesomeminer and 75°C in OpenHardwareMonitor. So there is something wrong. For AMD CPUs, only have a Ryzen 3000-series to test with and I will investigate on that one a bit more. Could you please also try with the older version called "Open Hardware Monitor 0.8.0 Beta", available here: https://openhardwaremonitor.org/downloads/It would be interesting to see if that one reports differently. Via Open Hardware Monitor you can also export as a report via the menu File -> Save Report. Can you please do this for the Ryzen 2600x system and send me via PM? Please also let me know the temperature you consider is correct for the time you created the report. The numbers in Awesome Miner is for one of the reported CPU temperatures sensors (so Awesome Miner isn't making up anything here) but it may not be the sensor most relevant for this specific Ryzen CPU. With the report above I might be able to find out the name of the sensors that would make more sense to display. So i tested with 0.8 beta, this version show no temperature, tested with 0.9.1 and it shows 88°C (AM 78°C), i tested with coretemp and it shows 88°C and the same in HWinfo, it also show 88°C. This is only on my Ryzen 5 2600x, Ryzen 1x00 no problem an intel cpu also ok. I will send you 2 reports. Thanks for sharing all details. I will update our library for reading CPU information and hopefully it will resolve the temperature issue. I don't have access to a Ryzen 2600x, so please let me know your feedback once the next version of Awesome Miner is released. |
|
|
|
I have an ASIC that I would like to use. It is the OW1 that is supposed to mine many algorithms. Does anybody know how I can unlock this thing to mine other algos it supports? Awesome Miner supports it, but haven't gotten that to unlock it yet.
Is there anybody that can help me with this? I have heard it is possible, but can't find any information
Hello. I don't have any first hand experience with this ASIC miner. I know it supports X16r but I'm not sure if it can support additional algorithms as well. Maybe someone else here in the community have more experience? |
|
|
|
|
Awesome Miner version 8.1.3
GPU mining
- Improved support for overclocking of AMD Radeon RX 5000-series on Linux
- Improved auto start procedure for Managed Miners after reboot
Features
- External Miner API endpoint includes MAC address
User interface
- Managed Miner configuration for Device Profile moved to the Advanced section as it not used very often
Mining software
- TeamRedMiner 0.7.14
- Lolminer 1.11, including correction in Awesome Miner for Ethereum hashrate display
- XmRig 6.4
- Gminer 2.29
- T-Rex Miner 0.18.2
Corrections
- Correction to the display of usage in "Time" in the Mining History dialog
|
|
|
|
Can you please share more details about the mining hardware you are using? The log file indicates "AMD Radeon 6540A", but that's a very old laptop GPU with only 0.5GB memory (may not be usable for mining). To correct the connection error message you see in the log file, please go to the Awesome Miner Options dialog, Managed Hosts, modify the host representing your Linux system. Please check the box for "Remote Agent for Linux". hiveos-beta-0.6-157@200909 How to make the adjustment work? https://ibb.co/BspQ7Ythttps://ibb.co/3rvJTyWhttps://ibb.co/wcvqPdHWe will improve the support for overclocking of Radeon 5700 on Linux in the next release. |
|
|
|
Can you please share more details about the mining hardware you are using? The log file indicates "AMD Radeon 6540A", but that's a very old laptop GPU with only 0.5GB memory (may not be usable for mining). To correct the connection error message you see in the log file, please go to the Awesome Miner Options dialog, Managed Hosts, modify the host representing your Linux system. Please check the box for "Remote Agent for Linux". |
|
|
|
lolminer API problem
I am testing lolminer to mine ETH.
look:
As you can see it is not reporting the tempeture, and the hashrate is wrong..
In blu, you can see phonenixminer reporting ok...
Thanks for your report. I will update Awesome Miner to consider the hashrate unit correctly for lolMiner. |
|
|
|
Hi @Sven, I don't know if I've touched something, but something strange happens to me. Creating a Pool Group now I don't get the nicehash and zergpool AL-GOS that I have selected. I had them selected but now they do not appear in the list, only the coins that I have been adding over time appear.
I was working measuring AL-GOS for that I use a pool group and there I select the nicehash or zergpool protocol and then in the miner it indicated to mine that pool group.
I think I have not touched anything, but now when creating a pool group nicehash and zergpool do not appear and I have them selected in the profit with their wallet. A while ago I changed from one to another, and after a while when I went to change they did not appear to me.
I even have groups created that tell me in the list that I have 5 active pools, but when I enter I don't see nicehash or zergpool, it's something strange. I am sorry I cannot provide you with more details to reproduce it.
I add, I look at each miner in the "profit swtiching" tab, all the al-gos of nicehash and zergpool appear, but they still do not appear to select in "pool group" The last thing I did before was to give priority to the different protocols that nicehash was using, 0 higher privilege, 1 lower privilege. It may be that you had two protocols with the same level of privilege. It's the only thing I've done weird today, and then the failure. Can you please go to the Options dialog, Profit Switching section. Is "Make predefined pools available everyone" enabled? When enabled, you should be able to see Nicehash and Zergpool in all locations where Awesome Miner lists the pools. |
|
|
|
is it possible to switch between 2 gpu miners I have created in awesome miner? I figure this would be a profit switching thing but I need to be able to manually control the profit switching parameters which doesn't seem possible.
I mine a coin that uses 3 algorithms. 1 algo for GPU, 1 for CPU, and 1 for ASIC and it rotates so 38% of the time it's GPU, 60% CPU, and 2% ASIC.
So one miner I made mines that 3-Algo coin and I made a second miner to mine other things when the first miner is not mining it's 38%.
The problem right now is that both miners just run equally so I don't get the full hashrate on the 3-algo coin because the other miner is stealing resources.
Thank you for any help.
Thanks for your question. This sounds like a very special case. If the first mining software is doing active mining only 38% of the time, the main question is how Awesome Miner can know when it's mining and when it isn't mining. Is the mining software running all the time, but only get work from the pool 38% of the time, resulting in a hashrate above zero for 38% of the time and a hashrate of 0H/s the remaining time? If it's possible to define a criteria from an Awesome Miner point of view, it should be possible to use the rules in Awesome Miner (Options dialog, Rules section). You could have one rule looking for the scenario when to start the second miner and another rule to look for the scenario when to stop the second miner. The Miner Statistics trigger can be used on the first miner to detect hashrate levels for example. |
|
|
|
Hi Patrike,
i have a difference in CPU temp only 1 rig. AM says 77°C and Coretemp and AMD Ryzen Master says it have 87°C. CPU is a Ryzen 5 2600x. On other rigs there are no problems (Ryzen 5 1600 temp is right, Ryzen 3 1200 temp is right and on all other Intel CPU´s temp is right)
There are multiple temperature sensors on the CPU, so it may not be the exact same we report as Ryzen Master reports. Awesome Miner prioritize the "CPU Core" and "CPU (Tdie)" sensors, but there are more sensors. If you want, please check with the tool OpenHardwareMonitor where you will see the name of many of the CPU temperature sensors and the reported temperature for each of them. I checked the temperature with OpenHardwareMonitor and it says only 89°C and some lower temps under 70°C and awesomeminer shows 79°C. This is only on the ryzen 5 2600x. Another rig with a ryzen 5 1600 shows 75°C in awesomeminer and 75°C in OpenHardwareMonitor. So there is something wrong. For AMD CPUs, only have a Ryzen 3000-series to test with and I will investigate on that one a bit more. Could you please also try with the older version called "Open Hardware Monitor 0.8.0 Beta", available here: https://openhardwaremonitor.org/downloads/It would be interesting to see if that one reports differently. Via Open Hardware Monitor you can also export as a report via the menu File -> Save Report. Can you please do this for the Ryzen 2600x system and send me via PM? Please also let me know the temperature you consider is correct for the time you created the report. The numbers in Awesome Miner is for one of the reported CPU temperatures sensors (so Awesome Miner isn't making up anything here) but it may not be the sensor most relevant for this specific Ryzen CPU. With the report above I might be able to find out the name of the sensors that would make more sense to display. |
|
|
|
Hi Patrike,
i have a difference in CPU temp only 1 rig. AM says 77°C and Coretemp and AMD Ryzen Master says it have 87°C. CPU is a Ryzen 5 2600x. On other rigs there are no problems (Ryzen 5 1600 temp is right, Ryzen 3 1200 temp is right and on all other Intel CPU´s temp is right)
There are multiple temperature sensors on the CPU, so it may not be the exact same we report as Ryzen Master reports. Awesome Miner prioritize the "CPU Core" and "CPU (Tdie)" sensors, but there are more sensors. If you want, please check with the tool OpenHardwareMonitor where you will see the name of many of the CPU temperature sensors and the reported temperature for each of them. |
|
|
|
Hi Patrike,
i want to ask you again about the AM-Firmware: is the Firmware for the S17e and T17e still in Development? and are there Plans for the S19 and S19Pro?!
BR Ralf
Hi Ralf, I was hoping to have a better answer for you, but the S17e/T17e firmware has been delayed. I've been talking to our firmware partner on this and the S17e/T17e firmware is still in development and will be the next supported firmware. |
|
|
|
@Patrike, Please add a "MegaMec" algo for T-Rex 18.1 miner. Algo param name is "megamec"
Regards
I've added this algorithm for T-Rex and WildRig. |
|
|
|
|
Awesome Miner version 8.1.2
ASIC mining
- Improved compatibility with Antminers running custom firmware
Features
- Improved variable support for command line arguments
Mining software
- Gminer 2.28
- SrbMiner 0.5.4
- T-rex Miner 0.18.1
Corrections
- Correction to ASIC pool operations over the Cgminer API
|
|
|
|
@Patrike Looks like i am found a problem with Cortex data displaying. AM use for Cortex algo name "Cortex", but must be "CuckooCycleCortex" WhatToMine API call " https://whattomine.com/coins/329.json" send responce: {"id":329,"name":"Cortex","tag":"CTXC","algorithm":"CuckooCycleCortex","block_time":"13.4344","block_reward":7.0,"block_reward24":7.0,"block_reward3":7.0,"block_reward7":7.0,"last_block":2573695,"difficulty":119112.0,"difficulty24":119049.223744292,"difficulty3":120360.139721957,"difficulty7":119042.176914675,"nethash":8866,"exchange_rate":7.93e-06,"exchange_rate24":7.90119148936163e-06,"exchange_rate3":8.06197634575145e-06,"exchange_rate7":8.08499978309983e-06,"exchange_rate_vol":5.80696497,"exchange_rate_curr":"BTC","market_cap":"$22,625,404","pool_fee":"1.675859","estimated_rewards":"15.082730","btc_revenue":"0.00011961","revenue":"$1.37","cost":"$0.86","profit":"$0.50","status":"Active","lagging":false,"testing":false,"listed":false,"timestamp":1602595861}
I have overriden default "Cortex" coin data with this responce and now displaying of Cortex prce is stable. Hope you fix this in next releases. Regards Awesome Miner should already do this mapping automatically since a few months ago. The WhatToMine algorithm name "CuckooCycleCortex" is mapped to "Cortex" in Awesome Miner. Without any manual mapping, isn't CTXC listed as Cortex in the Coins tab? |
|
|
|
|
Show Posts
