EWBF's Cuda Equihash Miner 0.6

[sahouri100]

EWBF Cuda Equihash Miner v0.6

Greetings!
It is based on my last Zcash miner and almost completely repeats it.
Now closer to the topic:
*  Parameter "solver" is disabled.
*  Solver for equihash 200,9 has been deleted.
*  Solvers for Equihash 192,7, 144,5, 96,5 and 210,9 has been added
*  Added timestamps in the output to the screen and to the log file.
*  Argument --algo is added, allow you to select Equihash variant allowed values 144_5, 192_7, 96_5, 210_9, zhash, aion. This parameter is mandatory.
*  Argument --pers is added, allow you to set personalization string (8 charachters) for equihash algorithm. This parameter is optional. Equihash by default uses the string "ZcashPoW", many other coins also use this string, but not all, some coins use their own string, and these are all differences, so for some coins, you need to set the --pers option to the required string, for example, Zero coin: https://bitcointalk.org/index.php?topic=3310714  uses the string "ZERO_PoW" and for mining this coin you need to pass arguments --algo 192_7 --pers ZERO_PoW ....
Fee is presented and by default 2%, argument --fee is presented too.

v0.6
* Fixed situation where the api socket did not close during the exit..
* Increased time-outs during stratum authorization and subscription.
* 144_5, 192_7, 96_5 now faster.
* 144_5 now uses less vram, ~1.63GB (This should be useful for 2GB cards).

v0.5
* 96_5 fixed the problem with cropped performance on fast (1080ti, Titan) gpu.
* 144_5 Speed up by 3-15% depends on the hardware.
* 210_9 Speed up by 2%.
* 210_9 Fixed "low difficulty shares" problem, on Aion pools.
* 210_9 can now be used via --algo 210_9, I recommend using --algo aion for Aion mining, this will help you avoid problems with the wrong personalization string.
* Added option --intensity, this option will not increase performance, only slightly reduce the gpu usage, if you set it to 1. Works like --cuda_devices argument,
   for example: --intensity 64 64 1 64 64 will apply the intensity 1 to the device with id 2.
 Special features (These features are added for specific projects,do not use these parameters on conventional pools):
* Added option --pers auto, Allow the pool to manage the personalization string. (Profit switching). (http://zergpool.com)
* Added option --algo 144_5_EXCC_D For ExchangeCoin.

Known issues (mostly will be fixed)
*  Equihash 96_5 Can be slower in cuda 8 versions.
*  Performance counters may display an incorrect speed during reconnection.

Expected performance:

96_5 uses ~1.6GB vram
 1050ti   ~7.8 KS/s  
 1060    ~14 KS/s
 1070    ~20 KS/s
 1080    ~25 KS/s
 1080ti    ~37 KS/s

192_7 uses ~2.5GB vram
 1050ti    ~8 S/s
 1060    ~15 S/s
 1070    ~22 S/s
 1080    ~24 S/s
 1080ti    ~35 S/s

144_5 uses ~1.63GB vram
 1050ti   ~18 S/s  
 1060    ~30 S/s
 1070    ~45 S/s
 1080    ~50 S/s
 1080ti    ~75 S/s

210_9(aion) uses 1.2G vram
 1050ti   ~75 S/s
 1060    ~130 S/s
 1070    ~190 S/s
 1080    ~210 S/s
 1080ti  ~320 S/s

Please note, that this is initial release, and it can be baggy or incompatible with many coins or pools.
Miner compiled with cuda 9.1 and cuda 8.0 for x64 linux and windows. Support devices with compute capability 5.0 and higher.

Windiws    https://mega.nz/#F!fsAlmZQS!CwVgFfBDduQI-CbwVkUEpQ
Linux        https://mega.nz/#F!3xYlSJDK!kG4kVLg1arbBuq1dd8u9aA

Linux        https://drive.google.com/open?id=1jUhXYysli_x6MH_wQ9lY07c68Ze7WM8g
Windiws   https://drive.google.com/open?id=1anfDRDVc_Fs_NceuZNuDK8HWZgcCdM3A

Usage examples (batch files):
Basic Example:

Code:

miner --algo 144_5 --server SERVER_ADDR --port PORT --user USER --pass PASSWORD

Failover pools up to 8 pools:

Code:

miner --algo 144_5 --server SERV1 --port PORT1 --user USER1 --pass PASS1 --server SERV2 --port PORT2 --user USER2 --pass PASS2

[1550466925]

1550466925

[1550466925]

1550466925

[1550466925]

1550466925

[1550466925]

1550466925

[1550466925]

1550466925

[endemion]

Greetings! I try to mined the EXCC coin.
Write the bat file like this

:restart
@echo  off
TIMEOUT 5
miner --algo --algo 144_5_EXCC_D --pers EXCHANGE --server excc.scecf.org --user --------.MSIONE --pass x --port 7088 --api 127.0.0.1:4200
goto start

But when the miner started it write me wrong jobe! What i do wrong? Or EWBF dont support this coin?

Thanks

[umine]

Greetings! I try to mined the EXCC coin.
Write the bat file like this

:restart
@echo  off
TIMEOUT 5
miner --algo --algo 144_5_EXCC_D --pers EXCHANGE --server excc.scecf.org --user --------.MSIONE --pass x --port 7088 --api 127.0.0.1:4200
goto start

But when the miner started it write me wrong jobe! What i do wrong? Or EWBF dont support this coin?

Thanks

check carefully your string:

Code:

miner --algo --algo 144_5_EXCC_D --pers EXCHANGE --server excc.scecf.org --user --------.MSIONE --pass x --port 7088 --api 127.0.0.1:4200

two times of

Code:

--algo

is unnecessary

[endemion]

Sorry it my mistake here. In bat file i don`t have this mistake. But if i change this options. it`s no help nothing same problem in miner. (received incorrect work) I suppose dev of miner can answer here, support this algo or no anymore? (maybe have plans to added again)

http://prntscr.com/m204w8

[Coin++]

Sorry it my mistake here. In bat file i don`t have this mistake. But if i change this options. it`s no help nothing same problem in miner. (received incorrect work) I suppose dev of miner can answer here, support this algo or no anymore? (maybe have plans to added again)

http://prntscr.com/m204w8

To know what algo are supported, make a miner -help command.

[umine]

Sorry it my mistake here. In bat file i don`t have this mistake. But if i change this options. it`s no help nothing same problem in miner. (received incorrect work) I suppose dev of miner can answer here, support this algo or no anymore? (maybe have plans to added again)

http://prntscr.com/m204w8

Seems EXCC use another hashing algo that doesn't support by EWBF-miner. You should ask EXCC developers about it. Even at EXCC pools there is no configuration for EWBF miner. They use another mining software

[1MORLAP]

Wehn Beam support arrives? 150,5?

[carel]

Miner development stopped?
interested in the possibility of mining at 1063 algo beam, grin ...

thank

[jjxaker]

Win10 x64 RS5(10.0.17763.292) miner does not work. please, add Nvidia DCH driver support.

[ninjam]

dev is enjoying on his own private island 

[prominertools]

EWBF miner has been added to the PMT archive:

https://prominertools.com/ewbf/

[TeamCyr]

Hello everyone!

None of my PNY or EVGA 1070 cards can go over 41.6 sols/s.  Would someone kindly give me the best MSI afterburner settings to achieve 45 as suggested by the OP?

my settings:
power 72
Temp 72
Core 144
Memory Clock 594


Getting 41.6 sol/s avg from 6 cards

THANK YOU!

[umine]

Hello everyone!

None of my PNY or EVGA 1070 cards can go over 41.6 sols/s.  Would someone kindly give me the best MSI afterburner settings to achieve 45 as suggested by the OP?

my settings:
power 72
Temp 72
Core 144
Memory Clock 594


Getting 41.6 sol/s avg from 6 cards

THANK YOU!

Each GPU is individual. So there is no universal best settings for all cards.
I use the following steps when install and setup GPU:
1. Choose desired power consumption
2. Choose maximum stable OC settings by step by step increasing of overclocking (memory or core depends on the algo)

[Junkey]

I have had a rig running 0.5 for nearly a year with no problems 5x MSI Gaming X 1070 on Windows 10.  One of the cards died and I did an RMA.  They sent me a Gaming Z 1070.  When I put that card back in I now get this error for every card.

 09:50:20 CUDA: Device: 0 GeForce GTX 1070, 8192 MB i:64
09:50:20 CUDA: Device: 1 GeForce GTX 1070, 8192 MB i:64
09:50:20 CUDA: Device: 2 GeForce GTX 1070, 8192 MB i:64
09:50:20 CUDA: Device: 3 GeForce GTX 1070, 8192 MB i:64
09:50:20 CUDA: Device: 4 GeForce GTX 1070, 8192 MB i:64
09:50:22 CUDA: Device: 4 Thread exited with message: "an illegal memory access was encountered"
09:50:22 CUDA: Device: 2 Thread exited with message: "an illegal memory access was encountered"
09:50:22 CUDA: Device: 1 Thread exited with message: "an illegal memory access was encountered"
09:50:22 CUDA: Device: 3 Thread exited with message: "an illegal memory access was encountered"
09:50:22 CUDA: Device: 0 Thread exited with message: "an illegal memory access was encountered"

And a popup for windows 10 says this.

"Application has been blocked from accessing graphics hardware."

I then upgraded to 0.6, nothing changed.  I googled some and figured since the RMA card I got back was different I then should just set every GPU back to stock using MSI afterburner.  That didn't fix it either.  MSI afterburner says driver version 388.13.  I then used windows to update the drivers to 399.24 and that didn't fix it either.  Next I used DDU to remove all drivers and start from scratch and that didn't fix it.  Ugg.


I have ran out of options.  Any ideas?  Thanks,

[erich8]

Hello people. I'm testing mining at Lubuntu 64bit.
I'm at miningpoolhub.
I'm in trouble.
I downloaded EWBF_Equihash_miner_v0.6.tar.gz
he gives this error;
./miner: error loading shared libraries: libnvidia-ml.so.1 can not open shared object file: no file or directory
my pc does not have nvidia card, i want to test mining in pc's CPU.
using this code;
miner --server us-east.equihash-hub.miningpoolhub.com --user username.workername --passar password --port 20595 --algo 144_5 --pers BgoldPoW
that's right?
Please help me.