Topic: EWBF's CUDA Zcash miner - page 151. (Read 2164327 times)
What wallet do you guys use with this miner? Want to use some local one for zcash..trying to skip all these online exchanges, ppl saying there are some problems with EWBF.. how comes? ;/
Hi Guys, I planing to make some Nvidia rigs (6 x 1070 and 6 x 1060 setups), need some tips.
What is power consumption of 6x 1070 rig? Is it 1200w power supply strong enough? Also how much power draw 6 x gtx1060 3gb rig, is it supply of 850-1000w enough?
Next question is hash (Zcash), gtx1060 3gb can make 300sol, while gtx1070 can make about 480sol, is that right?
What is power consumption of 6x 1070 rig? Is it 1200w power supply strong enough? Also how much power draw 6 x gtx1060 3gb rig, is it supply of 850-1000w enough?
Next question is hash (Zcash), gtx1060 3gb can make 300sol, while gtx1070 can make about 480sol, is that right?
I keep getting "ERROR: Cannot connect to the server. 7". Specifically:
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
Code:
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:16666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
How are you launching EWBF; and what arguments are you using?
Code:
./miner --server zec-us-west1.nanopool.org --port 16666 --user zec_wallet.worker --pass x
I've replaced my real wallet address for privacy, but that's essentially it.
that appears correct, I would try nanopools other port: 6666 also I don't think it matters but change --pass to : z
Code:
./miner --server zec-us-west1.nanopool.org --port 6666 --user zec_wallet.worker --pass z --templimit 80
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:6666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 80
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Yeah, I don't get it. I've tried 6666, 16666 and eu/us hosts, and 3333 for flypool etc, always that error. And i've tried x and z for pass.
I tried claymore, but it only supports AMD for zec. I used claymore for eth just fine on nanopool and ethermine. It's something about ewbf I feel like.
I use it with Ubuntu 16.04 no problem. This is how I launch it with more arguments and an absolute path to the client:
'/home/m1/zec/miner' --eexit 3 --fee 0 --pec --server zec-us-east1.nanopool.org --user zecADDR.worker --pass z --port 6666;
I mine under Ubuntu 16.04 because its faster than Windows 10 (the primary gfx card used for display seems ununsable under Windows 10).
Anyway, I booted into Win 10 today, downloaded the miner and tried it, but same.
My mine.cmd has:
Code:
miner --eexit 3 --fee 0 --pec --server zec-us-west1.nanopool.org --port 6666 --user zec_wallet.worker --pass x --templimit 80
And when I run it, same shit:
Code:
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:6666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 80
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
D:\Zcash\Zec.miner.0.3.3b>
So it's not even a Linux or Ubuntu thing. Comcast? IPv6? What could it be :/
--user zec_wallet.worker
There is 1 too many space in the user param but I dont know if it matters or not.
I am at work so I cant test it for you.
Have you tried changing the order of your params? Not sure if it would help, but all of my miners run in the following sequence.
--server xxxx --port xxxx --user xxxx --pass x --pec --log 1 --fee x
I have never mined to nanopool, but do you need to authorize the user before it can connect? I have seen it with dwarfpool (from memory) rejecting the connection because the user wasn't authorized on the account.
--server xxxx --port xxxx --user xxxx --pass x --pec --log 1 --fee x
I have never mined to nanopool, but do you need to authorize the user before it can connect? I have seen it with dwarfpool (from memory) rejecting the connection because the user wasn't authorized on the account.
I keep getting "ERROR: Cannot connect to the server. 7". Specifically:
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
Code:
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:16666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
How are you launching EWBF; and what arguments are you using?
Code:
./miner --server zec-us-west1.nanopool.org --port 16666 --user zec_wallet.worker --pass x
I've replaced my real wallet address for privacy, but that's essentially it.
that appears correct, I would try nanopools other port: 6666 also I don't think it matters but change --pass to : z
Code:
./miner --server zec-us-west1.nanopool.org --port 6666 --user zec_wallet.worker --pass z --templimit 80
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:6666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 80
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Yeah, I don't get it. I've tried 6666, 16666 and eu/us hosts, and 3333 for flypool etc, always that error. And i've tried x and z for pass.
I tried claymore, but it only supports AMD for zec. I used claymore for eth just fine on nanopool and ethermine. It's something about ewbf I feel like.
I use it with Ubuntu 16.04 no problem. This is how I launch it with more arguments and an absolute path to the client:
'/home/m1/zec/miner' --eexit 3 --fee 0 --pec --server zec-us-east1.nanopool.org --user zecADDR.worker --pass z --port 6666;
I mine under Ubuntu 16.04 because its faster than Windows 10 (the primary gfx card used for display seems ununsable under Windows 10).
Anyway, I booted into Win 10 today, downloaded the miner and tried it, but same.
My mine.cmd has:
Code:
miner --eexit 3 --fee 0 --pec --server zec-us-west1.nanopool.org --port 6666 --user zec_wallet.worker --pass x --templimit 80
And when I run it, same shit:
Code:
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:6666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 80
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
D:\Zcash\Zec.miner.0.3.3b>
So it's not even a Linux or Ubuntu thing. Comcast? IPv6? What could it be :/
Guys, do you know how to automatically restart the EWBF miner when the card is not response and produce 0 sols? I ran 7 1080ti on Win 10, about 5-10 hours, the 7 card stop working and produce 0 sols although the miner tried to restart the card several times, so the result is I need to close the miner and open in again in order making it to work. I run in bios stock and 80% power limit
Does it close the miner if you use --eexit 3?
If so you could just run the miner in a loop:
:loop
miner.exe ...
goto loop
If it doesn't quit and just get stuck then you could restart the miner periodically (like every couple hours) by running it in a loop like above and have another loop running which terminates the miner. Not ideal but better than having the cards not working for hours:
:restartloop
timeout -t 3600
taskkill -t -f /im miner.exe
goto restartloop
that is very helpful i was searching for something like this, but what i need is a bat that can start again the miners if the miner crash, or if after the system bsod, start it again, it's possible for a simple script to get somethign like this?
how to trigger shutdown /f /t 5 if miner has problem, i don't want to restart the miner because sometime one card stop working and only restart the pc can solve it
Not sure but a card crashing that only a restart (or nvidiainspector.exe -restartdisplaydriver solves) is usually caused by too high overclock.
I used -eexit 3, the miner was not closed, it tried to restart the GPU and it restarted successfully, however after the restart, the GPU produce 0 sols and so the miner keep running. I think it may come from the temperature, I only see the problem when it reach 70 degree C, although I set the limit at 85.
I will try the loop later, seems it is the only way to solve the problem.
One more thing is sometime my rig crashed, the computer is hanged, mouse can not move, but the GPU and CPU fan are still running like crazy, the only way to solve it is to unplug the power, I am not sure if it is because I ran 7 cards or not, I thought it should be fine since my MOBO support 7 pci
Just for the record, here is my spec
Mobo Asus z270a
CPU g4560 3.5ghz
Ram 8gb
7 gtx 1080ti
PSU 1600w
Win 10 home
I will try the loop later, seems it is the only way to solve the problem.
One more thing is sometime my rig crashed, the computer is hanged, mouse can not move, but the GPU and CPU fan are still running like crazy, the only way to solve it is to unplug the power, I am not sure if it is because I ran 7 cards or not, I thought it should be fine since my MOBO support 7 pci
Just for the record, here is my spec
Mobo Asus z270a
CPU g4560 3.5ghz
Ram 8gb
7 gtx 1080ti
PSU 1600w
Win 10 home
Guys, do you know how to automatically restart the EWBF miner when the card is not response and produce 0 sols? I ran 7 1080ti on Win 10, about 5-10 hours, the 7 card stop working and produce 0 sols although the miner tried to restart the card several times, so the result is I need to close the miner and open in again in order making it to work. I run in bios stock and 80% power limit
Does it close the miner if you use --eexit 3?
If so you could just run the miner in a loop:
:loop
miner.exe ...
goto loop
If it doesn't quit and just get stuck then you could restart the miner periodically (like every couple hours) by running it in a loop like above and have another loop running which terminates the miner. Not ideal but better than having the cards not working for hours:
:restartloop
timeout -t 3600
taskkill -t -f /im miner.exe
goto restartloop
Guys, do you know how to automatically restart the EWBF miner when the card is not response and produce 0 sols? I ran 7 1080ti on Win 10, about 5-10 hours, the 7 card stop working and produce 0 sols although the miner tried to restart the card several times, so the result is I need to close the miner and open in again in order making it to work. I run in bios stock and 80% power limit
Does it close the miner if you use --eexit 3?
If so you could just run the miner in a loop:
:loop
miner.exe ...
goto loop
If it doesn't quit and just get stuck then you could restart the miner periodically (like every couple hours) by running it in a loop like above and have another loop running which terminates the miner. Not ideal but better than having the cards not working for hours:
:restartloop
timeout -t 3600
taskkill -t -f /im miner.exe
goto restartloop
Guys, do you know how to automatically restart the EWBF miner when the card is not response and produce 0 sols? I ran 7 1080ti on Win 10, about 5-10 hours, the 7 card stop working and produce 0 sols although the miner tried to restart the card several times, so the result is I need to close the miner and open in again in order making it to work. I run in bios stock and 80% power limit
Hello. I'm using EWBF's CUDA Zcash miner 0.3.3b but when I start the miner it closes immediately. It was working fine on that PC with 2 1080ti and after it gave me 0 sols I closed the miner and since then I cannot start it.
I've reinstalled drivers, downloaded a new copy of the miner, but it is the same problem - the miner opens and closes after a few seconds.
I've reinstalled drivers, downloaded a new copy of the miner, but it is the same problem - the miner opens and closes after a few seconds.
Could be your anti-virus. Disable it and download a fresh copy.
I get that error as well sometimes, kind of annoying. Too bad the miner doesn't have an option to try reconnecting after a few seconds.
I keep getting "ERROR: Cannot connect to the server. 7". Specifically:
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
Code:
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:16666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
How are you launching EWBF; and what arguments are you using?
Code:
./miner --server zec-us-west1.nanopool.org --port 16666 --user zec_wallet.worker --pass x
I've replaced my real wallet address for privacy, but that's essentially it.
that appears correct, I would try nanopools other port: 6666 also I don't think it matters but change --pass to : z
Code:
./miner --server zec-us-west1.nanopool.org --port 6666 --user zec_wallet.worker --pass z --templimit 80
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:6666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 80
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Yeah, I don't get it. I've tried 6666, 16666 and eu/us hosts, and 3333 for flypool etc, always that error. And i've tried x and z for pass.
I tried claymore, but it only supports AMD for zec. I used claymore for eth just fine on nanopool and ethermine. It's something about ewbf I feel like.
I keep getting "ERROR: Cannot connect to the server. 7". Specifically:
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
Code:
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:16666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
How are you launching EWBF; and what arguments are you using?
Code:
./miner --server zec-us-west1.nanopool.org --port 16666 --user zec_wallet.worker --pass x
I've replaced my real wallet address for privacy, but that's essentially it.
I keep getting "ERROR: Cannot connect to the server. 7". Specifically:
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
Code:
+-------------------------------------------------+
| EWBF's Zcash CUDA miner. 0.3.3b |
+-------------------------------------------------+
INFO: Server: zec-us-west1.nanopool.org:16666
INFO: Solver Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
ERROR: Cannot connect to the server. 7
Running on Ubuntu 16.04.
I've tried nanopool, flypool, EU and US stratum servers for both, backup and primary ports for both, etc. etc.
I've run tcpdump and I see it connecting and sending the tcp packet (I see the json payload) but no response comes back.
I can even telnet to that hostname:port combination.
Any ideas??
Windows rightmouse on win dows icon
select run type cmd.exe
select run type cmd.exe
FTW: right-click in windows explorer while holding shift key and select "open command windows here".
Windows rightmouse on win dows icon
select run type cmd.exe
select run type cmd.exe
Hello. I'm using EWBF's CUDA Zcash miner 0.3.3b but when I start the miner it closes immediately. It was working fine on that PC with 2 1080ti and after it gave me 0 sols I closed the miner and since then I cannot start it.
I've reinstalled drivers, downloaded a new copy of the miner, but it is the same problem - the miner opens and closes after a few seconds.
I've reinstalled drivers, downloaded a new copy of the miner, but it is the same problem - the miner opens and closes after a few seconds.
try to run commands in terminal so you can see what closes it.
I'm using windows 10. Can you explain how to do that?
Hello. I'm using EWBF's CUDA Zcash miner 0.3.3b but when I start the miner it closes immediately. It was working fine on that PC with 2 1080ti and after it gave me 0 sols I closed the miner and since then I cannot start it.
I've reinstalled drivers, downloaded a new copy of the miner, but it is the same problem - the miner opens and closes after a few seconds.
I've reinstalled drivers, downloaded a new copy of the miner, but it is the same problem - the miner opens and closes after a few seconds.
try to run commands in terminal so you can see what closes it.
Jump to: