Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 3.2.0 Beta 5a is ready #2257

Closed
UselessGuru opened this issue Nov 27, 2018 · 39 comments
Closed

Version 3.2.0 Beta 5a is ready #2257

UselessGuru opened this issue Nov 27, 2018 · 39 comments

Comments

@UselessGuru
Copy link
Contributor

UselessGuru commented Nov 27, 2018

https://github.com/MultiPoolMiner/MultiPoolMiner/releases/tag/Beta3.2.0

Please also report if all is working fine - only so I can know that we get rid of all the bugs :-)

@UselessGuru UselessGuru self-assigned this Nov 27, 2018
@UselessGuru UselessGuru changed the title Version 3.2.0 Beta 5 is ready Version 3.2.0 Beta 5a is ready Nov 27, 2018
@skovesh
Copy link

skovesh commented Nov 27, 2018

What am I doing wrong? Mining is on my main BTC wallet, although I have a config.txt with various wallets.
Ravenminer is ignored !
Config.zip
MultiPoolMiner_2018-11-27.zip
Start.bat.txt
Thanks !

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 27, 2018

Mining is on my main BTC wallet

You need to add a wallet section to each pool config like this:

    "AHashPool": {
      "User": "s_kovesh",
      "Worker": "multipoolminer",
      "Wallets":  {
          "BTC":  "1H4xhbgThzeQLyjtz1LifgW9Bkojgjdyy5"
      },
      "API_ID": 0,
      "API_Key": "",
      "PricePenaltyFactor": 1.0
    },

Note: You can remove the 'wallets' element all together it you want to inherit the values from $Config.Wallets. Your original config is doing exactly this because there are no 'Wallets' elements, and that is why it is mining to your main BTC wallet.

For Nicehash (which I believe you have an NH internal address) you can configure like this:

    "NiceHash": {
      "User": "s_kovesh",
      "Worker": "multipoolminer",
      "Wallets":  {
          "BTC":  "34hZew4mSvJy6QM67xennM8qzJFXRwLiEt"
      },
      "IsInternalWallet":  true,
      "API_ID": 1346209,
      "API_Key": "c7529297-483d-a0f0-5388-f41f1a918e51",
      "PricePenaltyFactor": 1.0
    },

You can always verify the running config at http://localhost:3999/config

@torsrex
Copy link

torsrex commented Nov 27, 2018

The aforementioned issues have been fixed, except for xmrig not creating the configuration files properly.
Here's an excerpt from the logfile:

11-27 18:30:27 INFO: Starting miner (CPU-XmrigCryptonight_v2.8.3-CPU#00-1 {CryptonightV7@NiceHash}). 
2018-11-27 18:30:27 VERBOSE: Bin\CPU-XmrigCryptonight_v2.8.3\xmrig.exe --url=stratum+tcp://cryptonightv7.eu.nicehash.com:3363 --userpass=MINER_ADDRESS.worker1:x --rig-id= --keepalive --nicehash --config=NiceHash-Europe-CryptonightV7-GenuineIntel4CoreCPU-4003-MINER_ADDRESS.worker1-x-1.json
2018-11-27 18:30:28 WARNING: Benchmarking miner (CPU-XmrigCryptonight_v2.8.3-CPU#00-1 {CryptonightV7@NiceHash}) [Attempt 1 of max. 3]. 
2018-11-27 18:30:28 WARNING: Benchmarking in progress: 5 miners left to complete benchmark.
2018-11-27 18:30:28 INFO: Start waiting before next run. 
2018-11-27 18:30:33 VERBOSE: CPU-XmrigCryptonight_v2.8.3-CPU#00-1:  
2018-11-27 18:30:34 VERBOSE: AMD-JCECryptonote_v0.33b6-GPU#00-GPU#01: ["",{"hashrate":{"thread_0":204.79,"thread_1":204.4,"thread_2":211.62,"thread_3":211.84,"thread_all":"204.79 204.4 211.62 211.84","thread_gpu":"409.18 423.45","total":832.63,"max":856.76},"result":{"wallet":"MINER_ADDRESS.worker1","pool":"cryptonightv8.eu.nicehash.com:3367","ssl":false,"reconnections":0,"currency":"Nicehash","difficulty":100001,"shares":1,"hashes":100001,"uptime":"0:06:15","effective":266.67},"gpu_status":["@{index=0; temperature=81; fan=64; processor=Pitcairn; memory=2048; good_shares=0; bad_shares=0}","@{index=1; temperature=76; fan=55; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}"],"miner":{"version":"jce/0.33b-y/gpu","platform":"Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz","system":"Windows 64-bits","algorithm":"15"}}]
2018-11-27 18:30:34 INFO: Pinging monitoring server. 
2018-11-27 18:30:34 INFO: Miner Status (https://multipoolminer.io/monitor/miner.php): Success
2018-11-27 18:30:39 VERBOSE: CPU-XmrigCryptonight_v2.8.3-CPU#00-1:  
2018-11-27 18:30:40 VERBOSE: AMD-JCECryptonote_v0.33b6-GPU#00-GPU#01: ["",{"hashrate":{"thread_0":204.0,"thread_1":203.8,"thread_2":212.05,"thread_3":211.84,"thread_all":"204 203.8 212.05 211.84","thread_gpu":"407.79 423.88","total":831.67,"max":856.76},"result":{"wallet":"MINER_ADDRESS.worker1","pool":"cryptonightv8.eu.nicehash.com:3367","ssl":false,"reconnections":0,"currency":"Nicehash","difficulty":100001,"shares":1,"hashes":100001,"uptime":"0:06:21","effective":262.47},"gpu_status":["@{index=0; temperature=81; fan=64; processor=Pitcairn; memory=2048; good_shares=0; bad_shares=0}","@{index=1; temperature=76; fan=55; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}"],"miner":{"version":"jce/0.33b-y/gpu","platform":"Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz","system":"Windows 64-bits","algorithm":"15"}}]
2018-11-27 18:30:45 VERBOSE: CPU-XmrigCryptonight_v2.8.3-CPU#00-1:  
2018-11-27 18:30:47 VERBOSE: AMD-JCECryptonote_v0.33b6-GPU#00-GPU#01: ["",{"hashrate":{"thread_0":203.8,"thread_1":204.49,"thread_2":212.05,"thread_3":212.05,"thread_all":"203.8 204.49 212.05 212.05","thread_gpu":"408.29 424.09","total":832.38,"max":856.76},"result":{"wallet":"MINER_ADDRESS.worker1","pool":"cryptonightv8.eu.nicehash.com:3367","ssl":false,"reconnections":0,"currency":"Nicehash","difficulty":100001,"shares":2,"hashes":200002,"uptime":"0:06:27","effective":516.8},"gpu_status":["@{index=0; temperature=81; fan=64; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}","@{index=1; temperature=76; fan=55; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}"],"miner":{"version":"jce/0.33b-y/gpu","platform":"Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz","system":"Windows 64-bits","algorithm":"15"}}]
2018-11-27 18:30:52 VERBOSE: CPU-XmrigCryptonight_v2.8.3-CPU#00-1:  
2018-11-27 18:30:53 VERBOSE: AMD-JCECryptonote_v0.33b6-GPU#00-GPU#01: ["",{"hashrate":{"thread_0":204.4,"thread_1":204.2,"thread_2":213.78,"thread_3":211.62,"thread_all":"204.4 204.2 213.78 211.62","thread_gpu":"408.59 425.4","total":833.98,"max":856.76},"result":{"wallet":"MINER_ADDRESS.worker1","pool":"cryptonightv8.eu.nicehash.com:3367","ssl":false,"reconnections":0,"currency":"Nicehash","difficulty":100001,"shares":2,"hashes":200002,"uptime":"0:06:33","effective":508.91},"gpu_status":["@{index=0; temperature=81; fan=64; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}","@{index=1; temperature=76; fan=55; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}"],"miner":{"version":"jce/0.33b-y/gpu","platform":"Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz","system":"Windows 64-bits","algorithm":"15"}}]
2018-11-27 18:30:58 VERBOSE: CPU-XmrigCryptonight_v2.8.3-CPU#00-1:  
2018-11-27 18:30:58 ERROR: Miner (CPU-XmrigCryptonight_v2.8.3-CPU#00-1 {CryptonightV7@NiceHash}) has failed. 
2018-11-27 18:30:59 VERBOSE: AMD-JCECryptonote_v0.33b6-GPU#00-GPU#01: ["",{"hashrate":{"thread_0":204.4,"thread_1":204.4,"thread_2":211.62,"thread_3":211.84,"thread_all":"204.4 204.4 211.62 211.84","thread_gpu":"408.79 423.45","total":832.23,"max":856.76},"result":{"wallet":"MINER_ADDRESS.worker1","pool":"cryptonightv8.eu.nicehash.com:3367","ssl":false,"reconnections":0,"currency":"Nicehash","difficulty":100001,"shares":2,"hashes":200002,"uptime":"0:06:39","effective":501.26},"gpu_status":["@{index=0; temperature=81; fan=64; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}","@{index=1; temperature=76; fan=55; processor=Pitcairn; memory=2048; good_shares=1; bad_shares=0}"],"miner":{"version":"jce/0.33b-y/gpu","platform":"Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz","system":"Windows 64-bits","algorithm":"15"}}]
2018-11-27 18:30:59 INFO: Finish waiting before next run. 

The 'CPU-XmrigCryptonight_v2.8.3' directory only contains the xmrig file after the benchmark run, perchance there is an error with creating these? Thank you kindly for your quick replies.
image

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 27, 2018

except for xmrig not creating the configuration files properly.

I just testest again - I cannot reproduce the issue. MPM created the config files as designed.

Did you overwrite all APIs\* files as well as the MinersLegacy\* files as recommended?
Does your MPM path contain spaces???

@ALL

Does anyone else see the same issues? Comments are welcome!

@torsrex
Copy link

torsrex commented Nov 27, 2018

I tried with a fresh install directly in a subfolder test located at 'c:\test' using the supplied 'Start-MiningPoolHub.bat' file, but no dice. The path contains no spaces. All 'APIs*' and 'MinersLegacy*' files were overwritten. Let me know if you need any additional info to troubleshoot the issue!

I do get this red text while benchmarking if that could be helpful:

Write-Log : Miner (CPU-XmrigCryptonight_v2.8.3-1xGenuineIntel4CoreCPU-1 {CryptonightV8@MiningPoolHubCoins}) has failed.
At C:\test\MultiPoolMiner.ps1:955 char:17
+ ...             Write-Log -Level Error "Miner ($($Miner.Name) {$(($Miner. ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 27, 2018

I do get this red text while benchmarking if that could be helpful:

Unfortunately not. ;-)

Can you please when MPM is running:

  • goto http://localhost:3999/miners.html
  • search for one of the CPU-XmrigCryptonight_v2.8.3 miners (it doesn't matter which instance)
  • click + to expand
  • copy & paste the text that pops up, and post it here

This allows me to gather the parameters that are being passed to the miner API file.

Can you see some error messages on the miner screen when this happens? At least for troubleshooting I recommend you enable 'ShowMinerWindow'

@torsrex
Copy link

torsrex commented Nov 28, 2018

Here's the content of 'CPU-XmrigCryptonight_v2.8.3-1xGenuineIntel4CoreCPU-2':

Path: "C:\\Users\\torst\\Desktop\\MultiPoolMiner\\MultiPoolMiner_3_2_0_Beta5a\\Bin\\CPU-XmrigCryptonight_v2.8.3\\xmrig.exe"

HashSHA256: "19600AEAD9EBC509DB57538E5ACE0A30604708C051B34F81C0BDC1B587624434"

Arguments: "{\"ConfigFile\":{\"FileName\":\"NiceHash-Europe-CryptonightV8-GenuineIntel4CoreCPU-4003-MINER_ADDRESS.worker1-x-2.json\",\"Content\":{\"algo\":\"cryptonight/2\",\"api\":{\"port\":\"4003\",\"access-token\":null,\"worker-id\":null},\"background\":false,\"cuda-bfactor\":10,\"colors\":true,\"donate-level\":1,\"log-file\":null,\"print-time\":5,\"retries\":5,\"retry-pause\":5,\"threads\":[]}},\"Commands\":\"--url=stratum+tcp://cryptonightv8.eu.nicehash.com:3367 --userpass=MINER_ADDRESS.worker1:x --rig-id= --keepalive --nicehash --config=NiceHash-Europe-CryptonightV8-GenuineIntel4CoreCPU-4003-MINER_ADDRESS.worker1-x-2.json\",\"ThreadsConfigFileName\":\"ThreadsConfig-CryptonightV8-GenuineIntel4CoreCPU.json\",\"Threads\":2,\"HwDetectCommands\":\"--url=stratum+tcp://cryptonightv8.eu.nicehash.com:3367 --userpass=MINER_ADDRESS.worker1:x --rig-id= --keepalive --nicehash --config=ThreadsConfig-CryptonightV8-GenuineIntel4CoreCPU.json\"}"

API: "XmRig"

Port: "4003"

URI: "https://github.com/xmrig/xmrig/releases/download/v2.8.3/xmrig-2.8.3-msvc-win64.zip"

Name: "CPU-XmrigCryptonight_v2.8.3-1xGenuineIntel4CoreCPU-2"

BenchmarkIntervals: 1

HashRates: {"CryptonightV8":0}

Fees: {"CryptonightV8":0.01}

Pools: {"CryptonightV8":"@{Algorithm=CryptonightV8; CoinName=; Price=9.366098025E-08; StablePrice=9.36488697498093E-08; MarginOfError=0.0165600764056523; Protocol=stratum+tcp; Host=cryptonightv8.eu.nicehash.com; Port=3367; User=MINER_ADDRESS.worker1; Pass=x; Region=Europe; SSL=False; Updated=11/28/2018 02:40:11; Fee=0.03; Name=NiceHash; Price_Bias=9.23069284504561E-08; Price_Unbias=9.08511508425E-08}"}

Profits: {"CryptonightV8":0}

Profits_Comparison: {"CryptonightV8":0}

Profits_Bias: {"CryptonightV8":0}

Profits_Unbias: {"CryptonightV8":0}

Profit: 0

Profit_Comparison: 0

Profit_MarginOfError: 0.016560076405652286

Profit_Bias: 0

Profit_Unbias: 0

DeviceName: ["CPU#00"]

tDevices: "CPU#00"

tPrimaryAlgorithm: "CryptonightV8"

tSecondaryAlgorithm: undefined

tPrimaryHashRate: 0

tSecondaryHashRate: undefined

This is the output of the miner window during benchmarking:
image

@aaronsta1
Copy link

aaronsta1 commented Nov 28, 2018

xmr-stak is showing this error
[2018-11-27 22:18:52] : Elevating because we need to set up fast memory privileges.
[2018-11-27 22:18:52] : The miner needs to run as administrator, but you passed --noUAC option. Please remove it or set use_slow_memory to always.
Press any key to exit.

also this
AMD-TeamRed_v0.3.7-2xEllesmere4GB_3xEllesmere8GB[2.50%] CryptonightV8 1.49 MH/s 0.12610602 99% 86.68385840 MiningPoolHub-Monero[0.90%]

its showing me as making .126 btc a day.. which is like 500$..

@UselessGuru
Copy link
Contributor Author

Elevating because we need to set up fast memory privileges.

AFAIK Setting up'fast memory privileges' is a one time setting.
I've enabled UAC in the attached modified miner file. Can you see if this works as expected (rename to .ps1 and put it in the MinersLegacy folder)?

AMD_CPU_NVIDIA-FireiceCryptonight_v2.6.0.ps1.txt

AMD-TeamRed_v0.3.7-2xEllesmere4GB_3xEllesmere8GB [...] its showing me as making .126 btc a day..

Don't you like getting rich quickly??? ;-)
Can you reproduce the issue? Please delete the stats file; MPM it will re-benchmark. What speed gets recorded?

@aaronsta1
Copy link

aaronsta1 commented Nov 28, 2018

ok that fixed that..
edit nope take that back.. it wont close now, sgminer just tried to run while xmr-stak was still running.
let me investigate.

but there is also something going on with this

Device: {GPU#00, GPU#03, GPU#04}

Miner[Fee]                                          Algorithm                 Speed BTC/Day Accuracy  BTC/GH/Day Pool[Fee]
----------                                          ---------                 ----- ------- --------  ---------- ---------
AMD-XmrigCryptonight_v2.8.6-3xEllesmere8GB-3[1.00%] CryptonightV8 Benchmark pending Unknown     100% 87.03603750 MiningPoolHubCoins-Monero[0.90%]

xmrig has 3 listings.. one with 2, one with 3 and one with all 5 gpus.

@aaronsta1
Copy link

aaronsta1 commented Nov 28, 2018

hmm, now windows is saying the application has blocked usage of the gpu.
also does the -SSL tag not work anymore? because claymore is saying unsecured.

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 28, 2018

edit nope take that back. it wont close now

How many XmRig instances do you see in the task manager when this happens?
And does the ProcessID match the ProcessId that is stored in the miner object (http://localhost:3999/ -> expand XmRig miner -> ProcessID)
My assumption is that UAC spawns a new process that does not get killed when the parent process ends.

hmm, now windows is saying the application has blocked usage of the gpu.

I've seen this before. But that's a windows issue, nothing that MPM can do anything about it.

also does the -SSL tag not work anymore? because claymore is saying unsecured.

Please be more specific with your problem reports. Screenshots maybe? Which claymore?

@UselessGuru
Copy link
Contributor Author

@torsrex

In your screenshot I see a 'no such file or directory' message... this is cause by the missing config files.
I've added some error message handling stuff to the miner API file. Please rename the attached file to .ps1 and put it in the APIs folder.

Xmrig.ps1.txt

What error message does the miner now throw?

@aaronsta1
Copy link

aaronsta1 commented Nov 28, 2018

Please be more specific with your problem reports. Screenshots maybe? Which claymore?

EthDcrMiner64
when it signs onto the pool it says (unsecure) even tho i have -SSL enabled in the start.bat
same with neoscript miner.
NS: Stratum - Connected (neoscrypt.na.mine.zpool.ca:4233) (unsecure)

and AMD-XmrigCryptonight_v2.8.6-miner is not working right.. it only benchmarks one gpu, so i have a hash rate of 700 H /s
where the other cryptonightv8 shows 2.7KH/s

@UselessGuru
Copy link
Contributor Author

@aaronsta1

Please post http://localhost:3999/runningconfig.html & the command lines for each of the problematic miners (can be found in the log files)

@torsrex
Copy link

torsrex commented Nov 28, 2018

The miner throws the same error message using the modified 'Xmrig.ps1' file and 'MultiPoolMiner_3_2_0_Beta5a':
image

I downloaded 'MultiPoolMiner_3_2_0_Beta4a' and extracted it to a separate folder, and it created the config files successfully:
image
image

@UselessGuru
Copy link
Contributor Author

@torsrex

No red messages? And why there is now one config file in the miner directory?

@aaronsta1
Copy link

aaronsta1 commented Nov 28, 2018

http://localhost:3999/runningconfig.html

says SSL: true.. also
claymore equihash has this
stratum+ssl://us-east.equihash-hub.miningpoolhub.com:20594
but
claymore neoscrypt and ethminer has this
stratum+tcp://neoscrypt.na.mine.zpool.ca:4233
-epool us-east.ethash-hub.miningpoolhub.com:17020

which are not the SSL urls.

@UselessGuru
Copy link
Contributor Author

@aaronsta1

Please post http://localhost:3999/runningconfig.html and not just an extract. I need the full information.

@torsrex
Copy link

torsrex commented Nov 28, 2018

My apologies for providing ambigous feedback. Let me try to clarify ^^
The first screenshot shows the behavior of MultiPoolMiner_3_2_0_Beta5a. The config files don't exist, and both the miner and xmrig throws the same error. Here's the red error message from MultipoolMiner:

Write-Log : Miner (CPU-XmrigCryptonight_v2.8.3-1xGenuineIntel4CoreCPU-2 {CryptonightV8@NiceHash}) has failed.
At C:\Users\torst\Desktop\MultiPoolMiner\MultiPoolMiner_3_2_0_Beta5a\MultiPoolMiner.ps1:955 char:17
+ ...             Write-Log -Level Error "Miner ($($Miner.Name) {$(($Miner. ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log

The second two screenshots show the behavior of a separate installation of a previous version of MultipoolMiner (MultiPoolMiner_3_2_0_Beta4a) where it manages to create one config file.

@aaronsta1
Copy link

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 28, 2018

@torsrex / @aaronsta1

I am puzzled why the Beta 5a version is not working well. The only real change is the timing that has been altered.
Can you try with the attached files?

XmRig.zip

@UselessGuru
Copy link
Contributor Author

@aaronsta1

but claymore neoscrypt and ethminer has this stratum+tcp://neoscrypt.na.mine.zpool.ca:4233 -epool us-east.ethash-hub.miningpoolhub.com:17020

Not all miners support SSL, e.g. ethminer. Here is the code extract that limes its use to NON-SSL pools:

$Commands | Where-Object {$Pools.(Get-Algorithm $_.Algorithm).Protocol -eq "stratum+tcp" <#temp fix#>}

The -SSL parameter just defines the protocol preference, it does not rule out the usage of NON-SSL pools. This would severely limit profitability.

I am looking at a better SSL config implementation, but htat is not as easy as it seems ;-(

@torsrex
Copy link

torsrex commented Nov 28, 2018

Using the attached files, the miner still shows the following error:

Write-Log : Miner (CPU-XmrigCryptonight_v2.8.3-1xGenuineIntel4CoreCPU-1 {CryptonightV8@MiningPoolHubCoins}) has failed.
At C:\Users\torst\Desktop\MultiPoolMiner\MultiPoolMiner_3_2_0_Beta5a\MultiPoolMiner.ps1:955 char:17
+ ...             Write-Log -Level Error "Miner ($($Miner.Name) {$(($Miner. ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log

XmRig still displays:

unable to open NiceHash-Europe-CryptonightHeavy-GenuineIntel4CoreCPU-4003-MINER_ADDRESS.worker1-x-2.json: no such file or directory

and the json file(s) don't exist in the xmrig folder.

@aaronsta1
Copy link

aaronsta1 commented Nov 28, 2018

I am puzzled why the Beta 5a version is not working well. The only real change is the timing that has been altered.

even with this new file it runs one 1 gpu, 2 gpu and 3 gpu in 3 different sessions.

AMD-XmrigCryptonight_v2.8.6-3xEllesmere8GB-3
AMD-XmrigCryptonight_v2.8.6-2xEllesmere4GB_3xEllesmere8GB-1
AMD-XmrigCryptonight_v2.8.6-2xEllesmere4GB_3xEllesmere8GB-2

but when they run, they only use 1 gpu even tho the proper gpus are listed.

as far as the uac setting in xmr-stak it doesnt work.. it failed to load and crashed the gpu driver.

@torsrex
Copy link

torsrex commented Nov 28, 2018

I copied the json config files generated using 'MultiPoolMiner_3.2.0_Beta4a' and that worked (Xmrig benchmarked successfully), so seems like it's only the generation of the json files that doesn't work.

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 29, 2018

@torsrex

so seems like it's only the generation of the json files that doesn't work.

The generation of the json files is the hard bit.
XmRig ans FireIce (Xmr-Stak) are both very complicated when it comes to create config files. There is no proper way to get the gpu threads config, and there is no documented list :-(
My workaround is to start the miner briefly with an empty config. The miner then auto-creates a config file for ALL gpus. I then grab this file, and filter out the thread info for the selected miners. With this info I create a new 'real' config file that is used for mining.

Next try - I rewrote the whole stuff:

XmRig.zip

@UselessGuru
Copy link
Contributor Author

@aaronsta1

Elevating because we need to set up fast memory privileges.

These AMD driver settings impact hash speed:

  • Huge pages
  • Compute Mode

They might have undesired effects on other programs, so MPM should not interfere.
If desired then they must be set be the user himself, local admin rights are required.

@torsrex
Copy link

torsrex commented Nov 29, 2018

The generation of the json files is the hard bit.
XmRig ans FireIce (Xmr-Stak) are both very complicated when it comes to create config files. There is no proper way to get the gpu threads config, and there is no documented list :-(
My workaround is to start the miner briefly with an empty config. The miner then auto-creates a config file for ALL gpus. I then grab this file, and filter out the thread info for the selected miners. With this info I create a new 'real' config file that is used for mining.
Next try - I rewrote the whole stuff:

That does complicate things a whole lot! I like your way of doing it. Nice workaround ^^
Using the XmRig.zip you provided successfully create the config files, and the miner benchmarks successfully (both for amd and the cpu). I've got two amd gpus, but under the "opencl-platform" entry, it lists 0 twice image. Shouldn't this be 0 and 1 for the two gpus respectively?
Is it possible to add an if-check to see if the files exist and if so, not regenerate them, so they can be modified? Thank you so much for your time!

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 29, 2018

Shouldn't this be 0 and 1 for the two gpus respectively?

It should only have a single digit. Try the attached file (rename to .ps1):

AMD-XmrigCryptonight_v2.8.6.ps1.txt

Is it possible to add an if-check to see if the files exist and if so, not regenerate them,

Which files do you not want to be written every time?

  • ThreadsConfig-* or [Algo]-[GPU*]-*

@torsrex
Copy link

torsrex commented Nov 29, 2018

[Algo]-[GPU*]-* so that custom configurations can be added to these ^^ The attached file only adds a single digit. Here's the config in its entirety in case you'd like to take a look at it

{
  "algo": "cryptonight/1",
  "api": {
    "port": "4000",
    "access-token": null,
    "worker-id": null
  },
  "background": false,
  "cache": true,
  "colors": true,
  "donate-level": 1,
  "log-file": null,
  "print-time": 5,
  "retries": 5,
  "retry-pause": 5,
  "opencl-platform": 0,
  "threads": null
}

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 29, 2018

[Algo]-[GPU*]-* so that custom configurations can be added to these

Try this APIs file (rename to .ps1)

It will NOT overwrite the config files, except when the hardware has changed, e.g GPU added, removed, or GPU order change (if you have different GPU models). A hardware change will change GPU deviceIDs which invalidates the threads config stored in the 'ThreadsConfig-...' file.

Here's the config in its entirety in case you'd like to take a look at it

Your config file is NOT ok.
"threads": null

is wrong. It should look like

{
    "algo":  "cryptonight/1",
    "api":  {
        "port":  "4001",
        "access-token":  null,
        "worker-id":  null
    },
    "background":  false,
    "cache":  true,
    "colors":  true,
    "donate-level":  1,
    "log-file":  null,
    "print-time":  5,
    "retries":  5,
    "retry-pause":  5,
    "opencl-platform":  1,
    "threads":  [
        {
            "index":  0,
            "intensity":  768,
            "worksize":  8,
            "strided_index":  1,
            "mem_chunk":  2,
            "unroll":  8,
            "comp_mode":  false,
            "affine_to_cpu":  false
        },
        {
            "index":  0,
            "intensity":  768,
            "worksize":  8,
            "strided_index":  1,
            "mem_chunk":  2,
            "unroll":  8,
            "comp_mode":  false,
            "affine_to_cpu":  false
        }
    ]
}

Can you please zip all generated json files and post them here.

@torsrex
Copy link

torsrex commented Nov 29, 2018

I think you might have forgotten to attach the file :)

I cleared the stats files and let it benchmark again, and I think they now have the correct format?
Xmrig cpu:
CPU-XmrigCryptonight_v2.8.3.zip

Xmrig amd:
AMD-XmrigCryptonight_v2.8.6.zip

@UselessGuru
Copy link
Contributor Author

I think you might have forgotten to attach the file :)

Not anymore:

Xmrig.ps1.zip

@torsrex
Copy link

torsrex commented Nov 30, 2018

It seems to still rewrite the [Algo]-[GPU*]-* files using the attached file. It's mostly the 'threads' part that's interesting to modify. Presumably you still need to update the [Algo]-[GPU*]-* files with the correct pool, but perhaps it's possible to update only this part?

@UselessGuru
Copy link
Contributor Author

UselessGuru commented Nov 30, 2018

it seems to still rewrite the [Algo]-[GPU*]-* files

This rewrite is necessary cause I need to update the pool info.

but perhaps it's possible to update only this part?

Better you edit the ThreadsConfig file... these values will be imported to the [Algo]-[GPU*]-* config file on each run -> problem solved :-)

@torsrex
Copy link

torsrex commented Nov 30, 2018

That sounds excellent! I did however stumble across an issue while editing the TreadsConfig file.

Here's the TreadsConfig file:

[
  {
    "low_power_mode": 1,
    "affine_to_cpu": 0,
    "asm": true
  },
  {
    "low_power_mode": 1,
    "affine_to_cpu": 2,
    "asm": true
  },
  {
    "low_power_mode": 1,
    "affine_to_cpu": 4,
    "asm": true
  },
  {
    "low_power_mode": 1,
    "affine_to_cpu": 6,
    "asm": true
  }
]

Whereas here's the CryptonightV8-GenuineIntel4CoreCPU-4003-2.json file:

{
    "algo": "cryptonight/2",
    "api": {
        "port": 4003,
        "access-token": null,
        "id": null,
        "worker-id": null,
        "ipv6": false,
        "restricted": true
    },
    "asm": true,
    "autosave": true,
    "av": 0,
    "background": false,
    "colors": false,
    "cpu-affinity": null,
    "cpu-priority": null,
    "donate-level": 1,
    "huge-pages": true,
    "hw-aes": null,
    "log-file": null,
    "max-cpu-usage": 75,
    "pools": [
        {
            "url": "stratum+tcp://cryptonightv8.eu.nicehash.com:3367",
            "user": "MINER_ADRESS.worker1",
            "pass": "x",
            "rig-id": "worker1",
            "nicehash": true,
            "keepalive": false,
            "variant": -1,
            "tls": false,
            "tls-fingerprint": null
        },
        {
            "url": "stratum+tcp://cryptonightv8.eu.nicehash.com:3367",
            "user": "MINER_ADRESS.worker1",
            "pass": "x",
            "rig-id": "worker1",
            "nicehash": true,
            "keepalive": false,
            "variant": -1,
            "tls": false,
            "tls-fingerprint": null
        }
    ],
    "print-time": 5,
    "retries": 5,
    "retry-pause": 5,
    "safe": false,
    "threads": [
        {
            "low_power_mode": 1,
            "affine_to_cpu": false,
            "asm": true
        },
        {
            "low_power_mode": 1,
            "affine_to_cpu": false,
            "asm": true
        },
        {
            "low_power_mode": 1,
            "affine_to_cpu": false,
            "asm": true
        },
        {
            "low_power_mode": 1,
            "affine_to_cpu": false,
            "asm": true
        }
    ],
    "user-agent": null,
    "watch": false
}

It seems like the thread count (it should only be 2 threads for CryptonightV8-GenuineIntel4CoreCPU-4003-2.json) doesn't get set correctly, as well as the config (the affine_to_cpu value in particular) from the TreadsConfig file. Thank you for your continued support regarding xmrig. It's very much appreciated :-)

@UselessGuru
Copy link
Contributor Author

Thank you for your continued support regarding xmrig. It's very much appreciated :-)

Thank you - you are welcome!

It seems like the thread count (it should only be 2 threads for CryptonightV8-GenuineIntel4CoreCPU-4003-2.json) doesn't get set correctly,

Thank you for pointing this out - it a new issue with the CPU variant. I'll fix this.

@UselessGuru
Copy link
Contributor Author

@torsrex

It seems like the thread count (it should only be 2 threads for CryptonightV8-GenuineIntel4CoreCPU-4003-2.json) doesn't get set correctly,

Please try Beta 6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants