Author

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

member
Activity: 418
Merit: 21
Hey Patrik,

I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.

- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.

Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:

- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.

I think because there is no miner API established because of the crash, even if the mining window is still open?

Hey Patrik,

just got that situation again with the new T-Rex version in one of my single miners. Will send you the API-report by PM.

I think I know why this can happen:

- The profit switcher switched from NBminer to T-Rex, but NBminer wasn't closed for real. It is already running in the background (but depending to the pool with 0 hashrate).
- So there are 2 miners now and AM can't show the numbers for the T-Rex.

Is it somehow possible to double check (and kill) old unneeded tasks? Tried it with a batch command when NBminer stops, but this doesn't work all the time (taskkill /F /IM nbminer.exe).
legendary
Activity: 3346
Merit: 1094
Does anyone know which pool in Awesome Miner is most profitable for Nvidia gpus lately?
Thanks
For the predefined pools in Awesome Miner, the recommendation is to run the Benchmark once to make the profit switcher aware of what is most profitable. You can also view the Online Services tab in Awesome Miner at this point if you want to get an overview of the profitability of the predefined pools.

There can of course be other pools with even higher profit than those predefined in Awesome Miner as there are other mining pools for more recent coins on less common algorithms - but it requires a bit more work to keep up with all the latest and smaller coins.
legendary
Activity: 1848
Merit: 1018
Does anyone know which pool in Awesome Miner is most profitable for Nvidia gpus lately?
Thanks
member
Activity: 653
Merit: 11
Mine the new X25X algo with T-Rex 0.11.1 with 3 times more speed than what shows in WTM and also with 50% more pool rewards.
SIN is the most profitable coin to mine and it needs help from the miners for more hash.
Please bechmark in awesomeminer and look at the profitability.
legendary
Activity: 3346
Merit: 1094
Just asking I guess awesome miner doesn't Support AMD Radeon VII ?. I don't expect it to be added right now just want to know.
it only shows the hash rate no fan speed, temps etc.
I will verify the support within the next few days and get back to you.
member
Activity: 363
Merit: 16
latest version with a minor and a major problem


1. Awesomeminer shows me wrong GPU if i dont use all GPU´s

for example my 8 card Vega Rig:
TRM 0.5.0(also on 0.5.1)
-d 0 -> it show a not active card but i see shares in "Progress" tab
https://ibb.co/rZBzR4R

-d 0,1,2,3 -> 2 cards are maped correctly but two cards in the list are not active
https://ibb.co/bBchQvT


2. if i use awesomeminer the rig dont find shares after some minutes - some minutes later the whole rig is not reachable anymore
the same thing with SRBMiner
i DDU drivers and reinstall - underclock every card and put mv to 950 (instead of 860-880mv the last weeks/month works perfectly) ---- only solution i found out today...not using awesome miner - means -> i start TRM with normal batch on the Rig and dont have any problems

is there any way to disable something (or start debug log) in awesomeminer to verify that it could be a problem with the agent or api or whatever?

I use TRM and AM.

1. use TRM with --bus_reorder and then map the GPU in AM in the ascending order of the PCI BUS ID.
This worked for me, cause Default TRM uses Opencl order, --bus_reorder uses BusID order and AM uses the driver order by default.

2. Right click the miner and select view details -> process information. Verfiy that the command line param are correct.
Right click the miner in AM and select diagnostics -> u should be able to see what went wrong. I can personally confirm that TRM and SRB works fine on my remote 6x Vega Rig for months.


i have other rigs that also work...but like you can see at the screenshots (the links) that it dont matter to use or not use bus-reorder...Awesomeminer show me wrong GPU and after 10-30 minutes no shares and TRM and SRB stop working and i cant close or restart or reboot or anything...i have to power off and restart

without using Awesomeminer (and using same parameters in batch, that i use in awesomeminer) it workes for hours now
Hi,
Please us the "Map to system monitoring" dialog to change the order of the cards using the Up and Down arrow. In your first screenshot I think you should put Device#7 on top for example.

For the mining related issues and the command line - is the Diagnostics output (click the Diagnostics button in the toolbar) in Awesome Miner giving the exact same command line arguments as you have in your batch file? The Diagnostics will show exactly how Awesome Miner started the mining software and it will include both the command line arguments generated by Awesome Miner in combination with any manual commands you added.

You could also try to launch the mining software via Awesome Miner - then close down Remote Agent when the mining has started. Do you still get the crashes?

without the agent it works...will fresh install this rig again
member
Activity: 126
Merit: 10
Just asking I guess awesome miner doesn't Support AMD Radeon VII ?. I don't expect it to be added right now just want to know.
it only shows the hash rate no fan speed, temps etc.

legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
another question, I have asked before but I cannot figure it out --

how do I set different profit profiles for my SHA256 miners? I have tried adding additional ones but whatever I set for one SHA256 miner it sets all of the SHA256 miners to the same one. This does not work for me as some are S9's (all of which do not use the same power) some are T15's and some are T17's --- all of them use different amounts of electricity and I would like to set it for each one separately.
First of all you need more than one profit profile. Please make sure you define for example a S9 and T15 profile in the Options dialog, Profit profile section, where you can add additional profiles. Each profile are configured independently, making it possible for you to specify one hashrate+power for the S9 profile and completely different numbers for the T15 profile.

In the Properties for a miner, you can then select if it should use the S9 profile or the T15 profile as "Profit profile".

Maybe that is my issue - what I do is click on the miner, right click to get "Edit Profit Profile..." option and then on that screen that comes up (algorithms), I created additional SHA-256 items there with different speeds etc but it always assigns the same one to all the miners. When I go thru the way you said, it works fine. I believe you told me this before but I misunderstood - thanks!


nvm... i did this and created multiple profit profiles and set them but I dont see how to select them for the miner... i go thru the motions but it still shows no stats and now my power usage is zero.

and nvm again lol I found it, I have to go to External Miners after creating the profiles, then I can assign the miners to the profile. so now much better.
legendary
Activity: 3346
Merit: 1094
another question, I have asked before but I cannot figure it out --

how do I set different profit profiles for my SHA256 miners? I have tried adding additional ones but whatever I set for one SHA256 miner it sets all of the SHA256 miners to the same one. This does not work for me as some are S9's (all of which do not use the same power) some are T15's and some are T17's --- all of them use different amounts of electricity and I would like to set it for each one separately.
First of all you need more than one profit profile. Please make sure you define for example a S9 and T15 profile in the Options dialog, Profit profile section, where you can add additional profiles. Each profile are configured independently, making it possible for you to specify one hashrate+power for the S9 profile and completely different numbers for the T15 profile.

In the Properties for a miner, you can then select if it should use the S9 profile or the T15 profile as "Profit profile".
legendary
Activity: 3346
Merit: 1094
Awesome miner could add support for device selection in TRM, as currently using the device selection doesnt add the correspondin '-d ' command to the miner. That may solve ur issues.

As for the crashes, I have no clue, mine works fine. Which algo and clocks/timing are you running?

Edit: @Patrik : would be possible to intergrate device selection and builtin watchdog( --watchdog_script=X.bat ) to TRM, the script could be almost same as the SRB one that u have intergrated in AM. Cheesy
I will look into the device selection for TRM.

For watchdog script - I can look into that as well - but do you have any example of what the script would do in the TRM scenario?
For SrbMiner it's needed for terminating the SrbMiner process - in order to let Awesome Miner restart the mining process instead.
legendary
Activity: 3346
Merit: 1094
latest version with a minor and a major problem


1. Awesomeminer shows me wrong GPU if i dont use all GPU´s

for example my 8 card Vega Rig:
TRM 0.5.0(also on 0.5.1)
-d 0 -> it show a not active card but i see shares in "Progress" tab
https://ibb.co/rZBzR4R

-d 0,1,2,3 -> 2 cards are maped correctly but two cards in the list are not active
https://ibb.co/bBchQvT


2. if i use awesomeminer the rig dont find shares after some minutes - some minutes later the whole rig is not reachable anymore
the same thing with SRBMiner
i DDU drivers and reinstall - underclock every card and put mv to 950 (instead of 860-880mv the last weeks/month works perfectly) ---- only solution i found out today...not using awesome miner - means -> i start TRM with normal batch on the Rig and dont have any problems

is there any way to disable something (or start debug log) in awesomeminer to verify that it could be a problem with the agent or api or whatever?

I use TRM and AM.

1. use TRM with --bus_reorder and then map the GPU in AM in the ascending order of the PCI BUS ID.
This worked for me, cause Default TRM uses Opencl order, --bus_reorder uses BusID order and AM uses the driver order by default.

2. Right click the miner and select view details -> process information. Verfiy that the command line param are correct.
Right click the miner in AM and select diagnostics -> u should be able to see what went wrong. I can personally confirm that TRM and SRB works fine on my remote 6x Vega Rig for months.


i have other rigs that also work...but like you can see at the screenshots (the links) that it dont matter to use or not use bus-reorder...Awesomeminer show me wrong GPU and after 10-30 minutes no shares and TRM and SRB stop working and i cant close or restart or reboot or anything...i have to power off and restart

without using Awesomeminer (and using same parameters in batch, that i use in awesomeminer) it workes for hours now
Hi,
Please us the "Map to system monitoring" dialog to change the order of the cards using the Up and Down arrow. In your first screenshot I think you should put Device#7 on top for example.

For the mining related issues and the command line - is the Diagnostics output (click the Diagnostics button in the toolbar) in Awesome Miner giving the exact same command line arguments as you have in your batch file? The Diagnostics will show exactly how Awesome Miner started the mining software and it will include both the command line arguments generated by Awesome Miner in combination with any manual commands you added.

You could also try to launch the mining software via Awesome Miner - then close down Remote Agent when the mining has started. Do you still get the crashes?
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
another question, I have asked before but I cannot figure it out --

how do I set different profit profiles for my SHA256 miners? I have tried adding additional ones but whatever I set for one SHA256 miner it sets all of the SHA256 miners to the same one. This does not work for me as some are S9's (all of which do not use the same power) some are T15's and some are T17's --- all of them use different amounts of electricity and I would like to set it for each one separately.
member
Activity: 363
Merit: 16
Awesome miner could add support for device selection in TRM, as currently using the device selection doesnt add the correspondin '-d ' command to the miner. That may solve ur issues.

As for the crashes, I have no clue, mine works fine. Which algo and clocks/timing are you running?

no clock or mv problem - manual start of TRM in rig works fine
member
Activity: 204
Merit: 10
Awesome miner could add support for device selection in TRM, as currently using the device selection doesnt add the correspondin '-d ' command to the miner. That may solve ur issues.

As for the crashes, I have no clue, mine works fine. Which algo and clocks/timing are you running?

Edit: @Patrik : would be possible to intergrate device selection and builtin watchdog( --watchdog_script=X.bat ) to TRM, the script could be almost same as the SRB one that u have intergrated in AM. Cheesy
member
Activity: 363
Merit: 16
latest version with a minor and a major problem


1. Awesomeminer shows me wrong GPU if i dont use all GPU´s

for example my 8 card Vega Rig:
TRM 0.5.0(also on 0.5.1)
-d 0 -> it show a not active card but i see shares in "Progress" tab
https://ibb.co/rZBzR4R

-d 0,1,2,3 -> 2 cards are maped correctly but two cards in the list are not active
https://ibb.co/bBchQvT


2. if i use awesomeminer the rig dont find shares after some minutes - some minutes later the whole rig is not reachable anymore
the same thing with SRBMiner
i DDU drivers and reinstall - underclock every card and put mv to 950 (instead of 860-880mv the last weeks/month works perfectly) ---- only solution i found out today...not using awesome miner - means -> i start TRM with normal batch on the Rig and dont have any problems

is there any way to disable something (or start debug log) in awesomeminer to verify that it could be a problem with the agent or api or whatever?

I use TRM and AM.

1. use TRM with --bus_reorder and then map the GPU in AM in the ascending order of the PCI BUS ID.
This worked for me, cause Default TRM uses Opencl order, --bus_reorder uses BusID order and AM uses the driver order by default.

2. Right click the miner and select view details -> process information. Verfiy that the command line param are correct.
Right click the miner in AM and select diagnostics -> u should be able to see what went wrong. I can personally confirm that TRM and SRB works fine on my remote 6x Vega Rig for months.


i have other rigs that also work...but like you can see at the screenshots (the links) that it dont matter to use or not use bus-reorder...Awesomeminer show me wrong GPU and after 10-30 minutes no shares and TRM and SRB stop working and i cant close or restart or reboot or anything...i have to power off and restart

without using Awesomeminer (and using same parameters in batch, that i use in awesomeminer) it workes for hours now
member
Activity: 204
Merit: 10
latest version with a minor and a major problem


1. Awesomeminer shows me wrong GPU if i dont use all GPU´s

for example my 8 card Vega Rig:
TRM 0.5.0(also on 0.5.1)
-d 0 -> it show a not active card but i see shares in "Progress" tab
https://ibb.co/rZBzR4R

-d 0,1,2,3 -> 2 cards are maped correctly but two cards in the list are not active
https://ibb.co/bBchQvT


2. if i use awesomeminer the rig dont find shares after some minutes - some minutes later the whole rig is not reachable anymore
the same thing with SRBMiner
i DDU drivers and reinstall - underclock every card and put mv to 950 (instead of 860-880mv the last weeks/month works perfectly) ---- only solution i found out today...not using awesome miner - means -> i start TRM with normal batch on the Rig and dont have any problems

is there any way to disable something (or start debug log) in awesomeminer to verify that it could be a problem with the agent or api or whatever?

I use TRM and AM.

1. use TRM with --bus_reorder and then map the GPU in AM in the ascending order of the PCI BUS ID.
This worked for me, cause Default TRM uses Opencl order, --bus_reorder uses BusID order and AM uses the driver order by default.

2. Right click the miner and select view details -> process information. Verfiy that the command line param are correct.
Right click the miner in AM and select diagnostics -> u should be able to see what went wrong. I can personally confirm that TRM and SRB works fine on my remote 6x Vega Rig for months.
member
Activity: 363
Merit: 16
latest version with a minor and a major problem


1. Awesomeminer shows me wrong GPU if i dont use all GPU´s

for example my 8 card Vega Rig:
TRM 0.5.0(also on 0.5.1)
-d 0 -> it show a not active card but i see shares in "Progress" tab
https://ibb.co/rZBzR4R

-d 0,1,2,3 -> 2 cards are maped correctly but two cards in the list are not active
https://ibb.co/bBchQvT


2. if i use awesomeminer the rig dont find shares after some minutes - some minutes later the whole rig is not reachable anymore
the same thing with SRBMiner
i DDU drivers and reinstall - underclock every card and put mv to 950 (instead of 860-880mv the last weeks/month works perfectly) ---- only solution i found out today...not using awesome miner - means -> i start TRM with normal batch on the Rig and dont have any problems

is there any way to disable something (or start debug log) in awesomeminer to verify that it could be a problem with the agent or api or whatever?
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490

Yes, it will be included in the next release.

thank you Patrike

also, I have not read all the back posts - have you managed a way to get ssh into the bitmain miners yet? or have they released a firmware allowing it?
There are no solution to the SSH limitations yet and it looks like Bitmain are continuing to release new firmware with SSH disabled. I've been trying to get Bitmain to implement a setting to enable Privileged API access, but unfortunately no progress on that request either.

A while ago I added the features to set Default Pools and Reboot by connecting to the Antminer web interface instead of SSH - but those where just workarounds for the fact that SSH wasn't available.

ahh ok - the BW L21 miners are also API restricted as well Sad
legendary
Activity: 3346
Merit: 1094

Yes, it will be included in the next release.

thank you Patrike

also, I have not read all the back posts - have you managed a way to get ssh into the bitmain miners yet? or have they released a firmware allowing it?
There are no solution to the SSH limitations yet and it looks like Bitmain are continuing to release new firmware with SSH disabled. I've been trying to get Bitmain to implement a setting to enable Privileged API access, but unfortunately no progress on that request either.

A while ago I added the features to set Default Pools and Reboot by connecting to the Antminer web interface instead of SSH - but those where just workarounds for the fact that SSH wasn't available.
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490

Yes, it will be included in the next release.

thank you Patrike

also, I have not read all the back posts - have you managed a way to get ssh into the bitmain miners yet? or have they released a firmware allowing it?
Jump to: