Pages:
Author

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

legendary
Activity: 3346
Merit: 1094
Awesome Miner version 8.2.5

 ASIC mining
  - Whatsminer specific properties can be configured via the ASIC Tools menu
  - Improved compatibility with Whatsminer firmware version 1.3 (January 2021)
 Features
  - Miner graph improved to display Power usage, Revenue per day and Profit per day
  - Heat maps can be defined with a larger maximum size
 Mining software
  - SrbMiner Multi 0.6.5
  - XmRig 6.8.1
  - TeamRedMiner 0.8.1
  - Lolminer 1.21, including use of the new watchdog feature
 Corrections
  - Correction to nVidia GPU clocking on Linux
legendary
Activity: 3346
Merit: 1094
Hi, when i start "Device status marked as dead"

I have a Nvidia but is not selected.
Thanks for sharing the details. No additional error messages before that? I will try the combination of RTX 5700 with TeamRedMiner to see if there are any general problems and get back to you with an update.

The command line looks good in general.

Maybe you could verify the Virtual Memory size in Windows to make sure it's enough?
1) Open Control Panel and go to System
2) Select Advanced system settings
3) Click the Settings button in the Performance section
4) Select the Advanced tab
5) Click the Change button in the Virtual memory section
6) Define at least 20 GB virtual memory size
newbie
Activity: 6
Merit: 0
Hi, when i start "Device status marked as dead"

I have a Nvidia but is not selected.

Initialize diagnostics (4)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 8.2.4
OS: Microsoft Windows 10 Pro 64-bit
GPU Details:
  AMD driver version: 20.11.2
  AMD OpenCL Platform ID: 0
  nVidia driver version: 461.09
  nVidia OpenCL Platform ID: 1
  GPUs: RX 5700 XT, RTX 3070
Prerequisites:
  Microsoft .NET Framework: 4.8
  Microsoft VC++ 2013 runtime installed: Yes
  Microsoft VC++ 2015 runtime installed: Yes
  Microsoft VC++ 2017 runtime installed: Yes
  Microsoft VC++ 2019 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: TeamRedMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Properties: (WindowMode: ConsoleFormat, EngineType: TeamRedMiner, IsProfitMiner: True, RunAsAdmin: False)
