Topic: EWBF's Cuda Equihash Miner 0.6 - page 24. (Read 85776 times)
How many sol/s on 144_5 algorithm can I squeeze with 1060 in overclocking?
@EWBF_
Next version, Do you have for cuda 9.2 ?
Next version, Do you have for cuda 9.2 ?
Hello back here giving g a quick feedback :
0.3 and 0.4 works like a charm now using 144_5 algorithm doesn't matter which coin
Super stable I get 123 sols in 3 gtx1080 each one has different core clock, evga SC +130 core, Gigabyte gaming g1 +140 core and asus strix +150 core all three
running @650 memory. Not rejected shares at all.
Now with 0.4 I switch to different coin/algorithm 192_7
I got a couple rejected shares around 10 on the first day , now this algo won't accept the clocks I was using,
Same clocks will cause to exit threat and just give continuously errors.
I lower clocks to +100 core and memory to 550 in all cards, second day works with out error, rejected shares still keep increasing are now @26
I get solid 21 sols per gxt1080
I'm using windows 10 profesional
I5 6400
16gb ddr4
500gb ssd
Asus motherboard
"""Sorry if I misspell something, I mainly speak Spanish"""
0.3 and 0.4 works like a charm now using 144_5 algorithm doesn't matter which coin
Super stable I get 123 sols in 3 gtx1080 each one has different core clock, evga SC +130 core, Gigabyte gaming g1 +140 core and asus strix +150 core all three
running @650 memory. Not rejected shares at all.
Now with 0.4 I switch to different coin/algorithm 192_7
I got a couple rejected shares around 10 on the first day , now this algo won't accept the clocks I was using,
Same clocks will cause to exit threat and just give continuously errors.
I lower clocks to +100 core and memory to 550 in all cards, second day works with out error, rejected shares still keep increasing are now @26
I get solid 21 sols per gxt1080
I'm using windows 10 profesional
I5 6400
16gb ddr4
500gb ssd
Asus motherboard
"""Sorry if I misspell something, I mainly speak Spanish"""
I'm also having the various "illegal memory, cuda devices busy, gpu restarting" errors everyone else is reporting with 0.4. Occasionally would get them with 0.3 as well but after 4-5 days. Now with 0.4 its guaranteed to happen within about a 26-27 hour period. Had the misfortune of not catching this on one rig for hours and losing precious uptime because of it. Luckily no GPU's were harmed.
This is the new solvers, and I change them, in search of a way to make them better. So yes, every new version can be more or less stable, sorry for it guys. I continue this work until a satisfactory result is achieved.
On the intensity, it does not work right now, due to many solvers it will be completely changed and applied in the next version.
For everyone: I read this topic and see the errors that you posting here, so thanks for that, it really helps.
I'm also having the various "illegal memory, cuda devices busy, gpu restarting" errors everyone else is reporting with 0.4. Occasionally would get them with 0.3 as well but after 4-5 days. Now with 0.4 its guaranteed to happen within about a 26-27 hour period. Had the misfortune of not catching this on one rig for hours and losing precious uptime because of it. Luckily no GPU's were harmed.
I use --intensity 20 but it doesnot have effectively . Sol is same i:20 = i:64
Can you fix it ?
Can you fix it ?
EWBF Cuda Equihash Miner v0.4
Greetings!
This is the initial release of a new miner for Equihash algorithm.
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, 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://bitcointalksearch.org/topic/annzerzero-your-transactions-are-your-business-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.4
* Added new solver for Equihash 210,9. Available only with --algo aion (this solver is in beta status)
* Failover pools can now be specified via command-line arguments, just repeat the credentials set, but do not shuffle them (see Example below)
* Improved performance for algo 144_5 and maxwell gpus
* Fixed launching of devices
v0.3
* Added new solver for Equihash 96,5 --algo 96_5.
* Added --color argument, allow you to disable colored console: --color 0.
* 192_7 and 144_5 solvers 0 - 10% faster, depends on the gpu.
* 192_7 require now 2.5GB vram, it should fit in 3Gb gpu under win 10.
* 144_5 require now 1.99Gb of vram.
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.
Greetings!
This is the initial release of a new miner for Equihash algorithm.
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, 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://bitcointalksearch.org/topic/annzerzero-your-transactions-are-your-business-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.4
* Added new solver for Equihash 210,9. Available only with --algo aion (this solver is in beta status)
* Failover pools can now be specified via command-line arguments, just repeat the credentials set, but do not shuffle them (see Example below)
* Improved performance for algo 144_5 and maxwell gpus
* Fixed launching of devices
v0.3
* Added new solver for Equihash 96,5 --algo 96_5.
* Added --color argument, allow you to disable colored console: --color 0.
* 192_7 and 144_5 solvers 0 - 10% faster, depends on the gpu.
* 192_7 require now 2.5GB vram, it should fit in 3Gb gpu under win 10.
* 144_5 require now 1.99Gb of vram.
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.
Equihash Miner 0.4 is fast about 10% but very unstable, need catch all bugz.
I agree. I back to 0.3 again.
Equihash Miner 0.4 is fast about 10% but very unstable, need catch all bugz.
I cannot use This SW. Im getting always that error of cuda devices busy.
Hello, since version 0.4 I'm having problems with stability.
After this message autorestarting loops until manual restart.
I'm using same OC settings as with v0.3 which were rock solid (up to 16 days of continous mining)
ATM I lowered OC a bit and testing if problem still occurs.
Code:
18.07.2018 09:57:52 Temp: GPU0 54C GPU1 55C
18.07.2018 09:57:52 GPU0: 48 Sol/s GPU1: 27 Sol/s
18.07.2018 09:57:52 Total speed: 75 Sol/s
18.07.2018 09:57:57 CUDA: Device: 1 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 CUDA: Device: 0 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 WARNING: Looks like GPU0 are stopped. Restarting...
18.07.2018 09:57:57 INFO: GPU0 are restarted.
18.07.2018 09:57:58 WARNING: Looks like GPU1 are stopped. Restarting...
18.07.2018 09:57:58 INFO: GPU1 are restarted.
18.07.2018 09:57:58 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:58 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:59 WARNING: Looks like GPU0 are stopped. Restarting...
After this message autorestarting loops until manual restart.
I'm using same OC settings as with v0.3 which were rock solid (up to 16 days of continous mining)
ATM I lowered OC a bit and testing if problem still occurs.
I have this problem, with 0.3 work full time, 0.4 same OC and have problems.
Have same problem wtih version 0.4. I didint have that problem with 0.3 with same OC. after a while, a problem appeared...
Running on SimpleMining OS with 0.4
20:17:02 GPU0: 171 Sol/s GPU1: 172 Sol/s GPU2: 163 Sol/s GPU3: 101 Sol/s GPU4: 103 Sol/s
20:17:02 Total speed: 710 Sol/s
firt 3 ar 1080ti and 2 1060 6 GB
20:17:02 GPU0: 171 Sol/s GPU1: 172 Sol/s GPU2: 163 Sol/s GPU3: 101 Sol/s GPU4: 103 Sol/s
20:17:02 Total speed: 710 Sol/s
firt 3 ar 1080ti and 2 1060 6 GB
Do you have 100 sols with 1060? wtf i have 24, and 40 with 1070ti
I saw this also. My bet is he is NOT running 144,5. Probably 210,9.
Hello, since version 0.4 I'm having problems with stability.
After this message autorestarting loops until manual restart.
I'm using same OC settings as with v0.3 which were rock solid (up to 16 days of continous mining)
ATM I lowered OC a bit and testing if problem still occurs.
Code:
18.07.2018 09:57:52 Temp: GPU0 54C GPU1 55C
18.07.2018 09:57:52 GPU0: 48 Sol/s GPU1: 27 Sol/s
18.07.2018 09:57:52 Total speed: 75 Sol/s
18.07.2018 09:57:57 CUDA: Device: 1 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 CUDA: Device: 0 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 WARNING: Looks like GPU0 are stopped. Restarting...
18.07.2018 09:57:57 INFO: GPU0 are restarted.
18.07.2018 09:57:58 WARNING: Looks like GPU1 are stopped. Restarting...
18.07.2018 09:57:58 INFO: GPU1 are restarted.
18.07.2018 09:57:58 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:58 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:59 WARNING: Looks like GPU0 are stopped. Restarting...
After this message autorestarting loops until manual restart.
I'm using same OC settings as with v0.3 which were rock solid (up to 16 days of continous mining)
ATM I lowered OC a bit and testing if problem still occurs.
I have this problem, with 0.3 work full time, 0.4 same OC and have problems.
Running on SimpleMining OS with 0.4
20:17:02 GPU0: 171 Sol/s GPU1: 172 Sol/s GPU2: 163 Sol/s GPU3: 101 Sol/s GPU4: 103 Sol/s
20:17:02 Total speed: 710 Sol/s
firt 3 ar 1080ti and 2 1060 6 GB
20:17:02 GPU0: 171 Sol/s GPU1: 172 Sol/s GPU2: 163 Sol/s GPU3: 101 Sol/s GPU4: 103 Sol/s
20:17:02 Total speed: 710 Sol/s
firt 3 ar 1080ti and 2 1060 6 GB
Do you have 100 sols with 1060? wtf i have 24, and 40 with 1070ti
Hi, im getting this ERROR: cannot send request to server, and then ERROR: no connection with the pool, restoring
and then it keeps reppeating.. trying to mine BTG on miningpoolhub (i actually tried other pools, got same error), it was working normally a couple days ago.. actually that problem happened but sudenly it begun to work normally again.. but this time its stuck, cant figure it out.. tried the previous miner version (0.2, 0.3), tried without antivirus.. nothing.. im running it on windows 10.. any ideas?
and then it keeps reppeating.. trying to mine BTG on miningpoolhub (i actually tried other pools, got same error), it was working normally a couple days ago.. actually that problem happened but sudenly it begun to work normally again.. but this time its stuck, cant figure it out.. tried the previous miner version (0.2, 0.3), tried without antivirus.. nothing.. im running it on windows 10.. any ideas?
Try this with EWBF V.4.0 and if it works change your worker and pool
miner --algo 144_5 --pers BgoldPoW --server btg.suprnova.cc --port 8866 --user Josemagi.JoseHush --pass x
Running on SimpleMining OS with 0.4
20:17:02 GPU0: 171 Sol/s GPU1: 172 Sol/s GPU2: 163 Sol/s GPU3: 101 Sol/s GPU4: 103 Sol/s
20:17:02 Total speed: 710 Sol/s
firt 3 ar 1080ti and 2 1060 6 GB
20:17:02 GPU0: 171 Sol/s GPU1: 172 Sol/s GPU2: 163 Sol/s GPU3: 101 Sol/s GPU4: 103 Sol/s
20:17:02 Total speed: 710 Sol/s
firt 3 ar 1080ti and 2 1060 6 GB
Released NPlusMiner 4.3
https://github.com/MrPlusGH/NPlusMiner/releases
https://github.com/MrPlusGH/NPlusMiner/releases/tag/4.3
NPlusMiner now with a GUI and AutoUpdate
Candidate for AutoUpdate = Yes
- NPlusMiner checks for updates every 24 hours.
- If you do not want to wait, simply restart NPlusMiner and it will pick it up on startup
- More responsive UI
- Fixed wrong GPU selection while using ManualConfig
- Fixed Pause/Mine function
- Added CPU affinity for CPU miner
- Changed Stratum to Host in Switching.log
- Upgraded EWBFv2 to version 0.4
- Changed AutoUpdate function so we keep only the two last backups to avoid filling disk
https://github.com/MrPlusGH/NPlusMiner/releases
https://github.com/MrPlusGH/NPlusMiner/releases/tag/4.3
NPlusMiner now with a GUI and AutoUpdate
Candidate for AutoUpdate = Yes
- NPlusMiner checks for updates every 24 hours.
- If you do not want to wait, simply restart NPlusMiner and it will pick it up on startup
- More responsive UI
- Fixed wrong GPU selection while using ManualConfig
- Fixed Pause/Mine function
- Added CPU affinity for CPU miner
- Changed Stratum to Host in Switching.log
- Upgraded EWBFv2 to version 0.4
- Changed AutoUpdate function so we keep only the two last backups to avoid filling disk
How do you set the intensity?
yes it is true, but this is only a little description not a holy grail.
Lot of people cant start mining, becuse they have lot of error, and dont understund why all share reject etc ...
I hope this mini howto help them.
sry for my terrible english
Lot of people cant start mining, becuse they have lot of error, and dont understund why all share reject etc ...
I hope this mini howto help them.
sry for my terrible english
Little help for aion mine
lot of pool need aion wallet starting with 0xa
Your binance wallet starting 0x
lot of pool need aion wallet starting with 0xa
Your binance wallet starting 0x
FYI Binance does not list the native Aion coin (Aion-1), they have the Aion ERC20 Token. You will not be able to send your mined Aion-1 coins to Binance. You'll likely need await for Aion Bridge release to do token swaps unless Binance adds another Aion-1 market in the interim.
I'd also recommend NOT exporting your privatekey from the encrypted keystore file, just backup the keystore file; no need to expose raw privatekeys unless you're very secure about doing so.
Little help for aion mine
lot of pool need aion wallet starting with 0xa
Your binance wallet starting 0x
This is the first step, you can google easy how can make aion wallet.
Manual: https://github.com/aionnetwork/aion/wiki/Aion-Owner%27s-Manual
Use your vps, download the latest release: https://github.com/aionnetwork/aion/releases
after start it use screen, after detach
if you have memory problem add 10GB more swap to your system and no problem. ( http://bfy.tw/J5fv )
attach screen:
create address
ask the passphrase, dont forget, after show your address, cut n paste
List address:
Export:
now you can save the private key ( cut n paste and save your safest place, maybe your mind
)
Now you have, address, private key, running aion core, you can start mining.
i prefer this pool : https://pool.whibbit.cn/connect?coin=AION , because nice stats
but you can use any pool as you like.
I used simpleminingos, i change the 0.3 version to 0.4 it is easy ( i have no time to wait the updates )
OC settings
After you start mining, you can connect the aion gui.
lot of pool need aion wallet starting with 0xa
Your binance wallet starting 0x
This is the first step, you can google easy how can make aion wallet.
Manual: https://github.com/aionnetwork/aion/wiki/Aion-Owner%27s-Manual
Use your vps, download the latest release: https://github.com/aionnetwork/aion/releases
after start it use screen, after detach
if you have memory problem add 10GB more swap to your system and no problem. ( http://bfy.tw/J5fv )
Code:
screen -S aion
./aion.sh
CTRL + A and D
attach screen:
Code:
screen -x aion
create address
Code:
./aion.sh -a create
ask the passphrase, dont forget, after show your address, cut n paste
List address:
Code:
./aion.sh -a list
Export:
Code:
./aion.sh -a export 0xa...youraddresswhatyoulistedbefore...
now you can save the private key ( cut n paste and save your safest place, maybe your mind
)Now you have, address, private key, running aion core, you can start mining.
i prefer this pool : https://pool.whibbit.cn/connect?coin=AION , because nice stats
but you can use any pool as you like.
I used simpleminingos, i change the 0.3 version to 0.4 it is easy ( i have no time to wait the updates )
Code:
--algo aion --server cn-mining.whibbit.cn --port 30001 --user 0xa04d3075761b860d5fe344d069cb867720cf9fd225cc34c3f2e57e5a0ad82beb.$rigName
OC settings
Code:
1060 3 GB : core 1961 / memory 4050, core max 120-160 / memory 400-500, power 96W results : 128 - 131 Sol / card
1080 ti: core 1847 / memory 5500, core max (depend your 1080 ti card) / memory 600-800, power max 100% 250 W results 320 Sol / card
if you use lower power --> lower electricity bill ,but lower hashrate. if power 0.78% TDP 195W results: 275 Sol / card
After you start mining, you can connect the aion gui.
Hello, since version 0.4 I'm having problems with stability.
After this message autorestarting loops until manual restart.
I'm using same OC settings as with v0.3 which were rock solid (up to 16 days of continous mining)
ATM I lowered OC a bit and testing if problem still occurs.
Code:
18.07.2018 09:57:52 Temp: GPU0 54C GPU1 55C
18.07.2018 09:57:52 GPU0: 48 Sol/s GPU1: 27 Sol/s
18.07.2018 09:57:52 Total speed: 75 Sol/s
18.07.2018 09:57:57 CUDA: Device: 1 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 CUDA: Device: 0 Thread exited with message: "an illegal memory access was encountered"
18.07.2018 09:57:57 WARNING: Looks like GPU0 are stopped. Restarting...
18.07.2018 09:57:57 INFO: GPU0 are restarted.
18.07.2018 09:57:58 WARNING: Looks like GPU1 are stopped. Restarting...
18.07.2018 09:57:58 INFO: GPU1 are restarted.
18.07.2018 09:57:58 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:58 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
18.07.2018 09:57:59 WARNING: Looks like GPU0 are stopped. Restarting...
After this message autorestarting loops until manual restart.
I'm using same OC settings as with v0.3 which were rock solid (up to 16 days of continous mining)
ATM I lowered OC a bit and testing if problem still occurs.
Jump to: