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

Is HW acceleration likely to occur for other AMD cards or just the ones listed? I've got a R9 390 and a couple RX550's

I get the following error when trying to run with 6 x RX480 on Win 10. I have disabled the driver sig. Any help ??

=============================
Running Admin shell
=============================

SUCCESS: Specified value was saved.

SUCCESS: Specified value was saved.

SUCCESS: Specified value was saved.

SUCCESS: Specified value was saved.

SUCCESS: Specified value was saved.

======================= www.nicehash.com =====================
            Excavator v1.2.5a GPU Miner for NiceHash.
       Copyright (C) 2017 NiceHash. All rights reserved.
Developed by djeZo and zawawa with help and contributions from
         pallas, Vorksholk, bitbandi, ocminer, Genoil
======================= www.nicehash.com =====================

Build time: 2017-06-14 00:49:03
Build number: 388
Provided startup commandline:
        ..\excavator  -c ..\default_command_file.json

[23:01:29][0x0000080c][info] Log started
[23:01:29][0x0000080c][info] opencl | Loaded phymem for direct PCIe access.
[23:01:29][0x0000080c][error] OpenCL error 'Out of resources' in func 'openclhelp::init' line 262

[23:24:55][0x000010c8][info] Log started
[23:24:55][0x000010c8][error] opencl | Failed to load AMD Display Library.
[23:24:55][0x000010c8][error] opencl | Failed to initialize AMD Display Library.
[23:24:55][0x000010c8][info] Unable to access PCIe buses. Run miner as administrator instead.
[23:24:55][0x000010c8][error] opencl | Failed to load phymem.
[23:24:55][0x000010c8][error] opencl | Please disable driver signature enforcement and run miner as administrator.
[23:24:55][0x000010c8][info] core | Found CUDA device: GeForce GTX 1070
[23:24:55][0x000010c8][info] http | Listening on 127.0.0.1:38080
[23:24:55][0x000010c8][info] core | Initialized!
[23:24:55][0x0000250c][info] net | Connecting to 37.58.117.214:3356 (lbry.eu.nicehash.com)
[23:24:55][0x0000250c][info] net | Connecting to 37.58.117.214:3353 (daggerhashimoto.eu.nicehash.com)
[23:24:55][0x0000250c][info] net | Connected!
[23:24:55][0x0000250c][info] net | Connected!
[23:24:55][0x0000250c][info] net | Authorized as 16JXzYjdDcAojgkADGwtqM8UdKBkPXrZSn.test2
[23:24:55][0x00000334][info] algo-daggerhashimoto | New job '00000008504fbedc', diff=1
[23:24:56][0x00000334][info] net | Authorized as 16JXzYjdDcAojgkADGwtqM8UdKBkPXrZSn.test1
[23:24:56][0x00000334][info] algo-lbry | New job '0000000913b5e0e5', diff=128
[23:24:58][0x00000334][info] algo-lbry | New job '0000000913b5edaa', diff=128
[23:24:59][0x00000fe4][fatal] wrkr0-1 | bad function call
[23:24:58][0x0000284c][info] wrkr0-0 | Algorithm: CUDA-lbry parameters: B=116340,TPB=768,NPT=4
[23:24:59][0x000010c8][info] Shutting down
[23:24:59][0x000010c8][info] http | Closing

I get bad function call only on daggerhashimoto. Please help.
my config:
[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["lbry","lbry.eu.nicehash.com:3356","16JXzYjdDcAojgkADGwtqM8UdKBkPXrZSn.test1"]},
      {"id":1,"method":"algorithm.add","params":["daggerhashimoto","daggerhashimoto.eu.nicehash.com:3353","16JXzYjdDcAojgkADGwtqM8UdKBkPXrZSn.test2"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["1","0"]}
   ]},
   {"time":10,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":1,"method":"worker.print.speed","params":["1"]},
      {"id":1,"method":"algorithm.print.speeds","params":["0"]}
   ]}
]

I'm still not 100% clear how to mine with multiple GPUs. Is this correct for a 4 GPU rig?

[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["lbry","lbry.suprnova.cc:6256","account.worker"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["0","1"]},
      {"id":1,"method":"worker.add","params":["0","2"]},
      {"id":1,"method":"worker.add","params":["0","3"]}
   ]},
   {"time":10,"loop":10,"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":"algorithm.print.speeds","params":["0"]}
   ]}
]

Why is there 2 identical lines in the default .json file?
{"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["0","0"]}
   ]},

Does this mean that the miner will use 2 threads per each GPU? Is it faster (higher hashrate) than 1 thread per GPU? The miner keeps crashing for me after 10-30 seconds of running and the window disappears too quickly so I can't even see the crash reason (I think it's "cuda error something"). Sorry for noobish questions, it's just most mining software out there has simple readme files explaining each parameter in detail, and this one has too many things that aren't obvious (like all those "id:1" things in the .json, it's probably all perfectly clear to those familiar with json files, but for those of us that aren't... well, the whole syntax is a bit confusing).

By the way, regarding those rejected "low difficulty" shares on suprnova — there's now a note on top of the page, saying "Nicehash: lbry.suprnova.cc:6257". Kinda cryptic, does it mean that if I'm using excavator with suprnova lbry pool, I'm supposed to connect to 6257 port, instead of 6256? Or is for nicehash users only?

Can anyone report any kind of issues with lbry on NVIDIA? You should be getting around 400 MHs on 1080 and 300 MHs on 1070.

Can anyone report any kind of issues with lbry on NVIDIA? You should be getting around 400 MHs on 1080 and 300 MHs on 1070.

Do you have an ETA for the Linux version?

[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["daggerhashimoto","daggerhashimoto.eu.nicehash.com:3353","YOURBTCADRESS"]},
      {"id":1,"method":"algorithm.add","params":["sia","sia.eu.nicehash.com:3360","YOURBTCADRESS"]}
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
      {"id":1,"method":"worker.add","params":["1","0"]}
   ]},
   {"time":5,"loop":10,"commands":[
      {"id":1,"method":"worker.print.speed","params":["0"]},
      {"id":1,"method":"worker.print.speed","params":["1"]},
      {"id":1,"method":"algorithm.print.speeds","params":["0"]}
   ]}
]

[
   {"time":0,"commands":[
      {"id":1,"method":"algorithm.add","params":["daggerhashimoto","daggerhashimoto.eu.nicehash.com:3353","YOURBTCADRESS"]},
   ]},
   {"time":3,"commands":[
      {"id":1,"method":"worker.add","params":["0","0"]},
                {"id":1,"method":"worker.add","params":["0","1"]},
                {"id":1,"method":"worker.add","params":["0","2"]},
                {"id":1,"method":"worker.add","params":["0","3"]},
                {"id":1,"method":"worker.add","params":["0","4"]}
   ]},
   {"time":10,"loop":10,"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":"algorithm.print.speeds","params":["0"]}
   ]}
]

It is, here: https://github.com/nicehash/excavator/tree/master/api#algorithm-add

And there is also example json file in root folder where you only need to modify data with your own.

How do I select which cards are used for mining? By default only the 1st card in the rig is used and the others are idling. Is it the "-cd" parameter in the main .bat file? I can't find anything about this in the documentation.
And I'm also getting lots of rejected shares when mining lbry on suprnova. The reason is always "low difficulty share". I don't have nearly as many (pretty much none at all) on the same rig with the same pool when I'm using alexis ccminer.

Using start-up commanding file. See example default_command_file.json.

File contains a JSON array of all actions that would happen during runtime of Excavator. Each array item has two mandatory fields and one optional. Mandatory is 'time' which tells you after how many seconds since start of Excavator commands should execute and 'commands' which is a JSON array of commands you can find in API section.

Optionally you can specify 'loop' which repeat commands every 'loop' seconds. When creating algorithms and workers, note that IDs of returned objects always run from 0 and on, so first algorithm always has ID 0, second 1 etc.

You will want to figure out ID of each card; use telnet to connect to Excavator then send command

{"id":1,"method":"device.list","params":[]}
to retreive all available devices and their IDs.

After you have your commanding file ready, use '-c' command line switch to provide file name when starting Excavator.