Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 111. (Read 224961 times)
November 16, 2017, 01:41:27 AM
so great, i see nothing different with 0.5.4
November 15, 2017, 05:25:50 PM
Hi,
I have no problem running zm from the cli (Linux)
But when I set it up as a service, it halts and restarts every couple of minutes.
I used the systemd unit file below. Has anyone tried running it as a service and is there something I'm setting up wrong in the unit file?
I have no problem running zm from the cli (Linux)
But when I set it up as a service, it halts and restarts every couple of minutes.
I used the systemd unit file below. Has anyone tried running it as a service and is there something I'm setting up wrong in the unit file?
Code:
[Unit]
Description=Start DSTM Miner
Documentation=man:syslog-ng(8)
[Service]
User=miner
Type=forking
ExecStart=/user/local/bin/zm --server zec-us.suprnova.cc --port 2142 --user xxx.xxx --pass xxx --telemetry=127.0.0.1:43000
StandardOutput=null
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
Code:
[Unit]
Description=Zcash Service
Wants=lightdm.service network-online.target
After=lightdm.service network-online.target
Conflicts=ccminer.service ewbf.service
[Service]
Environment=DISPLAY=:0
ExecReload=/bin/kill -HUP $MAINPID
ExecStartPre=/usr/bin/nvidia-smi -pl {{ gpu_watt }}
ExecStartPre=/usr/bin/nvidia-settings \
-a "GPUFanControlState=1" \
-a "GPUPowerMizerMode=1" \
-a "GPUTargetFanSpeed={{ gpu_fan }}" \
-a "GPUGraphicsClockOffset[3]={{ gpu_core }}" \
-a "GPUMemoryTransferRateOffset[3]={{ gpu_mem }}"
ExecStart=/opt/zcash/zm \
--telemetry=0.0.0.0:12345 \
--server {{ pool_url }} \
--port {{ pool_port }} \
--user {{ pool_user }} \
--pass {{ pool_password }}
ExecStopPost=/usr/bin/nvidia-settings \
-a "GPUGraphicsClockOffset[3]=0" \
-a "GPUMemoryTransferRateOffset[3]=0"
User={{ ansible_env.SUDO_USER }}
KillMode=mixed
Restart=always
RestartSec=10s
TimeoutStopSec=10
Nice=-20
ProtectSystem=full
ProtectHome=yes
[Install]
WantedBy=multi-user.target
November 15, 2017, 05:10:46 PM
Hi,
I have no problem running zm from the cli (Linux)
But when I set it up as a service, it halts and restarts every couple of minutes.
I used the systemd unit file below. Has anyone tried running it as a service and is there something I'm setting up wrong in the unit file?
I have no problem running zm from the cli (Linux)
But when I set it up as a service, it halts and restarts every couple of minutes.
I used the systemd unit file below. Has anyone tried running it as a service and is there something I'm setting up wrong in the unit file?
Code:
[Unit]
Description=Start DSTM Miner
Documentation=man:syslog-ng(8)
[Service]
User=miner
Type=forking
ExecStart=/user/local/bin/zm --server zec-us.suprnova.cc --port 2142 --user xxx.xxx --pass xxx --telemetry=127.0.0.1:43000
StandardOutput=null
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target
November 15, 2017, 04:19:36 PM
Hi dstm!
Testing your version since yesterday
today i wasn't @ home, ISP went down for about an hour, when I get home (now) miner is working, so it's all good!, the only thing I don't know if it was consuming power or not, it should stop mining if there is no connection , dunno if that happened, i have an AC power meter connected but it does not have log capability (something i gotta do
)
will keep testing but so far so good!, rock solid.
cheers
Indkt.
Testing your version since yesterday
today i wasn't @ home, ISP went down for about an hour, when I get home (now) miner is working, so it's all good!, the only thing I don't know if it was consuming power or not, it should stop mining if there is no connection , dunno if that happened, i have an AC power meter connected but it does not have log capability (something i gotta do
)will keep testing but so far so good!, rock solid.
cheers
Indkt.
Thx for testing the development version.
All GPUs are stopped during periods of connection loss ofc.
November 15, 2017, 04:04:24 PM
Hi dstm!
Testing your version since yesterday
today i wasn't @ home, ISP went down for about an hour, when I get home (now) miner is working, so it's all good!, the only thing I don't know if it was consuming power or not, it should stop mining if there is no connection , dunno if that happened, i have an AC power meter connected but it does not have log capability (something i gotta do )
will keep testing but so far so good!, rock solid.
cheers
Indkt.
Testing your version since yesterday
today i wasn't @ home, ISP went down for about an hour, when I get home (now) miner is working, so it's all good!, the only thing I don't know if it was consuming power or not, it should stop mining if there is no connection , dunno if that happened, i have an AC power meter connected but it does not have log capability (something i gotta do
)will keep testing but so far so good!, rock solid.
cheers
Indkt.
November 15, 2017, 01:36:59 PM
New Version 0.5.5
con: handle failure of dev share pool
con: disable reconnect limit
logfile: disable buffering
ZM doesn't rely on a single dev share server now - it uses one of the available flypool servers. I haven't added more pools to it mainly because I wasn't able to test their network reliability yet and because it adds additional difficulties for people who have to tunnel all their traffic through a proxy or limit outgoing network traffic to allowed hosts only.
Previous zm versions aborted their reconnect retries after 10 minutes, this timeout is removed now. ZM behaved like this because most people have some kind of notification on miner termination - 10 minute limit seemed reasonable to indicate larger network problems - however zm supports the --noreconnect option now - people who prefer to handle network errors themselves (e.g. with scripts) can use it instead the previous 10 minute reconnect timeout.
con: handle failure of dev share pool
con: disable reconnect limit
logfile: disable buffering
ZM doesn't rely on a single dev share server now - it uses one of the available flypool servers. I haven't added more pools to it mainly because I wasn't able to test their network reliability yet and because it adds additional difficulties for people who have to tunnel all their traffic through a proxy or limit outgoing network traffic to allowed hosts only.
Previous zm versions aborted their reconnect retries after 10 minutes, this timeout is removed now. ZM behaved like this because most people have some kind of notification on miner termination - 10 minute limit seemed reasonable to indicate larger network problems - however zm supports the --noreconnect option now - people who prefer to handle network errors themselves (e.g. with scripts) can use it instead the previous 10 minute reconnect timeout.
November 15, 2017, 08:19:47 AM
It's pretty well optimized, there are limits to it ofc. I have some ideas which might improve performance, they require some restructuring. So yes, this is something I'll work on.
What do you make of these rumors about "private kernels" that supposedly can do 1000 Sol/S on a 1080Ti? Pure fiction?
Given there are no major algorithmic differences in solvers - 1000 Sol/s on 1080Ti is slightly above it's limits even if memory latency was more ideal - however something similar might be reachable.
November 15, 2017, 08:17:45 AM
Tonight I had problem with two my rigs which has lost connection to server at same almost same time. After 10 minutes both servers have connected automatically back. Can you tell me dstm what is this error and what has caused? Thanks
On widows - error code 10054 on receive means:
Connection reset by peer - An existing connection was forcibly closed by the remote host.
So either your local internet connection was down or flypool's servers had some issues.
ZM resumed mining after the servers were reachable again.
I’ve check my rigs on second location and they had same problem so it is problem with connection to flypool. How I can be sure is it problem due to lost connection to flypool us server which I’m using or again it is problem with eu flypool which you are using for dev share?
ZM handles all connections equally so there is currently no difference in it's reconnection behaviour. ZM 0.5.5 is under testing now and doesn't rely on a single pool for dev shares. You're right it's useful to distinguish both cases however it's not always possible e.g. in cases where your network goes down - in this situation any of the connection might go down first.
eu1-zcash.flypool.org had no issues during that period according to my logs.
November 15, 2017, 06:32:09 AM
It's pretty well optimized, there are limits to it ofc. I have some ideas which might improve performance, they require some restructuring. So yes, this is something I'll work on.
What do you make of these rumors about "private kernels" that supposedly can do 1000 Sol/S on a 1080Ti? Pure fiction?
November 15, 2017, 05:36:21 AM
Tonight I had problem with two my rigs which has lost connection to server at same almost same time. After 10 minutes both servers have connected automatically back. Can you tell me dstm what is this error and what has caused? Thanks
On widows - error code 10054 on receive means:
Connection reset by peer - An existing connection was forcibly closed by the remote host.
So either your local internet connection was down or flypool's servers had some issues.
ZM resumed mining after the servers were reachable again.
I’ve check my rigs on second location and they had same problem so it is problem with connection to flypool. How I can be sure is it problem due to lost connection to flypool us server which I’m using or again it is problem with eu flypool which you are using for dev share?
November 15, 2017, 05:19:35 AM
Tonight I had problem with two my rigs which has lost connection to server at same almost same time. After 10 minutes both servers have connected automatically back. Can you tell me dstm what is this error and what has caused? Thanks
On widows - error code 10054 on receive means:
Connection reset by peer - An existing connection was forcibly closed by the remote host.
So either your local internet connection was down or flypool's servers had some issues.
ZM resumed mining after the servers were reachable again.
November 15, 2017, 05:15:23 AM
Are there any ways or opportunities to increase the productivity of the miner in new releases?
When should we expect a new version?
When should we expect a new version?
It's pretty well optimized, there are limits to it ofc. I have some ideas which might improve performance, they require some restructuring. So yes, this is something I'll work on.
November 15, 2017, 04:16:45 AM
Tonight I had problem with two my rigs which has lost connection to server at same almost same time. After 10 minutes both servers have connected automatically back. Can you tell me dstm what is this error and what has caused? Thanks
http://i64.tinypic.com/1zc3km.jpg
http://i64.tinypic.com/1zc3km.jpg
November 15, 2017, 04:05:40 AM
Are there any ways or opportunities to increase the productivity of the miner in new releases?
When should we expect a new version?
When should we expect a new version?
November 15, 2017, 01:54:40 AM
wow, nice find!
it is always easy to have in when you need it
and now no need to wait when it would be shown in the miner
thank you, ap0stol !
it is always easy to have in when you need it
and now no need to wait when it would be shown in the miner
thank you, ap0stol !
November 14, 2017, 11:46:28 PM
I'm sry, how it will be on win10?
create file with name somename.html (not txt or else)
with contents:
Code:
Miner Status
Thanx! Easy))
November 14, 2017, 11:38:48 PM
I'm sry, how it will be on win10?
create file with name somename.html (not txt or else)
with contents:
Code:
Miner Status
November 14, 2017, 02:45:26 PM
Thanks. This was something that Papampi posted in the nvOC thread, and that stubo modified. I'm running the following to prevent scroll bars:
Code:
m1@miner01:~$ cat /var/www/html/multiminerinfo.html
Miner Status
November 14, 2017, 12:54:34 PM
why Contains 2% devfee ? some hight !
November 14, 2017, 12:51:46 PM
Does nvidia-smi report power usage properly?
Nope:
Code:
m1@miner02:~$ nvidia-smi
Tue Nov 14 12:45:57 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 387.12 Driver Version: 387.12 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 105... Off | 00000000:01:00.0 Off | N/A |
| 50% 49C P0 ERR! / 75W | 521MiB / 4038MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 105... Off | 00000000:03:00.0 Off | N/A |
| 50% 50C P0 ERR! / 75W | 484MiB / 4038MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 105... Off | 00000000:06:00.0 Off | N/A |
| 50% 49C P0 ERR! / 75W | 484MiB / 4038MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 105... Off | 00000000:07:00.0 Off | N/A |
| 50% 48C P0 ERR! / 75W | 484MiB / 4038MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 105... Off | 00000000:08:00.0 Off | N/A |
| 50% 51C P0 ERR! / 75W | 484MiB / 4038MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 5 GeForce GTX 105... Off | 00000000:09:00.0 Off | N/A |
| 50% 48C P0 ERR! / 75W | 484MiB / 4038MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
Quote
Btw. that a nice usage of frames to have multiple rigs on one page. I was also thinking to provide a html template for something similar.
Thanks. This was something that Papampi posted in the nvOC thread, and that stubo modified. I'm running the following to prevent scroll bars:
Code:
m1@miner01:~$ cat /var/www/html/multiminerinfo.html
Miner Status
Jump to: