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

Awesome Miner version 9.0.5

 ASIC mining
  - Added support for IBeLink BM-S1
  - Added support for Goldshell HS-BOX
  - Reboot of Goldshell ASIC miners. Configure the External Miner property ASIC Hardware and set to Goldshell.
 GPU mining
  - Memory voltage can be set for Radeon 5000-series on Linux
 Features
  - Display of revenue and profit in BTC on the dashboard, in additional to the configured display currency (e.g. USD)
  - Configurable: Display of revenue and profit in BTC for each miner group on the Groups page and Miners page
  - Heat map: Indication for miners with at least one hash board not working
 Integration
  - Support for pool balance via the new Luxor pool platform. Requires API key.
 User interface
  - Display of installed CUDA version on the Summary tab
  - Web: Display of GPU hotspot and memory temperature in mobile mode
 Mining software
  - Bminer 16.4.8
  - Nanominer 3.4.2
  - NbMiner 39.7
  - SrbMiner-Multi 0.8.2
  - TeamBlackMiner 1.22
  - WildRig Miner 0.30.1
  - XmRig 6.15.3
 Correction
  - Correction to display of notifications with additional device information for a selected miner
  - Correction to Lolminer setup when using the algorithm Equihash 192,7
  - Correction to T-Rex miner pool selection in profit switching scenarios when using the algorithms Autolykos2 or Octopus without having Ethereum enabled
  - Correction to connection status for cloud connected miners

I understand your point here. Are you also mining different algorithms so you define clocking settings not only per GPU but also per algorithm? Or are you only mining one single coin/algorithm all the time?

Well, that's the issue I have. Even though all my cards are 3080s I have to use slightly different settings for them being from various manufacturers and cooled differently. As a result at the moment my clocking profiles and profile groups look like a huge mess hard even for myself to sort out what's what.

You can define Clocking Profile Groups (see the Options dialog, GPU Clocking Profiles, where you find the groups as well) looking at the reported GPU Name. This is however the true name of the GPU like "nVidia GeForce RTX 3090", not any custom name you defined yourself.

With the Clocking Profile Groups you can for example define that all GPU names containing "3090" should have one profile or all GPU brands matching "ASUS" should have another profile and so on.

Interesting, I think I saw it somewhere in the manual, OC settings rule based on GPU name?

There are unfortunately no great feature for this today. For a selected miner, on the GPU tab, you do have a button for "Set name", but it's a bit limited at the moment. The name will only be used on the GPU tab itself. A future improvement would be to display it everywhere if defined.

Thanks for the suggestion - I will keep an eye on this one. I has not yet shown up on WhatToMine.

The pool will be ignored in case of multiple crashes or if no shares have been accepted for a while. Crashes should show up in the Notifications tab.

You can also review the ignore settings in the Options dialog, Profit switching section, where you will find "Ignore pools with no accepted shares in (minutes)". You could try to increase the number of minutes here to see if it makes a difference.

How do I assign custom name to each GPU in the rig? I did that a while ago with one of my rigs but totally forgot how to do it, search didn't return any answers. I want to be able to later assign clocking profiles to them based on names (which include manufacturer/model/cooling type)

This seems to have fixed the issue I was having here.

Hi Patrike

could you add a coin called Raptoreum https://raptoreum.com/

Thanks for the help before!

How can I find out why a pool was temporarily disabled from a profit switching miner?
I used the links on the AwesomeMiner website to setup the Kawpow pool at 2Miners but the pool randomly seems to be disabled after a while and I cannot find the reason why.

I will look into this.

Thanks for the details. I noticed that Kawpow wasn't enabled for Miniz at all, so by default Awesome Miner shoudn't even have tried it. I've pushed an updated software definition for Miniz now, to ensure Kawpow is working.

For the other algorithms in your screenshot, they should be working fine and I suspect it could be crashes in the Miniz mining software. If possible, can you share a similar command line for any of those and I can confirm if Awesome Miner launches Miniz correctly in your setup?

Can you please run the diagnostics for this miner? Maybe we can see an error or so.



@patrike

is it possible to show the installed cuda version in summary tab? I think it is useful.

Hi Patrike,

Hope this helps...

The miner (Miniz) fails to start on first run and sometimes fails altogether, this is the report from the fail.



It's not limited to just one algo either with this issue on any pool.


Hope you can find the issue here.

I agree with the point made by sxemini above. When mining on for example on Nicehash the actual coin you are mining can change over time and for this reason a 4 GB GPU may work for some time, but not all the time.

Thanks for your report. Can you please share more details about the scenario where the command line arguments are incorrect? This will help me to track down any issues.

I believe it was trying on Prohashing and Nicehash

Benchmark run on what pool? I think on some profit switching pools, so you need less than 4GB, but for Mining ETH you need over 4GB, because the DAG must fit in the VRam of your card.