I'm not sure if this information is accessible through nvidia's official APIs.
It would be very usefull, with at least the brand name : GPU-Z manages to display brands.
Probably it uses it's own database to do so.
Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 125. (Read 224961 times)
October 30, 2017, 06:25:15 AM
It would be very usefull, with at least the brand name : GPU-Z manages to display brands.
Probably it uses it's own database to do so.
October 30, 2017, 06:07:49 AM
Can I use --time-limit and --retries options with dstm? It's not specified in the OP?
ZM doesn't have these options, I'm not sure what functionality they are for, is this something other miners have?
Yes, I used to use them as a fail safe in-case on of the stratum went down. See ccminer as example - https://github.com/tpruvot/ccminer/blob/windows/README.txt
--retries=N number of times to retry if a network call fails
--time-limit maximum time to mine before exiting the program
These options would be great and handy in-case of stratum or pool's offline.
ZM retries for about 15min currently before exiting, if it can't reach the pool server. This seems like a sensible default to me.
time-limit: this needs more explanation
Can we not change zm reties time period, it would great to have a default and user-definable option too..
time-limit uses a another stratum/pool for a defined period and then you can use it to go back to the orginal startum/pool check out ccminer it is opensource.... this would be a neat option!
October 30, 2017, 06:06:25 AM
dstm, thank you.
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.
Code:
zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x
7777 - port which is mapped to eu1-zcash.flypool.org:3333
Well, should I open the port 3443 on proxy-server as well? And where should I map it then?
eu1-zcash.flypool.org:3443
October 30, 2017, 06:03:56 AM
Can I use --time-limit and --retries options with dstm? It's not specified in the OP?
ZM doesn't have these options, I'm not sure what functionality they are for, is this something other miners have?
Yes, I used to use them as a fail safe in-case on of the stratum went down. See ccminer as example - https://github.com/tpruvot/ccminer/blob/windows/README.txt
--retries=N number of times to retry if a network call fails
--time-limit maximum time to mine before exiting the program
These options would be great and handy in-case of stratum or pool's offline.
ZM retries for about 15min currently before exiting, if it can't reach the pool server. This seems like a sensible default to me.
time-limit: this needs more explanation
October 30, 2017, 05:57:39 AM
dstm, thank you.
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.
Code:
zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x
7777 - port which is mapped to eu1-zcash.flypool.org:3333
Well, should I open the port 3443 on proxy-server as well? And where should I map it then?
October 30, 2017, 05:51:42 AM
I'm not sure if this information is accessible through nvidia's official APIs.
It would be very usefull, with at least the brand name : GPU-Z manages to display brands.
October 30, 2017, 05:49:52 AM
Can I use --time-limit and --retries options with dstm? It's not specified in the OP?
ZM doesn't have these options, I'm not sure what functionality they are for, is this something other miners have?
Yes, I used to use them as a fail safe in-case on of the stratum went down. See ccminer as example - https://github.com/tpruvot/ccminer/blob/windows/README.txt
--retries=N number of times to retry if a network call fails
--time-limit maximum time to mine before exiting the program
These options would be great and handy in-case of stratum or pool's offline.
October 30, 2017, 05:48:34 AM
@dstm : good job and tool.
I use it since 1 week on 5x 1070 or 3x 1080ti and it runs stable
Could you add some informations on startup about GPU (such as brand and serial number) ?
PCI and GPU identification are always a pity on mining rigs...
Telemetry doesn't work at all. But not very usefull to me.
Wait for the new release which will correct the --dev option
I use it since 1 week on 5x 1070 or 3x 1080ti and it runs stable
Could you add some informations on startup about GPU (such as brand and serial number) ?
PCI and GPU identification are always a pity on mining rigs...
Telemetry doesn't work at all. But not very usefull to me.
Wait for the new release which will correct the --dev option
I'm not sure if this information is accessible through nvidia's official APIs.
October 30, 2017, 05:46:00 AM
Can I use --time-limit and --retries options with dstm? It's not specified in the OP?
ZM doesn't have these options, I'm not sure what functionality they are for, is this something other miners have?
October 30, 2017, 05:43:41 AM
dstm, thank you.
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.
October 30, 2017, 05:39:31 AM
@dstm : good job and tool.
I use it since 1 week on 5x 1070 or 3x 1080ti and it runs stable
Could you add some informations on startup about GPU (such as brand and serial number) ?
PCI and GPU identification are always a pity on mining rigs...
Telemetry doesn't work at all. But not very usefull to me.
Wait for the new release which will correct the --dev option
I use it since 1 week on 5x 1070 or 3x 1080ti and it runs stable
Could you add some informations on startup about GPU (such as brand and serial number) ?
PCI and GPU identification are always a pity on mining rigs...
Telemetry doesn't work at all. But not very usefull to me.
Wait for the new release which will correct the --dev option
October 30, 2017, 05:33:40 AM
Can I use --time-limit and --retries options with dstm? It's not specified in the OP?
October 30, 2017, 05:30:54 AM
dstm, thank you.
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.
Could you tell me please why is that? ZM cannot properly work with proxy under Linux?
October 30, 2017, 05:21:02 AM
dstm, could you tell me please when can we expect the new release with fixed telemetry?
Thank you!
Thank you!
Stability is of highest priority. I had a report about issues on pool.sexy, so I wanna make sure it's not a general issue first. Telemetry: probably by the end of this week.
October 30, 2017, 05:09:07 AM
I'm not sure I understand it correctly - could you pls explain this a bit more.
I think what he means is that when telemetry fails to start due to whatever reason, miner won't start either. I noticed that as well, for me though it wasn't a problem.
Right, zm exits if it can't bind the telemetry server to a socket. I designed it this way to make sure your telemetry settings are correct before it starts mining.
concerning miner auto-start on (re)boot .....my experience is somewhat different
I am not able to autostart ZM with an entry in Cinnamon's Startup Application because on boot-up I always get 'telemetry binding failed' ,
however contrary to the above posting and your confirmation that ZM was designed to abort in that case - my miner starts up 'in the background' ...and in the end it turns out that the telemetry is also active!
What is disturbing is that after the (apparently misleading) message 'telemetry binding failed' ...the terminal falls back to the shell prompt.....and
no output from the actually running ZM is displayed afterwards.
It is even stranger, that if I run the same autostart entry directly from the Startup Application (my Cinnamon Startup Application has besides Add/Edit/Remove also a 'Run immediately' button perhaps new to Mint 18.2) then ZM starts succesfully....reports that telemetry is started and happily floods the terminal with the miner's output afterwards.
The command in Startup Application is:
Code:
gnome-terminal --tab -e "/bin/bash -c '/home/.../dstm/zm_0.5.3/zm --server eu1-zcash.flypool.org --port 3333 --user t1xxxxx.Worker --pass d=32000 --temp-target 70 --telemetry=0.0.0.0:51000; exec /bin/bash -i'" --working-directory="/home/..../dstm/zm_0.5.3"
I tested autostarting ZM with setting even delays up to 90 sec...to no avail.
kuksaab
---------------------------------
6 x GTX 1070 Rig
Linux Mint 18.2 GNU/Linux 4.10.0-37-generic, Cinnamon
dstm's ZCash Miner v0.5.3
ZM terminates if it can't bind telemetry to a socket. I'm not familiar with Cinnamon's Startup Application functionality, you might check if your network is up at this point, you might also check if your startup entry is executed twice somehow.
October 30, 2017, 04:53:10 AM
dstm, could you tell me please when can we expect the new release with fixed telemetry?
Thank you!
Thank you!
October 30, 2017, 04:42:48 AM
Maybe there is an opportunity to increase performance on GDDR5X? (1080 and 1080TI) Due to prefetch and 64B data per memory access ?
Actually this is something that increases memory latency as far as I understand.
Can be doubling the buffer in 2 times, eventually give more SOL with an increased delay? Is it possible to check?
There is some misunderstanding in this question, memory latency is crucial for performance.
October 30, 2017, 04:14:42 AM
Maybe there is an opportunity to increase performance on GDDR5X? (1080 and 1080TI) Due to prefetch and 64B data per memory access ?
Actually this is something that increases memory latency as far as I understand.
Can be doubling the buffer in 2 times, eventually give more SOL with an increased delay? Is it possible to check?
October 30, 2017, 03:18:39 AM
October 30, 2017, 03:09:58 AM
Jump to: