 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
Please add support for mining BEAM on NiceHash. NiceHash requires a change in stratum protocol for equihash 150,5. Job message contains additional parameter "nonceprefix", which follows the same rules as "nonceprefix" field in the login response. Protocol specifications: https://github.com/nicehash/Specifications/blob/master/Beam_NiceHash_v1.0.txtAfter the required change, Gminer could be added to NiceHashMiner Legacy - currently used by more than 70k miners. GMiner already supports "nonceprefix" feature for BEAM stratum There is a difference, BEAM stratum sends nonceprefix in a response to the login method, that is only sent at the start of the mining. NiceHash protocol has nonceprefix parameter in a job message (nonceprefix field is sent for every job). |
|
|
|
Please add support for mining BEAM on NiceHash. NiceHash requires a change in stratum protocol for equihash 150,5. Job message contains additional parameter "nonceprefix", which follows the same rules as "nonceprefix" field in the login response. Protocol specifications: https://github.com/nicehash/Specifications/blob/master/Beam_NiceHash_v1.0.txtAfter the required change, Bminer could be added to NiceHashMiner Legacy - currently used by more than 70k miners. |
|
|
|
Please add support for mining BEAM on NiceHash. NiceHash requires a change in stratum protocol for equihash 150,5. Job message contains additional parameter "nonceprefix", which follows the same rules as "nonceprefix" field in the login response. Protocol specifications: https://github.com/nicehash/Specifications/blob/master/Beam_NiceHash_v1.0.txtAfter the required change, Gminer could be added to NiceHashMiner Legacy - currently used by more than 70k miners. |
|
|
|
Hello please help move to nicehash-skunkhash this script I use excavator 1.5.11 i just don't know what is write. Official site nicehash tells only for Micro$$$oft window$$ https://www.nicehash.com/news/206where i must write a btc address??? [ {"time":0,"commands":[ {"id":1,"method":"algorithm.add","params":["skunkhash", "skunk.eu.nicehash.com:3362","dj--alex.rig1:x"]} ]} , {"time":3,"commands":[ {"id":1,"method":"worker.add","params":["0","0"]} ]}, {"time":10,"loop":10,"commands":[ {"id":1,"method":"algorithm.print.speeds","params":[]} ]} ] excavator -p 0 -c skunk-nice-very-nice.json Hey, excavator doesn't support skunk algorithm. You can use NiceHash Miner Legacy or some third party miner (e.g. ccminer). Link to NiceHash Miner Legacy - https://github.com/nicehash/NiceHashMinerLegacy/releases |
|
|
|
Hello friends, dropky
@dropky, can you help me?
1- Using the algo-switching manually on Excavator(and at Nicehash servers), just like exemplified on command_file_switching_example.json, it would switch based on nicehash statistics? just like excavator changes when used by nicehash app? and are the earnings identical?
2- I'll use excavator from nicehash install, it would read my benchmarks made by nicehash exe before?
3- And where to add some overclocking params before each algo switch at "command_file_switching_example.json"?
I only wants to switch between Lyra2Rev2 and DaggerHashimoto, for one device, at nicehash, and based on my benchmarks which is lyra2rev2 = 69.3 MH/hs, and DaggerHashimoto 53.6 MH/s, and then add some overclock setup before each algo-switching, any example for this?
Any help???
Pleeease
1 - No, excavator doesn't perform auto switching and it doesn't receive any information for current algorithm profitability on its own. The command_file_switching_example.json file shows how the API can be used for easy algorithm switching in case you're developing your own application. 2 - Excavator doesn't read any benchmarks, that's all NiceHash Miner. Excavator doesn't make any decisions on its own. It has to be told what algorithm to mine, on which card, on what time. 3 - You can pass different OC settings through API (device related methods). But currently NiceHash Miner 2 doesn't support that, so either wait for NiceHash Miner 3  , write your own program/script or use a third party application that is build around excavator (I know that MinerPro for NiceHash supports individual overclocking for each algorithm). |
|
|
|
Increase pagefile to 56 GB (7 x 8gb). Which driver are you using? Also, recheck all your risers, PSU connectors, if everything is connected ok.
The latest nVidia drivers. What's the general consensus on the most stable drivers? Have you increased the pagefile? I haven't tried the latest drivers yet, usually I wait for a while. Currently I'm running 390.65 and I don't have any problems. |
|
|
|
I am converting some rigs from nvOC (ubuntu) / nicehash-equihash to windows using nicehash miner. All rigs were rock solid stable under nvOC.
So far my 5*1080ti rig converted well and accepts the ETHlargementpill no problem, with good benchmark results.
But I'm having problems with my 6*1080 + 1*1070ti rig. Even with no pill and no overclock (just power limit adjust), my rig will reboot within 5 seconds - 10 minutes of mining with NHM.
daggerhashimoto will result in an almost instant reboot, whereas something like lyra2rev2, it will mine for 5 minutes and then reboot.
Any ideas on troubleshooting?
* Mobo is ASUS Z270-P, using 7 risers, one of which is using M2_1 slot.
* Only 4GB RAM. I have adjusted pagefile to 32GB.
* Windows installed on a 120GB SSD.
Increase pagefile to 56 GB (7 x 8gb). Which driver are you using? Also, recheck all your risers, PSU connectors, if everything is connected ok. |
|
|
|
hi
i want use excavator mining multi algo switching . please help how can set it
i try default command_file_switching_example.json but not work
command_file_switching_example.json file is just an example demonstrating how to use the excavator API in switching. I suggest you to use NiceHash Miner ( https://miner.nicehash.com/), it runs excavator and it includes auto switching. |
|
|
|
Why first accepted share (in green) is always number 10? Never seen any lower numbers.
We start counting shares at 10, so the first accepted share is always number 10. When we used standard stratum protocol, it came in handy because we could use lower numbers (0-9) for other custom messages between server and miner. Now with our custom protocol we could start counting at 0 but I guess we got used to counting from 10  So the 10 equals to 1 share? Yes |
|
|
|
Why first accepted share (in green) is always number 10? Never seen any lower numbers.
We start counting shares at 10, so the first accepted share is always number 10. When we used standard stratum protocol, it came in handy because we could use lower numbers (0-9) for other custom messages between server and miner. Now with our custom protocol we could start counting at 0 but I guess we got used to counting from 10 |
|
|
|
@Dropky, Thank you very much for your help. I would like to confirm : for the BTC address, should I add ":x" behind my BTC address (like the one with Excavator 1.4.4a), or, no need to add those ":x" (just my BTC address) with v1.5.4a now ? FYI, I did have 6 GPUs. I don't know why Awesome Miner made the config with 13 devices. Should I edit it to only 6 devices, or, should I just leave it that way? Please advise. Thanks. There is no need to add :x behind your BTC address. Yes, I would advise you to edit your config file for 6 GPUs, but it should work either way, excavator is ignoring commands send for devices that do not exist. |
|
|
|
Ok, I see the problem, we modified excavator API with 1.5.x versions. Try this (change btc address in subscribe method):
[
{"time":1,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.jp.nicehash.com:3200","BTC address"]}
]},
{"time":2,"commands":[
{"id":1,"method":"algorithm.add","params":["lyra2rev2"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["lyra2rev2", "0"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "1"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "2"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "3"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "4"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "5"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "6"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "7"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "8"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "9"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "10"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "11"]},
{"id":1,"method":"worker.add","params":["lyra2rev2", "12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speeds","params":[]},
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]
FYI, you said you have 6 devices in the rig, the config file is made for 13 GPUs. |
|
|
|
@Dropky or anyone,
I want to setup my Awesome Miner to use Excavator 1.5.4a mining Lyra2REv2 at Nicehash, but it doesn't work.
How should I setup it with AM? Should I setup the Json file ?
I have 6 of GTX 1070 TI.
Please help. Thanks.
I'm not familiar how Awesome Miner passes the commands to Excavator. Probably through the config file, can you post here the json file you mentioned? |
|
|
|
|
@pupkinv From version 1.5.0 excavator supports only NiceHash stratums.
|
|
|
|
I'm try benchmark new lyra2z support. lyra2z-bench.json [
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["lyra2z","benchmark"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]
Benchmart starting, but but speed is "0 H/s" Console output: excavator.exe -c lyra2z-bench.json -f 0 -fn logfile.txt
=========================== www.nicehash.com =========================
Excavator v1.5.4a_nvidia GPU Miner for NiceHash.
Copyright (C) 2018 NiceHash. All rights reserved.
=========================== www.nicehash.com =========================
Build time: 2018-05-30 12:41:07
Build number: 5688
Provided startup commandline:
excavator.exe -c lyra2z-bench.json -f 0 -fn logfile.txt
[00:30:46][0x0000012c][info] Log started
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080 Ti
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080 Ti
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080 Ti
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080 Ti
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080 Ti
[00:30:47][0x0000012c][info] core | Found CUDA device: GeForce GTX 1080 Ti
[00:30:47][0x0000012c][info] api | Listening on 127.0.0.1:3456
[00:30:47][0x0000012c][info] core | Initialized!
[00:30:47][0x00000b8c][info] net | lyra2z | New job 'benchmarkjob', diff=1
[00:30:57][0x00000b8c][info] core | Algorithm 'lyra2z' speed: 0.000000 H/s
[00:31:07][0x0000012c][info] core | Algorithm 'lyra2z' speed: 0.000000 H/s
[00:31:17][0x00000b8c][info] core | Algorithm 'lyra2z' speed: 0.000000 H/s
[00:31:27][0x0000012c][info] core | Algorithm 'lyra2z' speed: 0.000000 H/s
[00:31:29][0x0000012c][info] Shutting down
[00:31:29][0x0000012c][info] api | Closing
Log file here https://dropmefiles.com/AQKx1Could you help? We made some changes to the API in 1.5.x versions. Replace worker.add with: {"id":1,"method":"worker.add","params":["lyra2z","0"]}From now on algorithm has to be assigned by name, not id. |
|
|
|
Guys, could someone share the .json file for 6 videocards for equihash (EU) which works nice for you.
[
{"time":1,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","Bitcoin_Address.Worker_Name"]}
]},
{"time":2,"commands":[
{"id":1,"method":"worker.add","params":["0","0","0"]},
{"id":1,"method":"worker.add","params":["0","1","0"]},
{"id":1,"method":"worker.add","params":["0","2","0"]},
{"id":1,"method":"worker.add","params":["0","3","0"]},
{"id":1,"method":"worker.add","params":["0","4","0"]},
{"id":1,"method":"worker.add","params":["0","5","0"]}
]},
{"time":5,"commands":[
{"id":1,"method":"device.set.tdp","params": ["0","95"]},
{"id":1,"method":"device.set.core_delta","params": ["0","100"]},
{"id":1,"method":"device.set.memory_delta","params":["0","680"]},
{"id":1,"method":"device.set.tdp","params": ["1","95"]},
{"id":1,"method":"device.set.core_delta","params": ["1","100"]},
{"id":1,"method":"device.set.memory_delta","params":["1","680"]},
{"id":1,"method":"device.set.tdp","params": ["2","95"]},
{"id":1,"method":"device.set.core_delta","params": ["2","100"]},
{"id":1,"method":"device.set.memory_delta","params":["2","680"]},
{"id":1,"method":"device.set.tdp","params": ["3","95"]},
{"id":1,"method":"device.set.core_delta","params": ["3","100"]},
{"id":1,"method":"device.set.memory_delta","params":["3","680"]},
{"id":1,"method":"device.set.tdp","params": ["4","95"]},
{"id":1,"method":"device.set.core_delta","params": ["4","100"]},
{"id":1,"method":"device.set.memory_delta","params":["4","680"]},
{"id":1,"method":"device.set.tdp","params": ["5","95"]},
{"id":1,"method":"device.set.core_delta","params": ["5","100"]},
{"id":1,"method":"device.set.memory_delta","params":["5","680"]}
]},
{"time":10,"commands":[
{"id":1,"method":"worker.reset","params":["0"]},
{"id":1,"method":"worker.reset","params":["1"]},
{"id":1,"method":"worker.reset","params":["2"]},
{"id":1,"method":"worker.reset","params":["3"]},
{"id":1,"method":"worker.reset","params":["4"]},
{"id":1,"method":"worker.reset","params":["5"]}
]},
{"time":15,"loop":20,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]},
{"event":"on_quit","commands":[
{"id":1,"method":"device.set.tdp","params": ["0","100"]},
{"id":1,"method":"device.set.core_delta","params": ["0","0"]},
{"id":1,"method":"device.set.memory_delta","params":["0","0"]},
{"id":1,"method":"device.set.tdp","params": ["1","100"]},
{"id":1,"method":"device.set.core_delta","params": ["1","0"]},
{"id":1,"method":"device.set.memory_delta","params":["1","0"]},
{"id":1,"method":"device.set.tdp","params": ["2","100"]},
{"id":1,"method":"device.set.core_delta","params": ["2","0"]},
{"id":1,"method":"device.set.memory_delta","params":["2","0"]},
{"id":1,"method":"device.set.tdp","params": ["3","100"]},
{"id":1,"method":"device.set.core_delta","params": ["3","0"]},
{"id":1,"method":"device.set.memory_delta","params":["3","0"]},
{"id":1,"method":"device.set.tdp","params": ["4","100"]},
{"id":1,"method":"device.set.core_delta","params": ["4","0"]},
{"id":1,"method":"device.set.memory_delta","params":["4","0"]},
{"id":1,"method":"device.set.tdp","params": ["5","100"]},
{"id":1,"method":"device.set.core_delta","params": ["5","0"]},
{"id":1,"method":"device.set.memory_delta","params":["5","0"]}
]}
]
Or you can try my application. It will help you much more than this JSON : https://github.com/EvgeniyKorepov/MinerPro-for-NiceHash@EvgeniyKorepov This json file is incorrect. You forgot the algorithm.add method, the first parameter in worker.add has to be the name of the algorithm, also M=0 is not the fastest option for equihash. If you're using M=0 parameter you should definitely use two workers per device to get better results. FYI, we added worker.print.speeds method, you might find it useful @dimytr Here is the correct example (without overclocking): [
{"time":0,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","btc_address.worker_name"]}
]},
{"time":2,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["equihash","0"]},
{"id":1,"method":"worker.add","params":["equihash","1"]},
{"id":1,"method":"worker.add","params":["equihash","2"]},
{"id":1,"method":"worker.add","params":["equihash","3"]},
{"id":1,"method":"worker.add","params":["equihash","4"]},
{"id":1,"method":"worker.add","params":["equihash","5"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"algorithm.print.speeds","params":[]}
]}
]
|
|
|
|
|
