Pages:
Author

Topic: Megaminer 6.3 - Multi pool / Multi Algo launcher - page 27. (Read 70970 times)

sr. member
Activity: 434
Merit: 251
How do I set a different payout coin for different pools? Like Ahashpool,zpool,ETC as i would like to set different payout coins for each.

The config file would do all.

If you want a different coin for each pool you need to edit the pool file and not use the config.
sr. member
Activity: 450
Merit: 255
How do I set a different payout coin for different pools? Like Ahashpool,zpool,ETC as i would like to set different payout coins for each.
member
Activity: 145
Merit: 10
5.0b1 works fine on my rig with 2x1070ti and 1x1070.

However on my rig with 1x1080ti and 1xvega64, 5.0b3 doesn't run the benchmarks. The miner windows open and insta-closes.

Also i'm getting this error:

Add-Member : Cannot add a member with the name "Name" because a member with that name already exists. To overwrite the
member anyway, add the Force parameter to your command.
At C:\Miners\Megaminer-5.0-beta3\Megaminer-5.0-beta3\Include.ps1:427 char:95
+ ... ent -ne $null) {$_.Content | Add-Member @{Name = $_.Name} -PassThru}}
+                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (@{Algorithm=Equ...ining_Pool_Hub}:PSObject) [Add-Member],
InvalidOperationException
    + FullyQualifiedErrorId : MemberAlreadyExists,Microsoft.PowerShell.Commands.AddMemberCommand
Add-Member : Cannot add a member with the name "Name" because a member with that name already exists. To overwrite the
member anyway, add the Force parameter to your command.

i've deleted the folders, and tried beta 1,2 and 3 but none works.

Any tips on how to solve this? Thanks!

Fixed it, Used gpu=0 for both 1080ti and vega64
newbie
Activity: 39
Merit: 0
Feature request:  After X intervals automatically exit the script. "X" would be a setting in the Config.txt file. This would allow us to restart the script in a batch file. Thanks.

Why do you need restart script? It can run days without problems.

I've found the script hung a couple of times. I only found out when another script I have that monitors temps alerted me to low temps on the rig. I've got large pages enabled, 8GB ram, and 120GB SSD. I'm willing to help diagnose if there's a way to troubleshoot this. I'll save the log when it happens again.
full member
Activity: 322
Merit: 105
Feature request:  After X intervals automatically exit the script. "X" would be a setting in the Config.txt file. This would allow us to restart the script in a batch file. Thanks.

Why do you need restart script? It can run days without problems.
newbie
Activity: 39
Merit: 0
Feature request:  After X intervals automatically exit the script. "X" would be a setting in the Config.txt file. This would allow us to restart the script in a batch file. Thanks.
full member
Activity: 322
Merit: 105
does anyone else experience high cpu load in powershell in megaminer 4.8?

I looked at two rigs (both somewhat older CPU/mainboard) and powershell/consolehost ist using around 10-15% CPU all the time. system is win10x64.

I don't really care about the 15% cpu usage, but that keeps the CPU from sleeping and increases power usage by about 30W compared to the scripts not running.

Is there anything that can be done to reduce the load of the scripts? refresh, update intervals, removing/disabling non-essential stuff? Anyone messed with that yet?

thanks!


Solved next release, you can test it now on github master branch
member
Activity: 111
Merit: 10
does anyone else experience high cpu load in powershell in megaminer 4.8?

I looked at two rigs (both somewhat older CPU/mainboard) and powershell/consolehost ist using around 10-15% CPU all the time. system is win10x64.

I don't really care about the 15% cpu usage, but that keeps the CPU from sleeping and increases power usage by about 30W compared to the scripts not running.

Is there anything that can be done to reduce the load of the scripts? refresh, update intervals, removing/disabling non-essential stuff? Anyone messed with that yet?

thanks!
member
Activity: 413
Merit: 17
The script doesn't benchmark ClaymoreETH dual on both NVIDIA and AMD on Mining Pool Hub. Can you look into it?

Try Beta3

I did, totally clean release with no changes at all. If I remove YIIMP from AutoStart Example - Two pools on Auto.bat and leave only MPH, the dual mining is not available.
There is something wrong with the dual mining parser on MPH.

Pick new Mining_pool_hub.ps1 file from github master branch

Coin names are not visible, otherwise it works fine. Thank you!
full member
Activity: 322
Merit: 105
The script doesn't benchmark ClaymoreETH dual on both NVIDIA and AMD on Mining Pool Hub. Can you look into it?

Try Beta3

I did, totally clean release with no changes at all. If I remove YIIMP from AutoStart Example - Two pools on Auto.bat and leave only MPH, the dual mining is not available.
There is something wrong with the dual mining parser on MPH.

Pick new Mining_pool_hub.ps1 file from github master branch
member
Activity: 413
Merit: 17
The script doesn't benchmark ClaymoreETH dual on both NVIDIA and AMD on Mining Pool Hub. Can you look into it?

Try Beta3

I did, totally clean release with no changes at all. If I remove YIIMP from AutoStart Example - Two pools on Auto.bat and leave only MPH, the dual mining is not available.
There is something wrong with the dual mining parser on MPH.
full member
Activity: 322
Merit: 105
Not support 12 GPU

"GroupName" : "1060","Type":"NVIDIA","GpuPlatform":"0","Gpus":"0,1,2,3,4,5,6,7,8,9,10,11"

program error can used 0-9  only 10 gpu


PlatformId Name        Vendor
---------- ----        ------
         0 NVIDIA CUDA NVIDIA Corporation




No MM gpu number limit, but I think some miners has. What error your get?
full member
Activity: 322
Merit: 105
is it possible do disable logging in 4.8, how to do it?


delete this line in core.ps1


Start-Transcript ".\Logs\$(Get-Date -Format "yyyy-MM-dd_HH-mm-ss").txt"
full member
Activity: 322
Merit: 105
I'm using 4.8 but I'm unable to use version 5.x on both my NVIDIA rigs or AMD rig.
It tells me
No miners!
What am I doing wrong in the config file?

Also, I'm using start.bat with MPH pool only and automatic coin and when I come back later my AMD rig is not mining anymore and is stuck in a loop trying to connect on NICEHASH pool but fails. Why is that happening? Can I delete nicehash.ps1 and it will resolve this?


I got this too. Script is unable to download miners. I downloaded manually using urls from logs. Maybe some firewall, or antivirus issue. On other pc on the same switch it downloaded ok.

On 4.8 the miners downloaded just fine.. I even tried to copy those but same message


Download method are the same, no changes, I think Windows antivirus has updated definitions or something similar, for me manual downloading of files fail (antivirus delete it), but works when run inside MM (I have this path excluded).

You can add MM path as exclusion on Windows Defender.




full member
Activity: 322
Merit: 105
I'm using 4.8 but I'm unable to use version 5.x on both my NVIDIA rigs or AMD rig.
It tells me
No miners!
What am I doing wrong in the config file?


Also, I'm using start.bat with MPH pool only and automatic coin and when I come back later my AMD rig is not mining anymore and is stuck in a loop trying to connect on NICEHASH pool but fails. Why is that happening? Can I delete nicehash.ps1 and it will resolve this?


Check miners are downloading at bin folder, some people are having problem with antivirus


You can delete Nicehash file, I don´t understand why this is happening if you are using "-Poolsname Mining_pool_hub" parameter, other pools files must be ignored.
full member
Activity: 322
Merit: 105


I was using 4.3 until upgrading to version 5 and with 4.3 I could add a "-b 0.0.0.0:4068" to the miner file and then monitor on awesome miner.

It appears we are using "-b XXXX" api for benchmarking

Any solution to monitoring rigs?


In 4.X releases if you need to force api port you can use ApiPort atribute of miner file, if you use -b parameter comunication between MM and miner will not work.

In 5.X  this field is not valid due to dinamic port asignation (you can be running same miner more than one time if you have more than one defined group). I have added to 5.0 beta 4 (in development now) that you can use again this miner atribute but it only will work if only one group is defined for your rig

full member
Activity: 322
Merit: 105
The script doesn't benchmark ClaymoreETH dual on both NVIDIA and AMD on Mining Pool Hub. Can you look into it?

Try Beta3
full member
Activity: 322
Merit: 105
Not a fan of the groups or #DEVICES#. I had to remove from most of the miners to get it to run.

This is a big change on program, is the first MPM fork works with this, on Nvidia pure rigs are running well, on mixed/AMD rigs not, as you know I havent AMD cards. It´s question of feedback and time
newbie
Activity: 3
Merit: 0
Not support 12 GPU

"GroupName" : "1060","Type":"NVIDIA","GpuPlatform":"0","Gpus":"0,1,2,3,4,5,6,7,8,9,10,11"

program error can used 0-9  only 10 gpu


PlatformId Name        Vendor
---------- ----        ------
         0 NVIDIA CUDA NVIDIA Corporation



Listing OpenCL devices.
FORMAT: [deviceID] deviceName
  • GeForce GTX 1070
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 8589934592
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 2147483648
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[1] GeForce GTX 1060 3GB
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 3221225472
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 805306368
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[2] GeForce GTX 1060 3GB
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 3221225472
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 805306368
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[3] GeForce GTX 1060 3GB
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 3221225472
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 805306368
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[4] GeForce GTX 1060 3GB
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 3221225472
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 805306368
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[5] GeForce GTX 1060 3GB
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 3221225472
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 805306368
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[6] GeForce GTX 1050 Ti
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1073741824
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[7] GeForce GTX 1050 Ti
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1073741824
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[8] GeForce GTX 1060 6GB
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 6442450944
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1610612736
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[9] GeForce GTX 1050 Ti
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1073741824
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[10] GeForce GTX 1050 Ti
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 4294967296
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 1073741824
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024
[11] GeForce GTX 1060 3GB
        CL_DEVICE_TYPE: GPU
        CL_DEVICE_GLOBAL_MEM_SIZE: 3221225472
        CL_DEVICE_MAX_MEM_ALLOC_SIZE: 805306368
        CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024

Listing CUDA devices.
FORMAT: [deviceID] deviceName
  • GeForce GTX 1070
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 8589934592
[1] GeForce GTX 1060 3GB
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 3221225472
[2] GeForce GTX 1060 3GB
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 3221225472
[3] GeForce GTX 1060 3GB
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 3221225472
[4] GeForce GTX 1060 3GB
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 3221225472
[5] GeForce GTX 1060 3GB
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 3221225472
[6] GeForce GTX 1050 Ti
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 4294967296
[7] GeForce GTX 1050 Ti
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 4294967296
[8] GeForce GTX 1060 6GB
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 6442450944
[9] GeForce GTX 1050 Ti
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 4294967296
[10] GeForce GTX 1050 Ti
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 4294967296
[11] GeForce GTX 1060 3GB
        Compute version: 6.1
        cudaDeviceProp::totalGlobalMem: 3221225472
member
Activity: 134
Merit: 10
is it possible do disable logging in 4.8, how to do it?
Pages:
Jump to: