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

Hey Patrik,

just testing my new boards with 13 cards and the native overclocking, especially the clocking profile groups. Because Afterburner cant handle more than 8 cards.

This is the problem:
- I have a mixed rig with for example 13 cards of 1060s, 1070s and 1080s. One (or more) cards are lost for whatever reason, like crashed, or dropped by windows, or anything else. So only 12 cards are available. The lost card is one of the 1080s with ID 6.
- Because of the lost ID there are only ID 0-11 left. ID 6 is now replaced with another card, for example a 1070 (which was ID 7 previously).
- I have integrated 3 different 1080s clocking profiles into 1 clocking profile group with their ID. Because the 1080 have to clock different and not exactly the same. And I also have different 1060s and 1070s profiles into 1060s and 1070s groups for the same reason.

If now the card with ID 6 is lost, every ID change. The overclocking of AM now clocks the new ID 6 (which is a 1070) with the settings of the 1080 (which is lost). But this will make the system unstable.
Also the GPU selection (in the properties) gets confused and everything gets completely wrong.

I hope you understand, its complicated to describe.

In the clocking profile groups I can edit the GPU expression by the name, but only like 1060, 1070, 1080... So AM would clock every 1080 the same.
Is it somehow possible to edit this expression field more complex? Like nvidia 1080 or asus 1070? If AM cant find that device (because something happend or it is just disabled), then AM just ignors that device for the clocking. AM already can read the GPU details like:
4 (4):GeForce GTX 1080
PCI BusId: 9
PCI Id Device: 7040
PCI Id SubDevice: 0x119E10DE
Subvendor Name: NVIDIA

Dunno if the SubDevice is unique to a specific card. If yes, this would be awesome to use in the expression field. If not, Vendor and Name together would be nice for a good start

PAtrike already sent you 2 internal messages with 3 logs so you have all the possible information.

I'm pretty sure that the failures are causing the latest security version of windows version 1809. It is easy to ask here if those who have older versions of Windows like the 1705 have problems with restarting the machines and if those who have updated the windows today have the problem.

ahh ok I did move the one up and it changed it to more accurate values. Though now I miss it telling me that my LTC miners were making $35 a day, even if it wasnt real lol

Hi Ralf,
Thanks for the update. It more sounds like it's an issue related to the actions (SSH reboot) rather than the trigger. Let's investigate why the reboot operation didn't work.

Can you please contact me via e-mail and provide the Awesome Miner log file (toolbar: Tools -> Log File). Please let me know the time of both the reboot issue above and also when you noticed the miner groups issue.
Thanks!

I will send you a PM in a short while where I will request a few more details on this. Discussion of some log file entries is sometimes better via PM as it doesn't have to be shared with everyone. Thanks!

Good point - I agree that this would make it easier. Your suggestion has been noted and I will consider this for future versions.

Thanks for the update. I do understand that you see all the fan speed values in the View Details window. Awesome Miner do list all properties it get from the ASIC miner here, but Awesome Miner do not understand the meaning of all of them. So a property can have the name like "Fan Speed In", but as this name is made up by the ASIC, Awesome Miner doesn't automatically know that it's related to fan speed.

I do however agree that Awesome Miner can be improved here and allow you to point to any property reported by the ASIC miners, for example the Whatsminer specific properties for fan speed, and display this in the Progress field. This is however not supported today and will require some implementation. But it can for sure be supported in the future. I fully understand your point here. Thanks!

If you for example put WhatToMine on top of CoinCalculators.io in the list, you will see that it most likely will load other exchanges. On the same configuration page you can also configure an Exchange Volume Filter, to exclude low volume exchanges that typically cause these problems. By setting a minimum volume to 0.01 or 0.001 BTC it's more likely to get realistic numbers.

I'm considering to set a minimum exchange volume value by default on new installations, to avoid these issues.

Please also note that Awesome Miner uses the Current coin statistics by default, while the web interfaces of the providers like CoinCalculators may use 24h average values.

Possibly, but it has to be optional.

The drawback I see with automatic software updates is that you will not get a chance to have a quick look at the release notes before upgrading. In almost all cases there is no need to read it, but it could be that we need to include an important message on the first line in the release notes.

Hi Patrike,

i have a second issue with the Version 6.5.5.

now i experince the second time, that some Minergroups are just vanished?!
all the miners out of this group are now located in the default-group.

a new start of AM don't help - i have to create the vanished grougs again and have to check all the rules depending on this groups?!
that's really annoying or better said much work...

can you look into this ASAP? do you need some logfiles?

thank you and BR Ralf

Hi Patrike,

additional detail:
also if i execute the rule through Actions-Button (manual-Activation) the miner is not rebooting - if i reboot through the web-Browser, the miner reboots and work fine again...

BR Ralf

It is not a problem of NBMINER, it happens with many more miners, ttminer, trex, basically with all, some more, others less. The only weird thing I'm using are the Nvidia Creator Drivers. Because now there are two versions, the gaming version and the creator version that is for heavier processes such as photoshop, cad etc ...

But I think it has more to do with the version 1809 of windows, since since you update all the computers to this latest version, the thing is even more unstable. I can have 20 restarts per hour with 6 rigs, it's hell. I have to work with very few protocols to minimize failures. My simple conclusions

Aftherburner does not affect, I tried it without it and the same thing happened

4 or 8 gigas of ram, it does not matter, the same happens

It all started with version 1809 and its latest update. All my equipment is in that version including the one that has AM installed

The intelibreeze service is called AM, it gets to consume 100% of CPU when it did not before and when it stops mining it sometimes stays at 50% of CPU with that service and when trying to mine another currency, the miner remains frozen and it reboots. If it is true that happens more with NBMiner because now we are mining much Cuckroo31. But also with other protocols x16s x16r etc ... Sometimes it is mining well and suddenly the miner closes and can not do it right until he restarts the machine.

Something suggests that some changes of the 1809 version is affecting intelibreeze. I have more than 150 failures a day, many more, and each failure is at least 5 minutes without mining, the time of lost mining is incredible

Is there a way to simplify  group profile OC?


Maybe to put group profile to the miner menu, also it would be very good if we could do the oc on each miner and just save a profile for entire miner instead of creating profile from individual OC settings

Dear Patrike
I just want to make it more clear. I can see fan speed on Awesome Miner's Details window (both air-in and air-out fans). From this, I understand the AM can get the fan speed in some ways. So, isn't there any way to show this info on Customization Progress Field.
Thanks in advance.

the ticker at the bottom is not using coincalculators.io - it says it is based on Escodex - which is not on the Statistics Providers page. as for calculating my profit, I am not sure which one it is using. Per coincalculators website, I should be averaging about $7.50 a day for LTC - per AM my per day rate is $11.50 per machine or $34.50 per day.

Automatic update option with email notification ?

Thank you

ahh my confusion then - thought 20 machines was still below the overclocking feature.

Thanks for all feedback and feature requests!

Today you can press a key like 'L' to go to the first coin with a name that starts with this letter. I understand that it's not as advanced as you request, but a general suggestion. This might be a future improvement.

Good for usability and quite easy to do. Can be supported in the future

There are some improvements for the Managed Software configuration that will be part of a development preview next week. You will be able to select CUDA version preferences and select older software versions from a list for example. The result is that you don't have to paste custom URL's so often.

As part of this there will be two additional column where one will display the latest mining software version and the other one the selected version. If they are different, the idea is to highlight it in some way. I think this fulfills your request.

I can look into this, but it should be a quite small correction

The plan is to support more of the popular pools in the future. If any pool operator is reading this and want their pool listed, please let me know. We are however currently not adding pools with very few miners - it needs to be at least a decent number.

Great that it's working fine with the expression!

For the fan speed the Whatsminer do have their own ways of reporting this, so although Awesome Miner receive this for the ASIC miner, it doesn't know how to interpret it. So the fan speed feature you ask for is not yet supported on Whatsminer but I've noted your feature request. Thanks!

Premium Edition (20 miners) includes all overclocking features. Both Native Overclocking and the MSI Afterburner integration. Lower editions doesn't include any overclocking features.