====================================================================================================
AppData\Roaming\AwesomeMinerService\teamredminer-v0.8.1-win_1\teamredminer-v0.8.1-win\teamredminer.exe  -a ethash --bus_reorder -d 0 -o stratum+tcp://daggerhashimoto -p x --watchdog_disabled --api_listen=0.0.0.0:4028
====================================================================================================
Mining Engine Process started, PID: 9048
>           Team Red Miner version 0.8.1
> [2021-02-05 09:04:08] Note: failed to enable terminal color support, colors will be disabled.
> [2021-02-05 09:04:11] Auto-detected AMD OpenCL platform 0
> [2021-02-05 09:04:17] Initializing GPU 0.
> [2021-02-05 09:04:21] GPU 0 Passed compute mode and crossfire verification.
> [2021-02-05 09:04:21] GPU 0 Starting tuning.
> [2021-02-05 09:04:21] Watchdog thread starting.
> [2021-02-05 09:04:21] Runtime Command Keys: h - help, s - stats, e - enable gpu, d - disable gpu, q - quit
> [2021-02-05 09:04:21] API initialized on 0.0.0.0:4028
> [2021-02-05 09:04:21] Successfully initialized GPU 0: Navi with 40 CU (PCIe 03:00.0)
> [2021-02-05 09:04:21] GPU 0 DAG allocation trying 8176.0 - 512.0 = 7664.0 MiB.
> [2021-02-05 09:04:21] Pool daggerhashimoto.usa.nicehash.com connecting to address .
> [2021-02-05 09:04:21] Pool daggerhashimoto.usa.nicehash.com successfully connected to address
> [2021-02-05 09:04:22] Pool daggerhashimoto.usa.nicehash.com connection was closed by the pool.
> [2021-02-05 09:04:22] Pool daggerhashimoto.usa.nicehash.com switching to stratum mode.
> [2021-02-05 09:04:22] Dev pool connected and ready.
> [2021-02-05 09:04:22] Pool daggerhashimoto.usa.nicehash.com connecting to address
> [2021-02-05 09:04:22] Pool daggerhashimoto.usa.nicehash.com successfully connected to address
> [2021-02-05 09:04:23] Pool daggerhashimoto.usa.nicehash.com successfully subscribed. (144 ms)
> [2021-02-05 09:04:23] Pool daggerhashimoto.usa.nicehash.com authorization succeeded.
> [2021-02-05 09:04:23] Pool daggerhashimoto.usa.nicehash.com set difficulty to 0.389 (1672 MH)
> [2021-02-05 09:04:23] Pool daggerhashimoto.usa.nicehash.com received new job. (job_id: 00000000049d6ce1, diff 0.389 / 1672 MH)
> [2021-02-05 09:04:26] Pool daggerhashimoto.usa.nicehash.com received new job epoch 393 (variant ethash), cache built in 3.1 secs.
> [2021-02-05 09:04:26] Pool daggerhashimoto.usa.nicehash.com extranonce subscribe succeeded. (3143 ms)
> [2021-02-05 09:04:26] GPU 0 Starting DAG generation for epoch 393 (single buffer mode).
> [2021-02-05 09:04:27] Pool daggerhashimoto.usa.nicehash.com received new job. (job_id: 00000000049d6ce2, diff 0.389 / 1672 MH)
> [2021-02-05 09:04:32] Pool daggerhashimoto.usa.nicehash.com received new job. (job_id: 00000000049d6ce3, diff 0.389 / 1672 MH)
> [2021-02-05 09:04:33] Pool daggerhashimoto.usa.nicehash.com received new job. (job_id: 00000000049d6ce4, diff 0.389 / 1672 MH)
> [2021-02-05 09:04:38] Pool daggerhashimoto.usa.nicehash.com received new job. (job_id: 00000000049d6ce5, diff 0.389 / 1672 MH)
legendary
Activity: 3346
Merit: 1094
Hi Guys, anyone try "team red miner" in Awesome, i'm trying to find the best setting but is not working with my RX 5700. Did you have any command line?

Thanks for help.
Hi. Could this be a GPU driver issue? Do you see any specific error message if you start the miner with the Diagnostics button in the toolbar? Thanks!
newbie
Activity: 6
Merit: 0
Hi Guys, anyone try "team red miner" in Awesome, i'm trying to find the best setting but is not working with my RX 5700. Did you have any command line?

Thanks for help.
legendary
Activity: 3346
Merit: 1094
Hi PatrickE,

Could you clarify in the FAQs if the Awesome Miner GUI can pull down managed miners and install them?  Initially I thought it could, but it looks like you have to do the install first.  Was hoping to use it to pull down PhoenixMiner, but it looks like I have to install it and then add it to Awesome Miner to manage it.  Would be nice if that was in the FAQs.

~Orph3us~
Hi and thanks for your question.

Awesome Miner automatically downloads the mining software. In the Properties of a Managed Miner you will find "Automatic download" (enabled by default). Phoenix Miner will be downloaded as well.

Once you start a Managed Miner, Awesome Miner will automatically download and extract the mining software. If you run into any issues, please start the miner with the Diagnostics button in the toolbar to get more details. Please also verify you don't run any anti-virus software that automatically removes Phoenix Miner.
newbie
Activity: 1
Merit: 0
Hi PatrickE,

Could you clarify in the FAQs if the Awesome Miner GUI can pull down managed miners and install them?  Initially I thought it could, but it looks like you have to do the install first.  Was hoping to use it to pull down PhoenixMiner, but it looks like I have to install it and then add it to Awesome Miner to manage it.  Would be nice if that was in the FAQs.

~Orph3us~
legendary
Activity: 3346
Merit: 1094
Hi Patrike,
Would it be possible for VertHash/new vertcoin algorithm to be added in profit mining/benchmark?
The miner is here https://github.com/CryptoGraphics/VerthashMiner

I am running mine just manually through there but would be nice to have in profit switching Smiley
thank you!
Thanks for the suggestion. It doesn't look like this new mining software provide any monitoring interface (API) yet, so it will not be possible to display the hashrate and similar details in Awesome Miner.
newbie
Activity: 1
Merit: 0
Hi Patrike,
Would it be possible for VertHash/new vertcoin algorithm to be added in profit mining/benchmark?
The miner is here https://github.com/CryptoGraphics/VerthashMiner

I am running mine just manually through there but would be nice to have in profit switching Smiley
thank you!
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 8.2.4

 ASIC mining
  - The operations for LED flash and miner sleep mode will show a progress dialog to indicate the result of these operations
 Features
  - New rule trigger Device Profile for detecting GPU core clock or GPU memory clock
 Mining software
  - XmRig 6.8
  - Lolminer 1.20
  - Gminer 2.44
  - PhoenixMiner 5.5c
 Corrections
  - Corrections to communication interface for Remote Agent on Linux
legendary
Activity: 3346
Merit: 1094
Hi.

If we Flash firmware with 3% on s9s we need to pay license?
Our Antminer S9 firmware with a 3% mining fee doesn't require you to pay for the Awesome Miner license. You only need to sign up for our completely free "Antminer firmware" license on the link below:
https://www.awesomeminer.com/signup

You simply enter your e-mail address and you will get a license that will work as long as you use it together with Antminers running our firmware with the 3% mining fee.
legendary
Activity: 1161
Merit: 1001
Don`t invest more than you can afford to lose
Hi.

If we Flash firmware with 3% on s9s we need to pay license?
legendary
Activity: 1754
Merit: 1007
Hi Patrike, some strange behavior in applying of overclocking settings i see in the last version (8.2.3)
For examle: rig start mining on Octopus algo with PL85% and MEM2000, later switch to ETH where other overclocking settings from Profit profile must be applied, but settings for ETH will not be applied and rig continue mining with settings from Octopus algo. If i mannualy restart mining process, the correct settings will be applied. That happens with all cards types 2080ti, 3070, 3090. And with random rigs.All rigs is Linux (HiveOS) machine. This problem is offten a reason for GPU crashing, where only reboot help. Please check.
Regards
I wasn't able to reproduce this one.

1) Can you please send me the log files for Remote Agent and let me know the time it didn't apply the correct clocking profile?
2) Are you using the new concept with delayed overclocking?
yes, i have used new concept with delayed OC, now i am back to old concept and looks like rigs began working normal. Or this happens when rigs switching back from Nicehash. Mining on  Nicehash is defenitly different as on regular pools. Later i will try switch rigs to new OC concept and if issue comback, than we start invistigate a log files. Regards
legendary
Activity: 3346
Merit: 1094
Hi Patrike, some strange behavior in applying of overclocking settings i see in the last version (8.2.3)
For examle: rig start mining on Octopus algo with PL85% and MEM2000, later switch to ETH where other overclocking settings from Profit profile must be applied, but settings for ETH will not be applied and rig continue mining with settings from Octopus algo. If i mannualy restart mining process, the correct settings will be applied. That happens with all cards types 2080ti, 3070, 3090. And with random rigs.All rigs is Linux (HiveOS) machine. This problem is offten a reason for GPU crashing, where only reboot help. Please check.
Regards
I wasn't able to reproduce this one.

1) Can you please send me the log files for Remote Agent and let me know the time it didn't apply the correct clocking profile?
2) Are you using the new concept with delayed overclocking?
legendary
Activity: 3346
Merit: 1094
Hi patrike,

AM did not change the order of the PCI Bus ID in GPU tab if i change the orders of the gpu´s.
What the GPU mapping is doing is to map the hashrates reported from the mining software to a specific GPU. In case Awesome Miner would show the hashrate for the wrong GPU, you can change the order to make this hashrate show up for another GPU.

So it isn't really for moving up/down a GPU in the list in general, but about moving up/down the hashrate and similar details from the mining software to make it show up for the correct GPU

Ok but the name, temp and clocks also change if i map the gpu´s. Only ID did not change in my case.
The list will always start with ID 0 and continue with 1, 2 and so on. I see that I didn't express this very well in my last response - sorry for any confusion. The GPU ID isn't moving up/down, but the actual GPU details are. Let's show this with an example

GPU 0: Geforce RTX 3080 | Clock details | 50% | 60 C | 28 MH/s
GPU 1: Radeon VII           | Clock details | 55% | 65 C | 42 MH/s

Let's say Awesome Miner didn't map the hashrates reported by the mining software to the correct GPU here. So what is wrong with the table above is that the higher hashrate (42MH/s) is actually the Geforce RTX GPU - but is incorrectly displayed for the Radeon VII GPU.

When using the mapping you can change the order and "move up" the Radeon VII GPU. The result will be the following:

GPU 0: Radeon VII           | Clock details | 55% | 65 C | 28 MH/s
GPU 1: Geforce RTX 3080 | Clock details | 50% | 60 C | 42 MH/s

At this point, 42 MH/s is for the Geforce RTX GPU, which we considered as correct for this example. So it's all about mapping the hashrate to the correct GPU. By design the GPU ID is static - but maybe it it adds a bit confusion and it would make more sense to move it as well.
legendary
Activity: 1754
Merit: 1007
Hi Patrike, some strange behavior in applying of overclocking settings i see in the last version (8.2.3)
For examle: rig start mining on Octopus algo with PL85% and MEM2000, later switch to ETH where other overclocking settings from Profit profile must be applied, but settings for ETH will not be applied and rig continue mining with settings from Octopus algo. If i mannualy restart mining process, the correct settings will be applied. That happens with all cards types 2080ti, 3070, 3090. And with random rigs.All rigs is Linux (HiveOS) machine. This problem is offten a reason for GPU crashing, where only reboot help. Please check.
Regards
member
Activity: 1558
Merit: 69
Hi patrike,

AM did not change the order of the PCI Bus ID in GPU tab if i change the orders of the gpu´s.
What the GPU mapping is doing is to map the hashrates reported from the mining software to a specific GPU. In case Awesome Miner would show the hashrate for the wrong GPU, you can change the order to make this hashrate show up for another GPU.

So it isn't really for moving up/down a GPU in the list in general, but about moving up/down the hashrate and similar details from the mining software to make it show up for the correct GPU

Ok but the name, temp and clocks also change if i map the gpu´s. Only ID did not change in my case.
legendary
Activity: 3346
Merit: 1094
Hi patrike,

AM did not change the order of the PCI Bus ID in GPU tab if i change the orders of the gpu´s.
What the GPU mapping is doing is to map the hashrates reported from the mining software to a specific GPU. In case Awesome Miner would show the hashrate for the wrong GPU, you can change the order to make this hashrate show up for another GPU.

So it isn't really for moving up/down a GPU in the list in general, but about moving up/down the hashrate and similar details from the mining software to make it show up for the correct GPU
full member
Activity: 237
Merit: 100
NOOB question:

I use managed miner with IP (like: 192.168.15.XX)
I am trying to use host becouse sometimes my RIP IP's changes (In this example, my host is: FOR003).

But using hiveos, the AM does not conect using host. Only using IP adreess works..

Is there something special to write on AM to work?

Example:

Remote Agent IP or Hostname: 192.168.15.XX (Works)
Remote Agent IP or Hostname: FOR003 (does not work)

Can anyone helpme?
If Windows can resolve the hostname, Awesome Miner should also be able to resolve the hostname. What happens if you ping the hostname via a Windows command prompt? Is it resolving the the correct IP address?

On windows, ping works only on IP, on putty, ping works with hostname.. I think it is not a AM question... Sad
member
Activity: 1558
Merit: 69
Hi patrike,

AM did not change the order of the PCI Bus ID in GPU tab if i change the orders of the gpu´s.
Pages:
Jump to: