 Show Posts
|
|
Pages: [1]
|
Hi,
I'am getting this error since 10 days agora:
clSetKernelArg (-48)
@PhoenixMiner How can we solve this? I see that there are many other users on reddit experiencing the same issue.
check: driver version and DAG "eres -1 or 0" not eres 2 Thanks but it doesn't solve changing the -eres to "1" or "0", I am using driver version 20.10... |
|
|
|
|
Hi,
I'am getting this error since 10 days agora:
clSetKernelArg (-48)
@PhoenixMiner How can we solve this? I see that there are many other users on reddit experiencing the same issue.
|
|
|
|
|
Hi,
Thanks for the 0.8.0, it really improved hashrate. Just notice that your miner doesn't have the --straps option like phoenixminer or claymore, could you had it too to your next release?
Thanks
|
|
|
|
|
Monitorig is down, thoober can you fix it please?
Thanks
|
|
|
|
|
Thoober, what is happening?
|
|
|
|
|
Hi, monitorig web page is offline. What is happening?
|
|
|
|
Using ZM I have my GPU monitored and if I click logfile i can see it hashing but always says not hashing
Same here, I have 5 rigs working well, and sending mining information to monitorig, but I have another one with this problem "Miner is not running or not hashing". Miner have logfiles, and it is mining. Got this erro in screenshot folder:  |
|
|
|
|
Seems that we have a problem using monitorig + farmwatchbot + claymore_zec. When I configure this system, i cant get info in monitorig, because logfiles are in the log folder, and monitorig rig only collects logs from the main folder of the miner. Can anyone resolve this issue?
Farmwatchbot creates a log file named "miner.log" and it cant work if I renamed it.
Ps: works fine with dstm miner aka “zm”
|
|
|
|
|
Hi, this version really needs a fix.
If my rigs lost connection with the server, miner just stops the software and closes. It is supposed to try to reconnect with the server, but is not doing that.
I have my rigs connected with powerline adaptares, so the connection brakes for 3 seconds 3/4 times a day. I NEED A FIX PLS!
|
|
|
|
error code 10054:
Connection reset by peer - An existing connection was forcibly closed by the remote host.
So either your local internet connection was down or the pool-servers had some issues.
So if connection goes down the miner stop? no reconection (so that is what happen).... |
|
|
|
|
Hi, after doing the right adjusts to monitor ZM miner, I stopped receiving email reports. It was doing that with ewbf before, now if one rig goes down, i dont receive any email. Can you help me?
|
|
|
|
Hi, dstm! Big thanks for your miner.
I gets a lot of RECV, farm reconnects and keep working, but I think, that shares a lost.
2018-01-08 7:44:12| ========== Sol/s: 2326.0 Sol/W: 3.46 Avg: 2293.5 I/s: 1249.0 Sh: 7.86 0.99 178
2018-01-08 7:44:15|# recv failed: 10054
2018-01-08 7:44:15|# reconnecting
2018-01-08 7:44:26|# connected to: eu1-zcash.flypool.org:3333
2018-01-08 0:58:46|nvmlDeviceGetTemperature failed (this is my farm goes to sleep! Fixed)
2018-01-08 7:31:52|> GPU0 32C Sol/s: 0.2 Sol/W: 3.45 Avg: 473.8 I/s: 0.1 Sh: 1.82 0.99 78
2018-01-08 7:31:52| GPU3 33C Sol/s: 0.1 Sol/W: 3.29 Avg: 452.8 I/s: 0.0 Sh: 1.47 1.00 78
2018-01-08 7:31:52| GPU2 33C Sol/s: 0.1 Sol/W: 3.39 Avg: 465.2 I/s: 0.1 Sh: 1.40 1.00 109
2018-01-08 7:31:52|> GPU4 32C Sol/s: 0.3 Sol/W: 3.87 Avg: 463.6 I/s: 0.2 Sh: 1.97 1.00 553
2018-01-08 7:31:52| ========== Sol/s: 465.6 Sol/W: 3.48 Avg: 2324.2 I/s: 251.2 Sh: 8.32 1.00 179
2018-01-08 7:31:53| GPU1 33C Sol/s: 0.1 Sol/W: 3.39 Avg: 464.9 I/s: 0.1 Sh: 1.64 1.00 78
2018-01-08 7:32:06| GPU1 40C Sol/s: 310.9 Sol/W: 3.38 Avg: 463.6 I/s: 169.5 Sh: 1.63 1.00 78
2018-01-08 7:32:06| GPU0 38C Sol/s: 345.2 Sol/W: 3.45 Avg: 472.8 I/s: 183.6 Sh: 1.80 0.99 78
2018-01-08 7:32:07| GPU3 40C Sol/s: 327.9 Sol/W: 3.29 Avg: 451.8 I/s: 176.5 Sh: 1.46 1.00 78
2018-01-08 7:32:07|# recv failed: 10054
2018-01-08 7:32:07|# reconnecting
2018-01-08 7:32:18|# connected to: eu1-zcash.flypool.org:3333
2018-01-08 7:32:21|# server set difficulty to: 0004189374bc6a7ef9db22d0...
I changes overclocking for minimum (tdp 50%), but RECV still my guest.
Sorry for my bad english.
This is not due to overclocking, it's a network issue, are you on wifi? Nope, recv failed: 10054 is a socket error. Please fix this issues, it seems that your miner is very good on the hashrate but need some fix on network side. |
|
|
|
|
