excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a]

[Burgie002]

Anyone

I am trying to implement the "device.list" command in my config file but failing.
I have already read the Readme and Master documents. It is not clear to me how this command is implemented.

I added the following to my config file and caused the system to freeze.

{"id":1,"method":"device.list","params":[]}


I am currently mining ZEC on Excavator. I have 5x GTX1080TI GPUS on my rig. It works fine until I add the "device.list" and then it crashes.

Has any of you used this function when running excavator? If yes can you show your config entries related to "device.list" functionality.

I ran the telnet call for the device info. I entered the device results into a text file.
Can anyone show how the "device.list" command works in the config file and where does the results of this command show up?

Best regards


device.list works only via API.  In the configuration file it does not work.
Via Telnet  - only type on keyboard {"id":1,"method":"device.list","params":[]} and press Enter.
With the HTTP  - http://Excavator_IP:Excavator_Port/api?command={"id":1,"method":"algorithm.list","params":[]}
For example:
Linux: wget --quiet -O - http://10.0.0.9:38080/api?command={"id":1,"method":"algorithm.list","params":[]}
Windows: use PowerShell (.Net) or wget for windows or browser

Thank You Kayfolom
I was expecting more from the command. My misunderstanding. I did run the api and did get the detailed device output.

Best regards

[lexkanev]

Anyone

I am trying to implement the "device.list" command in my config file but failing.
I have already read the Readme and Master documents. It is not clear to me how this command is implemented.

I added the following to my config file and caused the system to freeze.

{"id":1,"method":"device.list","params":[]}


I am currently mining ZEC on Excavator. I have 5x GTX1080TI GPUS on my rig. It works fine until I add the "device.list" and then it crashes.

Has any of you used this function when running excavator? If yes can you show your config entries related to "device.list" functionality.

I ran the telnet call for the device info. I entered the device results into a text file.
Can anyone show how the "device.list" command works in the config file and where does the results of this command show up?

Best regards

device.list works only via API.  In the configuration file it does not work.
Via Telnet  - only type on keyboard {"id":1,"method":"device.list","params":[]} and press Enter.
With the HTTP  - http://Excavator_IP:Excavator_Port/api?command={"id":1,"method":"algorithm.list","params":[]}
For example:
Linux: wget --quiet -O - http://10.0.0.9:38080/api?command={"id":1,"method":"algorithm.list","params":[]}
Windows: use PowerShell (.Net) or wget for windows or browser

I see the same HTTP request to api used in standard index.html. But how to get this result in index.html on Ubuntu?

Thnx!

[Kayfolom]

Dear Zawawa, is it planned to add new algorithms to the Excavator?

Good question - now I need ethash algorithm too, but on AMD and Ubuntu 14.04 LTS  
Dear Zawawa, help us!  

EXCAVATOR DOES ETH-HASH (DAGGER-HASHIMOTO)--

You may read on pages 48-50 or so for example configurations.  Excavator dual-mines with no fee.  Detailed configuration docs are on the GitHub site.       --scryptr

I saw 48-50 pages before and config dual-mining for ZEC and XMR. But I didn't know what algorithm is for ETH in Excavator miner. Thnx!

Now I can't config web stats for Excavator on Ubuntu 16.04 LTS. Where can I put the "index.html" file to get stats on web?
I start excavator with -wp and -wi parameters (not local IP bind) and get on web "404 Not Found", but when I do "api?..." to binded IP and port I can get stats in JSON format.

Thnx!

Лeкc, cпpocи вoт тyт https://github.com/nicehash/excavator/issues/60 , caм нe знaю, нa линyкce нe зaпycкaл.
Ask here https://github.com/nicehash/excavator/issues/60, I do not know, I did not run it on Linux.

[lexkanev]

Version 1.3.6 alpha NVIDIA for Linux

* cryptonight bug fixes & improvements

The Linux version of excavator is compatible only with Ubuntu 16.04 LTS and Ubuntu 14.04 LTS, and it requires NVIDIA Display Driver 387 or later. All you need to do for installation on Ubuntu 16.04 LTS is to install a compatible NVIDIA driver and to run:

.............
.............

Sorry for the delay... The new support scripts should be pretty useful, though. Enjoy!

Hi!
I compared performance of versions 1.3.4a and 1.3.6a in Ubuntu 16.04 LTS on Palit p106-100 (GFX 1060 6G).
It's very strange - on Monero (cryptonight algorithm) I have results:

1.3.4a ~ 431-436 H/s,
1.3.6a ~ 460-464 H/s.

In json config I use CUDA-cryptonight parameters: B=30,TPB=32.

PS. ZEC mining looks the same in both versions.

I am not sure if it is my optimization or voidstar's bug fix, but I am glad to hear that anyway!

One another question - how to use miner on AMD GPUs in Ubuntu 14.04 LTS?

Is there solution to start mining with Excavator on AMD GPUs in Ubuntu 14.04 LTS?
I read all pages and didn't found recept to do this.

[FFI2013]

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

[dropky]

Version 1.3.6 alpha NVIDIA for Linux

* cryptonight bug fixes & improvements

The Linux version of excavator is compatible only with Ubuntu 16.04 LTS and Ubuntu 14.04 LTS, and it requires NVIDIA Display Driver 387 or later. All you need to do for installation on Ubuntu 16.04 LTS is to install a compatible NVIDIA driver and to run:

.............
.............

Sorry for the delay... The new support scripts should be pretty useful, though. Enjoy!

Hi!
I compared performance of versions 1.3.4a and 1.3.6a in Ubuntu 16.04 LTS on Palit p106-100 (GFX 1060 6G).
It's very strange - on Monero (cryptonight algorithm) I have results:

1.3.4a ~ 431-436 H/s,
1.3.6a ~ 460-464 H/s.

In json config I use CUDA-cryptonight parameters: B=30,TPB=32.

PS. ZEC mining looks the same in both versions.

I am not sure if it is my optimization or voidstar's bug fix, but I am glad to hear that anyway!

One another question - how to use miner on AMD GPUs in Ubuntu 14.04 LTS?

Is there solution to start mining with Excavator on AMD GPUs in Ubuntu 14.04 LTS?
I read all pages and didn't found recept to do this.

Unfortunately, Excavator doesn't support AMD anymore. Sorry. 

[dropky]

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.

[m1n1ngP4d4w4n]

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.

[dropky]

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

[m1n1ngP4d4w4n]

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 

[m1n1ngP4d4w4n]

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 

[scryptr]

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  

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

[dropky]

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  

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.

[MarcusDe]

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  

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

[DeadMoroz]

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.

[halker2010]

does anyone has crash issues on 1070 ? whenever i open excavator for neoscrypt sometimes even it freezes the system until i restart again.

[Kayfolom]

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

[scryptr]

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

[m1n1ngP4d4w4n]

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

excavator.exe -c yourconfig.json

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

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.

[scryptr]

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