The reject issue with excavator should be fixed now, sgminer did not have this issue.
its somewhat fixed , it works fine for hours , but at some random point all submited shares are getting rejected , only fix is to restart excavator.
Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] - page 67. (Read 179301 times)
February 14, 2017, 02:25:10 AM
its somewhat fixed , it works fine for hours , but at some random point all submited shares are getting rejected , only fix is to restart excavator.
February 14, 2017, 01:26:36 AM
how can i use this to solo mine
what config
what config
February 12, 2017, 08:36:56 AM
The reject issue with excavator should be fixed now, sgminer did not have this issue.
February 12, 2017, 02:41:24 AM
Have a lot of rejects on suprnova...Went to sgminer and nanopool...
February 11, 2017, 07:48:59 AM
We already fixed the issue.
.....
Contact pool operator to fix this issue.
Yes, you are right. At now I mine on nanopool, and all works well. Seems, there is suprnova pool problem. .....
Contact pool operator to fix this issue.
February 10, 2017, 05:51:11 PM
February 10, 2017, 02:05:40 PM
There is indeed a bug regarding shares! Will be fixed in next release.
If anyone can catch the bug (using -f 0 for full file logging), would be greatly appreciated! Thanks!
Something like this:
Code:
[[2017-02-08 02:45:50.878003] [thread=0x000013d8] [debug]]
device#8 | Found nonce: 6c4fedd7 diff=12.4733
[[2017-02-08 02:45:50.878003] [thread=0x000013d8] [debug]]
net | Sending share #1691
[[2017-02-08 02:45:50.878003] [thread=0x000013d8] [trace]]
net | Sending: {"id":1691,"method":"mining.submit","params":["wallet","463","e620202020202020","589a69ab","6c4fedd7"]}
[[2017-02-08 02:45:50.940517] [thread=0x000013a0] [trace]]
net | Received: {"id":1691,"result":null,"error":[23,"low difficulty share of 12.47332076155086"]}
[[2017-02-08 02:45:50.940517] [thread=0x000013a0] [info]]
net | Share #1691 rejected
reason: low difficulty share of 12.47332076155086
We already fixed the issue.
The issue you are reporting here is due to malfunctioning pool. Clearly from the logs, you can see that
Code:
net | New job '463', diff=11.315
So, the job in question (with id '463') has diff of 11.315, but later, we can find out that pool rejected share of this job that had diff 13+:
Code:
[[2017-02-08 02:45:17.124847] [thread=0x00000840] [debug]]
device#10 | Found nonce: 7e0b38db diff=13.4074
[[2017-02-08 02:45:17.124847] [thread=0x00000840] [debug]]
net | Sending share #1685
[[2017-02-08 02:45:17.124847] [thread=0x00000840] [trace]]
net | Sending: {"id":1685,"method":"mining.submit","params":["wallet","463","b820202020202020","589a69ab","7e0b38db"]}
[[2017-02-08 02:45:17.171735] [thread=0x000013a0] [trace]]
net | Received: {"id":1685,"result":null,"error":[23,"low difficulty share of 13.407363099810183"]}
[[2017-02-08 02:45:17.171735] [thread=0x000013a0] [info]]
net | Share #1685 rejected
reason: low difficulty share of 13.407363099810183
Contact pool operator to fix this issue.
February 09, 2017, 10:38:53 AM
Write the correct .bat for suprnova and gtx 1070 pls .
excavator.exe -a pascal -s stratum+tcp://pasc.suprnova.cc:5279 -u Weblogin.Worker -p WorkerPassword -ca -d 2
this work, i haven't tried with the -u WorkerPassword.Worker that i use traditionally on suprnova, i just followed their example for sg-miner
then you have to fill of course the account part with the payload & exchange address, there is an example how to do it directly on the account page.
Cheers.
February 09, 2017, 10:13:38 AM
Write the correct .bat for suprnova and gtx 1070 pls .
February 09, 2017, 09:55:09 AM
.
February 09, 2017, 05:34:55 AM
Pretty nice job guys, the miner work flawlessly. 
February 09, 2017, 01:04:27 AM
i found here for information from yesterday I was thinking to mine pascalcoin and using NVidia, I'll try to test my hashrate
February 08, 2017, 11:42:16 PM
Doesn#t work anymore on suprnova or nanopool.
It started and then GPU load drops to 0..thats it.
It started and then GPU load drops to 0..thats it.
What's your bat looks like please?
February 07, 2017, 08:25:38 PM
There is indeed a bug regarding shares! Will be fixed in next release.
If anyone can catch the bug (using -f 0 for full file logging), would be greatly appreciated! Thanks!
Something like this:
Code:
[[2017-02-08 02:45:50.878003] [thread=0x000013d8] [debug]]
device#8 | Found nonce: 6c4fedd7 diff=12.4733
[[2017-02-08 02:45:50.878003] [thread=0x000013d8] [debug]]
net | Sending share #1691
[[2017-02-08 02:45:50.878003] [thread=0x000013d8] [trace]]
net | Sending: {"id":1691,"method":"mining.submit","params":["wallet","463","e620202020202020","589a69ab","6c4fedd7"]}
[[2017-02-08 02:45:50.940517] [thread=0x000013a0] [trace]]
net | Received: {"id":1691,"result":null,"error":[23,"low difficulty share of 12.47332076155086"]}
[[2017-02-08 02:45:50.940517] [thread=0x000013a0] [info]]
net | Share #1691 rejected
reason: low difficulty share of 12.47332076155086
February 07, 2017, 06:03:39 AM
February 07, 2017, 06:02:52 AM
Can it do solo mining ?
February 06, 2017, 07:22:49 PM
The algorithm is basically SHA256 thus GPU can be fully utilized with no waiting for memory (such as with equihash). There is trully 100% extreme load. If you want lower heat, limit your TDP or play with -ct and -cb parameters. You cannot compare pascal algorithm to equihash, pascal is more similar to blake algorithms (such as decred).
February 06, 2017, 06:22:03 PM
Here it is, this issue should be fixed + few percent more speed: https://www.nicehash.com/tools/excavator_v1.0.0b_Win64.zip
Is the extra heat output something that will be worked on later? I am assuming the fixed issue is the shares problem
February 06, 2017, 04:59:31 PM
Device 0: Hasher interrupted.
This error is normal?
This error is normal?
This is not an error but rather information that CUDA feeding loop has been interrupted (but will be be restarted back on of course).
Ok so it is ok even though it is repeating all the time?
Yes, if you don't use debug printing, it is not visible.
February 06, 2017, 04:12:07 PM
Device 0: Hasher interrupted.
This error is normal?
This error is normal?
This is not an error but rather information that CUDA feeding loop has been interrupted (but will be be restarted back on of course).
Ok so it is ok even though it is repeating all the time?
Jump to: