Pages:
Author

Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] - page 16. (Read 179296 times)

legendary
Activity: 1564
Merit: 1027

is there any single page where I can learn to create a mining pool? Recently tried and couldn't find a one-stop solution?


There are many guides online, including YouTube. This is not the proper thread for that kind of request.
member
Activity: 98
Merit: 10
Hi All,

How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine  but has slightly lower hash rate.

I'm getting  "error" not expected type: Array

[23:20:00][0x00004010][info] Log started
[23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Initialized!
[23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1)
[23:20:02][0x00002078][info] net | Connected!
[23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"

Thanks! Huh

Here are the specifications of the protocol stratum, the pool should support them https://github.com/nicehash/Specifications

is there any single page where I can learn to create a mining pool? Recently tried and couldn't find a one-stop solution?
member
Activity: 68
Merit: 10
Hi All,

How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine  but has slightly lower hash rate.

I'm getting  "error" not expected type: Array

[23:20:00][0x00004010][info] Log started
[23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Initialized!
[23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1)
[23:20:02][0x00002078][info] net | Connected!
[23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"

Thanks! Huh

Here are the specifications of the protocol stratum, the pool should support them https://github.com/nicehash/Specifications
newbie
Activity: 10
Merit: 0
Hi!

Now in 1.3.8a version on Ubuntu 16.04 I get an error about 1-2 days after start mining and Excavator stops working:

rig03 kernel: [77113.327260] show_signal_msg: 18 callbacks suppressed
rig03 kernel: [77113.327270] excavator[32683]: segfault at 0 ip 00007fa7c52e2c29 sp 00007fa7c20d1b98 er$
rig03 start.sh[32653]: Segmentation fault (core dumped)
rig03 systemd[1]: exc.service: Main process exited, code=exited, status=139/n/a
rig03 systemd[1]: exc.service: Unit entered failed state.
rig03 systemd[1]: exc.service: Failed with result 'exit-code'.

I'll try 1.3.7a and I'll write results late.
newbie
Activity: 10
Merit: 0
Hi All,

How do I make excavator work with p2pool, or what I need to change in the pool to make excavator to work> CC Miner works fine  but has slightly lower hash rate.

I'm getting  "error" not expected type: Array

[23:20:00][0x00004010][info] Log started
[23:20:00][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Found CUDA device: GeForce GTX 1080 Ti
[23:20:02][0x00004010][info] core | Initialized!
[23:20:02][0x00003948][info] net | Connecting to 127.0.0.1:9171 (127.0.0.1)
[23:20:02][0x00002078][info] net | Connected!
[23:20:02][0x00003948][warning] net | Net error: JSON member "error" not expected type: Array
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00002078][warning] net | Net error: JSON member missing: "error"
[23:20:02][0x00003948][warning] net | Net error: JSON member missing: "error"

Thanks! Huh
newbie
Activity: 1
Merit: 0
So i just got this miner for myself, so pretty noob still with it. I have 2 GPU's and i would want to mine with only my secondary one from time to time, how do i do it?
newbie
Activity: 10
Merit: 0
legendary
Activity: 1797
Merit: 1028
EXCAVATOR BENCHMARKS--

After installing Excavator on my Linux rig (instructions at the GitHub site), I ran the bencmark script.  Here are the results:

Excavator Version: v1.3.8a_nvidia                                                                                                                                                                                                                  
OS: Ubuntu 14.04.5 LTS                                                                                                                                                                                                                              
NVIDIA Driver Version: 384.90                                                                                                                                                                                                                      
Found 3 device(s):                                                                                                                                                                                                                                  
GeForce GTX 1070 Ti                                                                                                                                                                                                                                
GeForce GTX 980 Ti                                                                                                                                                                                                                                  
GeForce GTX 980 Ti                                                                                                                                                                                                                                  
Benchmarking with 3 device(s) for 300 seconds for each algorithm...                                                                                                                                                                                
Benchmarking without network connection first...                                                                                                                                                                                                    
equihash: 1.412996 kH/s
pascal: 3.140780 GH/s                                                                                                                                                                                                                              
decred: 8.864810 GH/s                                                                                                                                                                                                                              
sia: 5.674955 GH/s                                                                                                                                                                                                                                  
lbry: 837.269673 MH/s                                                                                                                                                                                                                              
blake2s: 12.842469 GH/s
lyra2rev2: 119.783266 MH/s                                                                                                                                                                                                                          
cryptonight: 1.569471 kH/s                                                                                                                                                                                                                          
daggerhashimoto: 70.255890 MH/s
daggerhashimoto_pascal: 52.603532 MH/s & 2.006996 GH/s                                                                                                                                                                                              
daggerhashimoto_decred: 67.375154 MH/s & 2.927411 GH/s
daggerhashimoto_sia: 68.533263 MH/s & 1.346579 GH/s                                                                                                                                                                                                
Benchmarking with 3 device(s) for 300 seconds for each algorithm...                                                                                                                                                                                
Connectng to usa.nicehash.com...                                                                                                                                                                                                                    
equihash: 1.408922 kH/s (50 acceped, 0 rejected)                                                                                                                                                                                                    
pascal: 2.084523 GH/s (38 acceped, 0 rejected)                                                                                                                                                                                                      
decred: 8.870751 GH/s (124 acceped, 0 rejected)                                                                                                                                                                                                    
sia: 5.676765 GH/s (102 acceped, 0 rejected)                                                                                                                                                                                                        
lbry: 837.882124 MH/s (97 acceped, 0 rejected)                                                                                                                                                                                                      
blake2s: 12.825668 GH/s (194 acceped, 0 rejected)                                                                                                                                                                                                  
lyra2rev2: 119.710346 MH/s (66 acceped, 0 rejected)                                                                                                                                                                                                
cryptonight: 1.536833 kH/s (2 acceped, 1 rejected)                                                                                                                                                                                                  
daggerhashimoto: 52.099698 MH/s (12 acceped, 0 rejected)                                                                                                                                                                                            
daggerhashimoto_pascal: 49.025702 MH/s & 1.836451 GH/s (82 acceped, 1 rejected)                                                                                                                                                                    
daggerhashimoto_decred: 47.552451 MH/s & 2.268395 GH/s (42 acceped, 0 rejected)                                                                                                                                                                    
daggerhashimoto_sia: 50.623493 MH/s & 1.102006 GH/s (32 acceped, 0 rejected)

Things to note!  I had difficulty breaking out of the benchmark process with "control-c" and had to reboot to stop the process.  The word "accepted" is spelled wrong.  The process took more than 2 hours, 22 benchmarks at 300 seconds each.  Neoscrypt is not included in the benchmarks.  My 1070ti is slightly faster than my 980ti cards, at about 1/2 the wattage.     --scryptr
full member
Activity: 224
Merit: 100
CryptoLearner
For user ReallyMe

Refer to the first post of this topic or follow this link to download the excavator binaries on github.

https://github.com/nicehash/excavator (i recommend at that time the 1.3.7a, because i had stability issue with 1.3.8 )

The miner work with json configuration files that will contain everything needed to mine a specific algo (algo, pool, number of GPU's, overclock, miner console settings, etc...), there is an extensive documentation available on the github depot for each and every configuration parameters.

Here is an example configuration for lyra2rev2 mining (monacoin and such) for 6gpus and no overclock specified.

mona_suprnova.json

Code:
[
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["lyra2rev2","mona.suprnova.cc:2995","workerpass.workername"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]},
{"id":2,"method":"worker.add","params":["0","1"]},
{"id":3,"method":"worker.add","params":["0","2"]},
{"id":4,"method":"worker.add","params":["0","3"]},
{"id":5,"method":"worker.add","params":["0","4"]},
{"id":6,"method":"worker.add","params":["0","5"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":2,"method":"worker.print.speed","params":["1"]},
{"id":3,"method":"worker.print.speed","params":["2"]},
{"id":4,"method":"worker.print.speed","params":["3"]},
{"id":5,"method":"worker.print.speed","params":["4"]},
{"id":6,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
]

This configuration file is pretty basic and simple

First portion add the algorithm and pool infos for the mining to start

second portion add the workers per GPU for mining, in the parameters first number equal the worker number of the second number that represent the GPU ID (0,0 = worker 0 of GPU 0), not that depending on the algorithm it's better to define 2 worker per gpu, there is a table explaining that in the nvidia manual of excavator.

third portion is the console output setting, i ask for all my 6gpu to print the current hashrate, and at the end the overall hashrate.

You can expand this configuration file with overclock and such. The manual explain how to do it.

Now to start excavator the most basic way

Quote
excavator.exe -c yourconfig.json

You can also expand the command by adding for example webUI or Json API interface for monitoring.

Quote
excavator.exe -c yourconfig.json -wp my_network_port -wi my_rig_local_ip (or 0.0.0.0 to bind it to all your rig ip's)

Hope it'll help you set it up. Cheers.
legendary
Activity: 1797
Merit: 1028
does anyone has crash issues on 1070 ? whenever i open excavator for neoscrypt sometimes even it freezes the system until i restart again.

At me too does not work, here the details https://github.com/nicehash/excavator/issues/78


MY COMPUTER FREEZES SOLID--

With v1.6.8a, mining CryptoNight worked well, without a sluggish computer response while trying to do other tasks.  However, I have found my computer completely frozen a couple times, no mouse movement, no clock increment, no response to ctrl-alt-del.  I love the system, with the web-interface and console stats.  But, it is still a bit raw.       --scryptr
member
Activity: 68
Merit: 10
does anyone has crash issues on 1070 ? whenever i open excavator for neoscrypt sometimes even it freezes the system until i restart again.

At me too does not work, here the details https://github.com/nicehash/excavator/issues/78
sr. member
Activity: 532
Merit: 250
The harder your life is the more meaning it has.
does anyone has crash issues on 1070 ? whenever i open excavator for neoscrypt sometimes even it freezes the system until i restart again.
newbie
Activity: 2
Merit: 0
If I install excavator and ubuntu 16.04 on my 1070s will excavator still be able to control the clocks just wondering I'm not a linux guy but trying to learn it more than my second question is on my win 10 pro build do I just leave out the clock commands to let AF manage my cards I'm asking because I read somewhere that running excavator would disable msi AF or this is no longer the case

Excavator will not disable MSI Afterburner, you can manage your GPU settings either using command line or third party software (e.g. MSI AF).

Regarding Linux, yes you will still be able to manage GPU through excavator's commands.
Are you sure? I didn't manage to get excavator change GPU settings (clock, memory, fan and TDP). They just do nothing. No errors, but nothing changes. Have to use nvidia-smi and nvidia-settings to make changes for now.
hero member
Activity: 796
Merit: 505
Testing out the 1.3.8 release with neoscrypt algo, doesn't perform as well as KlausT or Alexis CCminer, (getting about 900kH/sec instead of 1.1MH/sec per card), tweaked a bit the B parameters but default one seems to be good, also tried to use dual-worker, but no dice, can't squeeze more from it, need a little more optimisation to be competitive.

keep up the good work  Cool

NEOSCRYPT NEEDS OPTIMIZATION--

I have similar results.  My 1080ti gets about 1.02MH/s with Excavator v1.3.8a, default parameters and default clocks.  With CCminer v2.2.2, default parameters and clocks, it gets about 1.4Mh/s while mining NeoScrypt.  Tweaking the block ("B") parameter did nothing but lessen the hashrate on Excavator.  Mild clock changes did very little to help, also.       --scryptr

Thanks for the feedback. We're still working on optimisations, mainly for the 1080 and 1080 ti cards.

6x 1060 3GB - excavator -> 3.4 MH, ccminer -> 3.9 MH
jr. member
Activity: 132
Merit: 7
Testing out the 1.3.8 release with neoscrypt algo, doesn't perform as well as KlausT or Alexis CCminer, (getting about 900kH/sec instead of 1.1MH/sec per card), tweaked a bit the B parameters but default one seems to be good, also tried to use dual-worker, but no dice, can't squeeze more from it, need a little more optimisation to be competitive.

keep up the good work  Cool

NEOSCRYPT NEEDS OPTIMIZATION--

I have similar results.  My 1080ti gets about 1.02MH/s with Excavator v1.3.8a, default parameters and default clocks.  With CCminer v2.2.2, default parameters and clocks, it gets about 1.4Mh/s while mining NeoScrypt.  Tweaking the block ("B") parameter did nothing but lessen the hashrate on Excavator.  Mild clock changes did very little to help, also.       --scryptr

Thanks for the feedback. We're still working on optimisations, mainly for the 1080 and 1080 ti cards.
legendary
Activity: 1797
Merit: 1028
Testing out the 1.3.8 release with neoscrypt algo, doesn't perform as well as KlausT or Alexis CCminer, (getting about 900kH/sec instead of 1.1MH/sec per card), tweaked a bit the B parameters but default one seems to be good, also tried to use dual-worker, but no dice, can't squeeze more from it, need a little more optimisation to be competitive.

keep up the good work  Cool

NEOSCRYPT NEEDS OPTIMIZATION--

I have similar results.  My 1080ti gets about 1.02MH/s with Excavator v1.3.8a, default parameters and default clocks.  With CCminer v2.2.2, default parameters and clocks, it gets about 1.4Mh/s while mining NeoScrypt.  Tweaking the block ("B") parameter did nothing but lessen the hashrate on Excavator.  Mild clock changes did very little to help, also.       --scryptr
full member
Activity: 224
Merit: 100
CryptoLearner
Testing out the 1.3.8 release with neoscrypt algo, doesn't perform as well as KlausT or Alexis CCminer, (getting about 900kH/sec instead of 1.1MH/sec per card), tweaked a bit the B parameters but default one seems to be good, also tried to use dual-worker, but no dice, can't squeeze more from it, need a little more optimisation to be competitive.

keep up the good work  Cool
full member
Activity: 224
Merit: 100
CryptoLearner

You should split username and password with ":".

{"id":1,"method":"algorithm.add","params":["algo","pool_address:pool_port","workername:mypass"]}

https://github.com/nicehash/excavator/tree/master/api#-algorithmadd


Ahhhhhhhh, apologies, i didn't saw this, thanks for your help  Cool
jr. member
Activity: 132
Merit: 7
Hello,

How do you put the pool/worker password in the json ?

The following doesn't seems to work.

{"id":1,"method":"algorithm.add","params":["algo","pool_address:pool_port","workername.mypass"]}
{"id":1,"method":"algorithm.add","params":["algo","pool_address:pool_port","workername/mypass"]}
{"id":1,"method":"algorithm.add","params":["algo","pool_address:pool_port","workername","mypass"]}

Could you please give me the right method ?

Thanks.

You should split username and password with ":".

{"id":1,"method":"algorithm.add","params":["algo","pool_address:pool_port","workername:mypass"]}

https://github.com/nicehash/excavator/tree/master/api#-algorithmadd
Pages:
Jump to: