Author

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

newbie
Activity: 31
Merit: 0
anyone have problems with Nicehash if mining Coockarood29 or Coockaroom29 with GMiner 1.96 ?
I always get "End of file" error and connection will be closed.
Looks like Nicehash not correct recognize "Grin29" algo param.
I have set in AM for each algo explicit algo params name like: coockarood29 and coockaroom29 and looks like its works now.


Thanks for the fix, it works fine with those modifications!
newbie
Activity: 59
Merit: 0
anyone have problems with Nicehash if mining Coockarood29 or Coockaroom29 with GMiner 1.96 ?
I always get "End of file" error and connection will be closed.
Looks like Nicehash not correct recognize "Grin29" algo param.
I have set in AM for each algo explicit algo params name like: coockarood29 and coockaroom29 and looks like its works now.


Chugging away nicely on my Nvidia GPU rig and desktop. Using GMiner default settings. No issues noted. V1.96 provided a nice bump up in hashrate.

This is for CuckaRoom29. Have not tried CuckaRood29.

...jim
legendary
Activity: 1754
Merit: 1007
anyone have problems with Nicehash if mining Coockarood29 or Coockaroom29 with GMiner 1.96 ?
I always get "End of file" error and connection will be closed.
Looks like Nicehash not correct recognize "Grin29" algo param.
I have set in AM for each algo explicit algo params name like: coockarood29 and coockaroom29 and looks like its works now.
legendary
Activity: 3346
Merit: 1094
How this calculation got zero??? any many coin calculation earning error??  Please concern about this , if u cant get this coin calculation fix better remove it! Thanks!!
Awesome Miner get coin statistics from a few providers but in some cases Awesome Miner needs to do some adjustments based on the raw data reported. I've just pushed an adjustment for these coins to correct the problem. Recent versions of Awesome Miner will automatically pick up calculation adjustments like this within an hour.
legendary
Activity: 3346
Merit: 1094
GMINER ORDER WRONG

If i set Gminer, it will only recognize the Nvidia Cards in GPU selection, but it must show all cards, because Gminer can use AMD and Nvidia. The problem at the moment is, he recognize only Nvidia cards and set the wrong order.
If i set use all GPU´s, it will mine BEAM with alle 13 Cards. If i set use only the Nvidia Cards in GPU selection, it will set -d 0 1 2 3 4 5 in commandline but this is the wrong order. The right order is  -d 3 4 5 7 8 12
I hope you understand the problem?
Yes, I see your point. I will investigate this and I will probably have a solution available in the next release. Thanks for letting me know!

XMRIG AND NANOMINER USE THE SAME CONFIG

If i set a config for RandomX and Nanominer in ManagedMiner Properties Config File, XMRig use the same config. I think this is bug.

The configuration of algorithm specific configuration files are only stored "per algorithm" for a Managed Miner. If you change the mining software of the Managed Miner from Nanominer and XmRig, any configuration you made for RandomX for Nanominer will also show up for XmRig. It's currently not stored "per algorithm per mining software".

This is the same as all other settings for a Managed Miner. If you configure a custom command line, a GPU clocking profile and so on - it's stored for the Managed Miner and if you change between Nanominer and XmRig, they will not have separate storage for a custom command line and so on.
legendary
Activity: 3346
Merit: 1094
Can you add PhoenixMiner dual mining capability for Eth+Blake2s ?
This is supported already. Please create a Pool Group (Options dialog, Pools section) with an Ethereum pool and Blake2s pool. Then go to the Properties of your Managed Miner and set Dual Mode to "Ethereum + Blake2s" and select your Pool Group.
member
Activity: 180
Merit: 10
How this calculation got zero??? any many coin calculation earning error??  Please concern about this , if u cant get this coin calculation fix better remove it! Thanks!!


I hope that I'm misinterpreting this because it seems kinda rude.
Patrike seems to be one of the best and most supportive developer on here and should be treated a bit more respectfully. Just my opinion though.
member
Activity: 180
Merit: 10
c:\windows\system32\nvml.dll
C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll
C:\Program Files (x86)\NVIDIA Corporation\NVSMI\nvml.dll


So I don't think it's a problem with AwesomeMiner after all.
I just spotted this on on the command prompt window for PhoenixMiner the rig while doing the search.

GPU1: N/A, GPU2: N/A, GPU3: 59C 53% 115W, GPU4: N/A, GPU5: N/A, GPU6: 59C 53% 135W, GPU7: 58C 52% 137W, GPU8: N/A, GPU9: N/A, GPU10: N/A, GPU11: N/A
GPUs power: 387.0 W

I tried switching to Claymore and it yielded the same result in AwesomeMiner.

Strange, isn't it?
Thanks for sharing all details - it was really helpful. I have an idea what it's about and there will soon be an updated release with some improvements.

As I'm not able to reproduce this in my setup, please let me know the result once the new version is available. Thanks!

Wow!
I'm not sure what you did but it seemed to have worked. Thanks!
Good thing too because the 1600W PDU that I had ordered requires a C19 cable (instead of the expected C13) to connect it to my 220V PDU. So it looks like it might be a few more days until I get it set up. Wink

Thanks for your diligence.

Thanks for the feedback.

What I noticed based on your reports was that the nVidia driver installer only put nvml.dll in the Windows System32 folder these days. In the past the file was not installed in System32 at all. The other folders (Program Files) had an older nvml.dll not updated and not removed by the later driver versions. So in some systems you could have an outdated nvml.dll here, causing problems with Power Usage reporting for many applications incl. Awesome Miner. I changed Awesome Miner to favor the version in the System32 folder and this resolved the problem.

You're a genius. Thanks again.
copper member
Activity: 416
Merit: 105
How this calculation got zero??? any many coin calculation earning error??  Please concern about this , if u cant get this coin calculation fix better remove it! Thanks!!
member
Activity: 1558
Merit: 69
Hi Patrike,

Bug report:

GMINER ORDER WRONG

RIG-1
7 AMD Cards mining ETH with claymore


6 Nvidia Cards mining BEAM with Gminer


If i set Gminer, it will only recognize the Nvidia Cards in GPU selection, but it must show all cards, because Gminer can use AMD and Nvidia. The problem at the moment is, he recognize only Nvidia cards and set the wrong order.
If i set use all GPU´s, it will mine BEAM with alle 13 Cards. If i set use only the Nvidia Cards in GPU selection, it will set -d 0 1 2 3 4 5 in commandline but this is the wrong order. The right order is  -d 3 4 5 7 8 12
I hope you understand the problem?

XMRIG AND NANOMINER USE THE SAME CONFIG

If i set a config for RandomX and Nanominer in ManagedMiner Properties Config File, XMRig use the same config. I think this is bug.

newbie
Activity: 49
Merit: 0
Can you add PhoenixMiner dual mining capability for Eth+Blake2s ?
legendary
Activity: 3346
Merit: 1094
@patrike
Hi boss.
this scenario not good  work:
AM managed different rigs Win & Linux clients.
If i try to put custom URL in "Predefined Managed Software Properties" with Windows package, then Linux rig also download Windows version and this is of course wrong. We need different field for "Custom URL" for Linux.

Regards
Thanks for the report.

The configuration of Managed Software only allows one customized download path to be set at the moment, so if you have a mix of Windows and Linux this will not work so well.

A workaround for the moment would be to add a new User Defined Managed Software, where you specify full compatibility with the original software, but with a different download URL. This new User Defined software could for example represent the mining software you want to use for Linux.

I agree that there probably should be a way to configure URL and executable individually for Windows and Linux on a single Managed Software.
legendary
Activity: 3346
Merit: 1094
Bugfixes on lolminer compatibility:

1. Miner supports all c29 variants (29,d,m) and c31
2. Miner uses this format of algo support. I think it is done internally in AM and not via miner properties-command line arg. Adding support to do this via the deafult/user defined command line args would help
Code:
--coin
--coin sets the coin you want to mine, e.g. BEAM,AION,BTG,...

...

3. Hashrates are not properly parsed in decimal from the api. The api gives proper 1.2 as values, but is parsed and displayed as 1 in am.

Thanks for the details! There were a number of hardcoded mappings for Lolminer as it had a bit special concept for specifying algorithms - as it's typically the coin name you specify. I will change this to be more flexible where you can use the standard algorithm configuration for Lolminer as well.

I will also correct the hashrate reporting.
legendary
Activity: 1754
Merit: 1007
@patrike
Hi boss.
this scenario not good  work:
AM managed different rigs Win & Linux clients.
If i try to put custom URL in "Predefined Managed Software Properties" with Windows package, then Linux rig also download Windows version and this is of course wrong. We need different field for "Custom URL" for Linux.

Regards
legendary
Activity: 3346
Merit: 1094
c:\windows\system32\nvml.dll
C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll
C:\Program Files (x86)\NVIDIA Corporation\NVSMI\nvml.dll


So I don't think it's a problem with AwesomeMiner after all.
I just spotted this on on the command prompt window for PhoenixMiner the rig while doing the search.

GPU1: N/A, GPU2: N/A, GPU3: 59C 53% 115W, GPU4: N/A, GPU5: N/A, GPU6: 59C 53% 135W, GPU7: 58C 52% 137W, GPU8: N/A, GPU9: N/A, GPU10: N/A, GPU11: N/A
GPUs power: 387.0 W

I tried switching to Claymore and it yielded the same result in AwesomeMiner.

Strange, isn't it?
Thanks for sharing all details - it was really helpful. I have an idea what it's about and there will soon be an updated release with some improvements.

As I'm not able to reproduce this in my setup, please let me know the result once the new version is available. Thanks!

Wow!
I'm not sure what you did but it seemed to have worked. Thanks!
Good thing too because the 1600W PDU that I had ordered requires a C19 cable (instead of the expected C13) to connect it to my 220V PDU. So it looks like it might be a few more days until I get it set up. Wink

Thanks for your diligence.

Thanks for the feedback.

What I noticed based on your reports was that the nVidia driver installer only put nvml.dll in the Windows System32 folder these days. In the past the file was not installed in System32 at all. The other folders (Program Files) had an older nvml.dll not updated and not removed by the later driver versions. So in some systems you could have an outdated nvml.dll here, causing problems with Power Usage reporting for many applications incl. Awesome Miner. I changed Awesome Miner to favor the version in the System32 folder and this resolved the problem.
member
Activity: 204
Merit: 10
Bugfixes on lolminer compatibility:

1. Miner supports all c29 variants (29,d,m) and c31
2. Miner uses this format of algo support. I think it is done internally in AM and not via miner properties-command line arg. Adding support to do this via the deafult/user defined command line args would help
Code:
--coin
--coin sets the coin you want to mine, e.g. BEAM,AION,BTG,...

Command line arg  Full Coin NameAlgorithm
AUTO144_5 For use with personalisation String --overwritePersonal
Equihash 144/5
AUTO192_7For use with personalisation String --overwritePersonal Equihash 192/7
BEAM Beam (Beam Hash II)EquihashR 150/5/3
GRIN-C29MGrinCuckarooM 29
GRIN-C31GrinCuckatoo 31
GRIN-C32GrinCuckatoo 32

3. Hashrates are not properly parsed in decimal from the api. The api gives proper 1.2 as values, but is parsed and displayed as 1 in am.
member
Activity: 180
Merit: 10
@Binary100100
Maybe that help you:
Create folder NVSMI in C:/Programm Files/NVIDIA Corporation
find on computer file nvml.dll and copy to NVSMI
restart miner

Thanks for trying, but no. I even tried re-installing the drivers and rebooting. Same results.
Thanks for sharing the fact that the LibreHardwareMonitor tool was working. That tool uses NVML in a similar way as Awesome Miner, so Awesome Miner is expected to work in this environment as well. I will investigate the issue in more detail. I may get back to you about the log file for Remote Agent if needed.

Okay, thanks for trying.
I'm expecting to get my new 1600W PSU on Tuesday. Depending on the time of the delivery I might be installing it as late as Wednesday. At that point, I might be moving the 1070 cards back to their original machine. At that point, this won't really matter much to me anymore. I only brought it to your attention because it was a pretty strange issue.
If possible, could you please search for "nvml.dll" and let me know the path or paths where it's found? Many thanks!

c:\windows\system32\nvml.dll
C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll
C:\Program Files (x86)\NVIDIA Corporation\NVSMI\nvml.dll


So I don't think it's a problem with AwesomeMiner after all.
I just spotted this on on the command prompt window for PhoenixMiner the rig while doing the search.

GPU1: N/A, GPU2: N/A, GPU3: 59C 53% 115W, GPU4: N/A, GPU5: N/A, GPU6: 59C 53% 135W, GPU7: 58C 52% 137W, GPU8: N/A, GPU9: N/A, GPU10: N/A, GPU11: N/A
GPUs power: 387.0 W

I tried switching to Claymore and it yielded the same result in AwesomeMiner.

Strange, isn't it?
Thanks for sharing all details - it was really helpful. I have an idea what it's about and there will soon be an updated release with some improvements.

As I'm not able to reproduce this in my setup, please let me know the result once the new version is available. Thanks!

Wow!
I'm not sure what you did but it seemed to have worked. Thanks!
Good thing too because the 1600W PDU that I had ordered requires a C19 cable (instead of the expected C13) to connect it to my 220V PDU. So it looks like it might be a few more days until I get it set up. Wink

Thanks for your diligence.
jr. member
Activity: 238
Merit: 3
C29M is disabled for lolMiner, does not work even if I manually enable it and add "--coin C29M" - looks like the custom command line argument is not used so the miner silently fails.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 7.2.10

 GPU mining
  - Improved compatibility for reading GPU power usage on recent nVidia driver versions
 Mining software
  - Gminer 1.95
  - Bminer 16.0.1
  - Lolminer 0.9.6
  - Nanominer 1.7.1
  - CpuMiner-Opt 3.11.5
  - SrbMiner Multi 0.3
 Corrections
  - Correction to sorting by temperature in the miner list
legendary
Activity: 3346
Merit: 1094
@Binary100100
Maybe that help you:
Create folder NVSMI in C:/Programm Files/NVIDIA Corporation
find on computer file nvml.dll and copy to NVSMI
restart miner

Thanks for trying, but no. I even tried re-installing the drivers and rebooting. Same results.
Thanks for sharing the fact that the LibreHardwareMonitor tool was working. That tool uses NVML in a similar way as Awesome Miner, so Awesome Miner is expected to work in this environment as well. I will investigate the issue in more detail. I may get back to you about the log file for Remote Agent if needed.

Okay, thanks for trying.
I'm expecting to get my new 1600W PSU on Tuesday. Depending on the time of the delivery I might be installing it as late as Wednesday. At that point, I might be moving the 1070 cards back to their original machine. At that point, this won't really matter much to me anymore. I only brought it to your attention because it was a pretty strange issue.
If possible, could you please search for "nvml.dll" and let me know the path or paths where it's found? Many thanks!

c:\windows\system32\nvml.dll
C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll
C:\Program Files (x86)\NVIDIA Corporation\NVSMI\nvml.dll


So I don't think it's a problem with AwesomeMiner after all.
I just spotted this on on the command prompt window for PhoenixMiner the rig while doing the search.

GPU1: N/A, GPU2: N/A, GPU3: 59C 53% 115W, GPU4: N/A, GPU5: N/A, GPU6: 59C 53% 135W, GPU7: 58C 52% 137W, GPU8: N/A, GPU9: N/A, GPU10: N/A, GPU11: N/A
GPUs power: 387.0 W

I tried switching to Claymore and it yielded the same result in AwesomeMiner.

Strange, isn't it?
Thanks for sharing all details - it was really helpful. I have an idea what it's about and there will soon be an updated release with some improvements.

As I'm not able to reproduce this in my setup, please let me know the result once the new version is available. Thanks!
Jump to: