Pages:
Author

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 71. (Read 703512 times)

member
Activity: 418
Merit: 21
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  Smiley ). Tested with a fresh profile and a value of 800 and AM shows correctly VL: 800 in the Clocking Profile summary.



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.
member
Activity: 1558
Merit: 69
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

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.
newbie
Activity: 18
Merit: 0
Is it possible to supply the memory temperature sensor reading statistics?
-mvdd=        - Memory voltage, mV (1350 mV by default)  RaveOS
And can I lower it for W10 somehow by means of AM?
legendary
Activity: 3346
Merit: 1094
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
member
Activity: 126
Merit: 10
CPU mining
  - Update library for reading CPU information to improve temperature reading support for Ryzen CPUs

is there a way now to turn the temps on or is it a bug

I don't see any CPU temps after updating to 8.1.4 I have five Ryzen 3900X CPUs.
legendary
Activity: 3346
Merit: 1094
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
legendary
Activity: 3346
Merit: 1094
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.
legendary
Activity: 1754
Merit: 1007
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
legendary
Activity: 3346
Merit: 1094
Hi Patrike
Default defenition for noncerproAMDminer download a wrong version of software from Github for Linux based systems. AM download a windows version. Regards
Hi,
There is only a single version defined for Linux, 3.02, with the following download URL:
https://github.com/NoncerPro/noncerpro-nimiq-opencl/releases/download/v3.0.2/noncerpro-opencl-linux-3.0.2.tar.gz

Can you please go to the Options dialog, Managed Software section and verify if this matches what you see for Noncer Pro AMD? Thanks!
now in AM deault setting is: https://github.com/NoncerPro/noncerpro-nimiq-opencl/releases/download/v3.0.2/noncerpro-opencl-win64-3.0.2.zip
in case if rig on Linux, AM download a Win version of the software. This not happens with CUDA version of noncerpro. Of course, i have overwritten link and solve the problem, but looks like we have small bug.

Please push update for T-Rex, ver 0.18.5 is out.
Regards
Thanks for the details.

I've just pushed a mining software definition update, where T-Rex 0.18.5 is one of the updates.
legendary
Activity: 3346
Merit: 1094
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.
legendary
Activity: 1754
Merit: 1007
Hi Patrike
Default defenition for noncerproAMDminer download a wrong version of software from Github for Linux based systems. AM download a windows version. Regards
Hi,
There is only a single version defined for Linux, 3.02, with the following download URL:
https://github.com/NoncerPro/noncerpro-nimiq-opencl/releases/download/v3.0.2/noncerpro-opencl-linux-3.0.2.tar.gz

Can you please go to the Options dialog, Managed Software section and verify if this matches what you see for Noncer Pro AMD? Thanks!
now in AM deault setting is: https://github.com/NoncerPro/noncerpro-nimiq-opencl/releases/download/v3.0.2/noncerpro-opencl-win64-3.0.2.zip
in case if rig on Linux, AM download a Win version of the software. This not happens with CUDA version of noncerpro. Of course, i have overwritten link and solve the problem, but looks like we have small bug.

Please push update for T-Rex, ver 0.18.5 is out.
Regards
newbie
Activity: 17
Merit: 0
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.
legendary
Activity: 3346
Merit: 1094
Hi Patrike
Default defenition for noncerproAMDminer download a wrong version of software from Github for Linux based systems. AM download a windows version. Regards
Hi,
There is only a single version defined for Linux, 3.02, with the following download URL:
https://github.com/NoncerPro/noncerpro-nimiq-opencl/releases/download/v3.0.2/noncerpro-opencl-linux-3.0.2.tar.gz

Can you please go to the Options dialog, Managed Software section and verify if this matches what you see for Noncer Pro AMD? Thanks!
legendary
Activity: 3346
Merit: 1094
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.
legendary
Activity: 3346
Merit: 1094
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.

legendary
Activity: 1754
Merit: 1007
Hi Patrike
Default defenition for noncerproAMDminer download a wrong version of software from Github for Linux based systems. AM download a windows version. Regards
member
Activity: 418
Merit: 21
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!
newbie
Activity: 17
Merit: 0
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.
legendary
Activity: 3346
Merit: 1094
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.
legendary
Activity: 3346
Merit: 1094

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?
Pages:
Jump to: