Pages:
Author

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

full member
Activity: 322
Merit: 105


What should I do now?

This is visual only error, all works fine.

If you want to avoid this remove miningpoolhub.ps1 line

Remove-variable request
sr. member
Activity: 703
Merit: 272


What should I do now?

wait until benchmarking completes... and then wait more.   there's really nothing more for you to do except look at the screen.
jr. member
Activity: 42
Merit: 1
Oh I've had that same error. The only way I made it go away was by removing offending alogorithm in config.txt. It's been a lot of trial and error. For instance, the amd algo list includes hooks into a miner that only works for vega hardware.

Anyway, for me it has been a grueling process of pools and algos. I think it is worth the effort because this software profit switching looks en pointe. I'm still collecting data for my rigs, both amd and nvidia, but it looks good so far. I'm still trying to figure it out.

full member
Activity: 266
Merit: 100


What should I do now?
jr. member
Activity: 42
Merit: 1
Hey guys, I hate to make noob fail post, but here I am. I have let this software churn for 12 hours and nothing is happening. Grateful for some help. I am running on test pc with only a single nvidia 1050 ti, I am back one version on the driver (April? 393?). Windows 10.

At first I was ambitious and enabled all the pools but I have cut down to one pool only, zpool, until i figure this out. I've left all the algorithms. Sometimes miner windows don't launch at all, sometimes they launch and I see a gpu memory exception flashing by.

But first things first - blue powershell screen - Is it supposed to start up and then shut down right away? I see many lines of red errors, but gone so fast I'm unable to read. At some point on the regular black dos startup screen I saw an error with some variable named "request" and I saw another error about the window width.

Thanks.  Huh

Something is going wrong, check log files from logs folder

Hi,

I am making some progress, isolating and capturing errors. I will create thread on github/issues to continue convo. Thanks for your reply, see you over there. Smiley
full member
Activity: 322
Merit: 105
Hey guys, I hate to make noob fail post, but here I am. I have let this software churn for 12 hours and nothing is happening. Grateful for some help. I am running on test pc with only a single nvidia 1050 ti, I am back one version on the driver (April? 393?). Windows 10.

At first I was ambitious and enabled all the pools but I have cut down to one pool only, zpool, until i figure this out. I've left all the algorithms. Sometimes miner windows don't launch at all, sometimes they launch and I see a gpu memory exception flashing by.

But first things first - blue powershell screen - Is it supposed to start up and then shut down right away? I see many lines of red errors, but gone so fast I'm unable to read. At some point on the regular black dos startup screen I saw an error with some variable named "request" and I saw another error about the window width.

Thanks.  Huh

Something is going wrong, check log files from logs folder
jr. member
Activity: 42
Merit: 1
Hey guys, I hate to make noob fail post, but here I am. I have let this software churn for 12 hours and nothing is happening. Grateful for some help. I am running on test pc with only a single nvidia 1050 ti, I am back one version on the driver (April? 393?). Windows 10.

At first I was ambitious and enabled all the pools but I have cut down to one pool only, zpool, until i figure this out. I've left all the algorithms. Sometimes miner windows don't launch at all, sometimes they launch and I see a gpu memory exception flashing by.

But first things first - blue powershell screen - Is it supposed to start up and then shut down right away? I see many lines of red errors, but gone so fast I'm unable to read. At some point on the regular black dos startup screen I saw an error with some variable named "request" and I saw another error about the window width.

Thanks.  Huh
full member
Activity: 322
Merit: 105
Hey buddy, Megaminer is using x16s on zergpool to try bench RVN, might wanna fix that Tongue
as you can imagine it wont complete bench even as it results in 100% rejected shares : / 

Love the program Smiley



to add to that, it's also using RVN on blazepool to try and bench x16s for SuprminerSP/a

in addition, 6.3 is not accepting additional algo's that i add, such as sha256t (supported by both Jayddee(cpu) and Tpruvot(gpu)).  it worked fine in mm 6.2.1 and earlier.


Check last master code, first bug fixed and sha256t included
full member
Activity: 322
Merit: 105
there is no enemy miner available to ddl cause there is no url.  how do i add it to the mine x16r?


Enemy miner is included as ccminerX16r
sr. member
Activity: 703
Merit: 272
Hey buddy, Megaminer is using x16s on zergpool to try bench RVN, might wanna fix that Tongue
as you can imagine it wont complete bench even as it results in 100% rejected shares : / 

Love the program Smiley



to add to that, it's also using RVN on blazepool to try and bench x16s for SuprminerSP/a

in addition, 6.3 is not accepting additional algo's that i add, such as sha256t (supported by both Jayddee(cpu) and Tpruvot(gpu)).  it worked fine in mm 6.2.1 and earlier.
legendary
Activity: 1820
Merit: 1092
~Full-Time Minter since 2016~
Hey buddy, Megaminer is using x16s on zergpool to try bench RVN, might wanna fix that Tongue
as you can imagine it wont complete bench even as it results in 100% rejected shares : / 

Love the program Smiley

newbie
Activity: 55
Merit: 0
there is no enemy miner available to ddl cause there is no url.  how do i add it to the mine x16r?
full member
Activity: 322
Merit: 105

6.3 Release

---FEATURES CHANGES:
* Added Automatic EThLargementPill for Nvidia hashrate booster for 1080/1080ti
* New message at start if new Megaminer release available
* Updated nvdia-smi (needed for nvidia cards identification) to 397.64 release
* Added hamsi,bmw,whirpool and echo Algos for AMD
* Added allium algo for NVIDIA
* Added x16r for CPU



---MINERS CHANGES:

* Updated AMD SgminerAver to 1.4 Release
* Updated CPU cpuminer Jayddee to 3.8.8.1
* Updated CPU xmrig to 2.6.2
* Added NVDIA SuprminerSP 4a
* Added NVDIA Ccminer for Allium


---BUG FIXES:
* X16r,Blake2s and Neoscrypt not working for Unimining.net
* Nicehash not using europe location



--RELEASE NOTES
If you want to reuse your old config.txt file, and you want to use new EthLargementPill feature you must add this section @@ETHLARGEMENTPILL=ENABLED
If you use new ETHlargementpill feature you must delete ETHASH
full member
Activity: 322
Merit: 105
Hi

I did updater nVidia drivers to latest 397.64 and now Megaminer wont start up.
If I run GPULIST.bat only that it shows is that pause command "Press any key to continue", but no any GPU´s

When I start it using start.bat what was working just fine before update I do get next messages:

First message:

"WARNING: No gpus for group  was detected, activity based watchdog will be disabled for that group, this can happens if AMD beta blockchain drivers are installed or incorrect
@@gpugroups config"

Second message "NO MINERS!"

And this is log:
Code:
05/09/2018 18:58:49...... Release 6.2.1
05/09/2018 18:58:50...... Starting Parameters:  //Algorithm:  //PoolsName: Zpool //CoinsName:  //MiningMode: AUTOMATIC //Groupnames:  //PercentToSwitch:
05/09/2018 18:58:50...... No gpus for group  was detected, activity based watchdog will be disabled for that group, this can happens if AMD beta blockchain drivers are installed or incorrect @@gpugroups config
05/09/2018 18:59:00...... New interval starting.............
05/09/2018 18:59:34...... "AverageCpu = 2 % | MemoryUsage = 19,00 % | VirtualMemoryUsage = 9,42 % |  PercentCFree = 88,44 % | Processes = 121 | Connections = 46"
05/09/2018 18:59:34...... Next interval will be 300
05/09/2018 18:59:34...... Loading Pools Information.............
05/09/2018 18:59:34...... Pool Zpool was responsive....
05/09/2018 18:59:34...... Detected 33 pools......
05/09/2018 18:59:34...... 33 pools left after min workers filter.....
05/09/2018 18:59:34...... Coindesk api was responsive..........
05/09/2018 18:59:34...... Files in miner folder: 46
05/09/2018 18:59:34...... Number of gpu groups: 0
05/09/2018 18:59:34...... Miners/Pools combinations detected: 0.........
05/09/2018 18:59:34...... NO MINERS!



All GPU´s are shown in device manager and miners launched from command prompt works just fine, excavator works fine.

[UPDATE] Reverting back to 391.35 everything work like it should.


I have installed 397.64  and no problem here, I will upload today new code to github master with nvdia-smi updated to this release.
full member
Activity: 322
Merit: 105
can i use it on windows 10 32bit system or not?

I will guess that the answer will be yes/no. Some of the miners that MegaMiner uses may require a 64bit platform.

true, you can use but you must delete all 64 bits miners or replace manually for 32 bits releases
newbie
Activity: 39
Merit: 0
can i use it on windows 10 32bit system or not?

I will guess that the answer will be yes/no. Some of the miners that MegaMiner uses may require a 64bit platform.
newbie
Activity: 55
Merit: 0
can i use it on windows 10 32bit system or not?
full member
Activity: 322
Merit: 105
how do i specific a coin? i want to mine rvn. 

You can use start.bat selecting manual mode or also you can use coinsname parameter in your batch file like examples.
newbie
Activity: 55
Merit: 0
how do i specific a coin? i want to mine rvn. 
newbie
Activity: 27
Merit: 5
Hi

I did updater nVidia drivers to latest 397.64 and now Megaminer wont start up.
If I run GPULIST.bat only that it shows is that pause command "Press any key to continue", but no any GPU´s

When I start it using start.bat what was working just fine before update I do get next messages:

First message:

"WARNING: No gpus for group  was detected, activity based watchdog will be disabled for that group, this can happens if AMD beta blockchain drivers are installed or incorrect
@@gpugroups config"

Second message "NO MINERS!"

And this is log:
Code:
05/09/2018 18:58:49...... Release 6.2.1
05/09/2018 18:58:50...... Starting Parameters:  //Algorithm:  //PoolsName: Zpool //CoinsName:  //MiningMode: AUTOMATIC //Groupnames:  //PercentToSwitch:
05/09/2018 18:58:50...... No gpus for group  was detected, activity based watchdog will be disabled for that group, this can happens if AMD beta blockchain drivers are installed or incorrect @@gpugroups config
05/09/2018 18:59:00...... New interval starting.............
05/09/2018 18:59:34...... "AverageCpu = 2 % | MemoryUsage = 19,00 % | VirtualMemoryUsage = 9,42 % |  PercentCFree = 88,44 % | Processes = 121 | Connections = 46"
05/09/2018 18:59:34...... Next interval will be 300
05/09/2018 18:59:34...... Loading Pools Information.............
05/09/2018 18:59:34...... Pool Zpool was responsive....
05/09/2018 18:59:34...... Detected 33 pools......
05/09/2018 18:59:34...... 33 pools left after min workers filter.....
05/09/2018 18:59:34...... Coindesk api was responsive..........
05/09/2018 18:59:34...... Files in miner folder: 46
05/09/2018 18:59:34...... Number of gpu groups: 0
05/09/2018 18:59:34...... Miners/Pools combinations detected: 0.........
05/09/2018 18:59:34...... NO MINERS!



All GPU´s are shown in device manager and miners launched from command prompt works just fine, excavator works fine.

[UPDATE] Reverting back to 391.35 everything work like it should.
Pages:
Jump to: