[ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows)

[akuci]

I think you should release 0.7 and then wait for the "asic" outcome to add the ne algos maybe.

[1714704958]

1714704958

[Andrey09]

On v.7 will some improvements? May be GDDR5X optimisation?

[wetblanket]

I had a crash this morning on Linux with DSTM Miner v0.6:

*** stack smashing detected ***: ./zmminer terminated

 

Could you pls provide your startup configuration?

Again this morning, same error message.

I don't use a config file, I call zmminer in a bash script:

./zmminer --server $server --port $port \
          --telemetry \
          --user $worker --pass x \
           --time >> "$log" 2>&1

Thanks

Do your log files contain a 'unresponsive gpu' message before the crash?

I didn't see any follow-up on this from `symbiosoft`, but have run into this twice over the last week or so myself. Here are the last few lines of output:

Code:

2018-05-07 04:41:33 AM|   ========== Sol/s: 2768.4 Sol/W: 4.02  Avg: 2767.2 I/s: 1482.3 Sh: 31.30  1.00 113
2018-05-07 04:41:46 AM|   GPU0  55C  Sol/s: 460.4  Sol/W: 4.07  Avg: 466.8  I/s: 249.2  Sh: 4.49   1.00 114 +
2018-05-07 04:41:47 AM|   GPU2  59C  Sol/s: 466.7  Sol/W: 3.97  Avg: 455.7  I/s: 244.6  Sh: 5.16   1.00 116 +
2018-05-07 04:41:47 AM|   GPU1  55C  Sol/s: 467.2  Sol/W: 4.06  Avg: 465.3  I/s: 249.5  Sh: 5.81   1.00 115
*** stack smashing detected ***: zm_0.6/zm terminated
Aborted (core dumped)

I'm running with this on the command line (Ubuntu Linux 16.04):

Code:

zm_0.6/zm --time --server us-east.equihash-hub.miningpoolhub.com --port 17023 --user login.rig --pass pass

Here's my latest one (this is new, the previously quoted crash was all I'd seen before now):

Code:

2018-05-09 05:26:50 PM|   ========== Sol/s: 2768.1 Sol/W: 4.02  Avg: 2763.7 I/s: 1479.6 Sh: 2.35   0.99 270
2018-05-09 05:26:50 PM|   GPU2  60C  Sol/s: 456.8  Sol/W: 3.97  Avg: 455.5  I/s: 243.8  Sh: 0.39   1.00 610
2018-05-09 05:26:54 PM|   GPU3  61C  Sol/s: 454.8  Sol/W: 3.98  Avg: 456.6  I/s: 244.6  Sh: 0.38   0.99 204
2018-05-09 05:26:57 PM|   GPU1  56C  Sol/s: 470.0  Sol/W: 4.06  Avg: 466.0  I/s: 249.6  Sh: 0.39   0.99 201
2018-05-09 05:26:59 PM|#  server set difficulty to: 00011f7d098fe205b0000000...
2018-05-09 05:27:02 PM|>  GPU4  64C  Sol/s: 454.4  Sol/W: 4.01  Avg: 459.6  I/s: 246.2  Sh: 0.40   0.99 205
2018-05-09 05:27:04 PM|>  GPU0  58C  Sol/s: 467.9  Sol/W: 4.05  Avg: 464.4  I/s: 248.3  Sh: 0.41   1.00 202
2018-05-09 05:27:08 PM|gpu_id 1 61 3 unspecified launch failure
2018-05-09 05:27:08 PM|gpu 1 unresponsive - check overclocking
2018-05-09 05:27:08 PM|cudaMemcpy 1 failed
Segmentation fault (core dumped)

I assume most others would confirm this is overclock related (duh, the error message?!) - maybe due to the warmer spring weather pushing ambient temperatures up? But, my temps are all consistently below 70C, so this would still surprise me as NOTHING else has changed on this machine since it was rock solid before, other than time has passed and temps have risen. <sadface>

Only other option is a loose/malfunctioning riser, I suppose.

[jpl]

Just a few quick questions...  so when, "server sets difficulty",.. is it set and locked?.. because when I up the settings on my cards while running in afterburner,.. I would expect my sol/s to go up.. but they stay the same.
Maybe I should launch cards with higher settings (in afterburner) to get a better difficulty rate?
Should I not change card settings after launching bat file?
Also, if I change afterburner settings while running,. does it stay on the same pool?.. Or is it better to restart miner to reconnect.. where it looks like it does the "server sets difficulty" again.

thx all

[suwbw]

Hello. Why I can't download the latest version 0.7 from drive.google? It says me there is a virus:

Sorry, this file is infected with a virus

Only the owner is allowed to download infected files.

[Coin++]

Hello. Why I can't download the latest version 0.7 from drive.google? It says me there is a virus:

Sorry, this file is infected with a virus

Only the owner is allowed to download infected files.

Hello,
You can't download the latest version 0.7 because they do not exist : we are at 0.6 version.

[suwbw]

Hello,
You can't download the latest version 0.7 because they do not exist : we are at 0.6 version.

Yes, I mean 0.6 not 0.7. Just my mistake.

[activatorwmw]

I had a crash this morning on Linux with DSTM Miner v0.6:

*** stack smashing detected ***: ./zmminer terminated

 

Could you pls provide your startup configuration?

Again this morning, same error message.

I don't use a config file, I call zmminer in a bash script:

./zmminer --server $server --port $port \
          --telemetry \
          --user $worker --pass x \
           --time >> "$log" 2>&1

Thanks

Do your log files contain a 'unresponsive gpu' message before the crash?

I didn't see any follow-up on this from `symbiosoft`, but have run into this twice over the last week or so myself. Here are the last few lines of output:

Code:

2018-05-07 04:41:33 AM|   ========== Sol/s: 2768.4 Sol/W: 4.02  Avg: 2767.2 I/s: 1482.3 Sh: 31.30  1.00 113
2018-05-07 04:41:46 AM|   GPU0  55C  Sol/s: 460.4  Sol/W: 4.07  Avg: 466.8  I/s: 249.2  Sh: 4.49   1.00 114 +
2018-05-07 04:41:47 AM|   GPU2  59C  Sol/s: 466.7  Sol/W: 3.97  Avg: 455.7  I/s: 244.6  Sh: 5.16   1.00 116 +
2018-05-07 04:41:47 AM|   GPU1  55C  Sol/s: 467.2  Sol/W: 4.06  Avg: 465.3  I/s: 249.5  Sh: 5.81   1.00 115
*** stack smashing detected ***: zm_0.6/zm terminated
Aborted (core dumped)

I'm running with this on the command line (Ubuntu Linux 16.04):

Code:

zm_0.6/zm --time --server us-east.equihash-hub.miningpoolhub.com --port 17023 --user login.rig --pass pass

Here's my latest one (this is new, the previously quoted crash was all I'd seen before now):

Code:

2018-05-09 05:26:50 PM|   ========== Sol/s: 2768.1 Sol/W: 4.02  Avg: 2763.7 I/s: 1479.6 Sh: 2.35   0.99 270
2018-05-09 05:26:50 PM|   GPU2  60C  Sol/s: 456.8  Sol/W: 3.97  Avg: 455.5  I/s: 243.8  Sh: 0.39   1.00 610
2018-05-09 05:26:54 PM|   GPU3  61C  Sol/s: 454.8  Sol/W: 3.98  Avg: 456.6  I/s: 244.6  Sh: 0.38   0.99 204
2018-05-09 05:26:57 PM|   GPU1  56C  Sol/s: 470.0  Sol/W: 4.06  Avg: 466.0  I/s: 249.6  Sh: 0.39   0.99 201
2018-05-09 05:26:59 PM|#  server set difficulty to: 00011f7d098fe205b0000000...
2018-05-09 05:27:02 PM|>  GPU4  64C  Sol/s: 454.4  Sol/W: 4.01  Avg: 459.6  I/s: 246.2  Sh: 0.40   0.99 205
2018-05-09 05:27:04 PM|>  GPU0  58C  Sol/s: 467.9  Sol/W: 4.05  Avg: 464.4  I/s: 248.3  Sh: 0.41   1.00 202
2018-05-09 05:27:08 PM|gpu_id 1 61 3 unspecified launch failure
2018-05-09 05:27:08 PM|gpu 1 unresponsive - check overclocking
2018-05-09 05:27:08 PM|cudaMemcpy 1 failed
Segmentation fault (core dumped)

I assume most others would confirm this is overclock related (duh, the error message?!) - maybe due to the warmer spring weather pushing ambient temperatures up? But, my temps are all consistently below 70C, so this would still surprise me as NOTHING else has changed on this machine since it was rock solid before, other than time has passed and temps have risen. <sadface>

Only other option is a loose/malfunctioning riser, I suppose.

I think you set too low power

[chaostic]

yes you def need to turn power back up, i can tell those are 1070 ti, and also reading 50 less than it should be, and then about 100 less than on full tilt, power should be never below 84%, pretty much never above 92% unless catching up or something, currently my 1070 ti's are set to kernel mode, extended msi setting, 94% TPD, +176/+604 (lots of wiggle room with the 1070 ti's, once u go under about 88% the 1070z suffer really hard, keep that in mind when finding a lower efficiency setting.) hopefully a dstm update for windows comes out soon, as we have been waiting a while, 0.7 can be released now and 0.7.1 released in few weeks, we dont have much time so the dev needs to understand we need the miner up to date asap before asics hit and we have to switch coins to mine q=]  PS: 4 sols per watt is possible, but who is going to want nor need to turn a 1070 ti down to 58% TPD lol

[JukNi]

Hi,

I have been using DSTM miner for zcash for some time now and first I have to say BIG THANK YOU it´s really good and stable miner.
But one question about Dev Fee

Code:

ZM's output on system with 7 GPUs:

>  GPU0 42°C  Sol/s: 739.0  Sol/W: 2.85  Avg: 739.0  I/s: 390.1  Sh: 54.00  1.00  29  ++++++++++++++++++
>  GPU1 44°C  Sol/s: 459.0  Sol/W: 2.91  Avg: 459.0  I/s: 243.5  Sh: 27.00  1.00  29  +++++++++
>  GPU2 46°C  Sol/s: 451.3  Sol/W: 2.77  Avg: 451.3  I/s: 243.5  Sh: 15.00  1.00  28  +++++
>  GPU3 43°C  Sol/s: 449.7  Sol/W: 2.83  Avg: 449.7  I/s: 242.8  Sh: 24.00  1.00  29  ++++++++*
>  GPU4 42°C  Sol/s: 449.0  Sol/W: 2.76  Avg: 449.0  I/s: 243.5  Sh: 36.00  1.00  28  ++++++++++++
   GPU5 43°C  Sol/s: 446.4  Sol/W: 2.79  Avg: 446.4  I/s: 243.6  Sh: 30.00  1.00  28  ++++++++++
   GPU6 42°C  Sol/s: 461.4  Sol/W: 2.84  Avg: 461.4  I/s: 243.8  Sh: 18.00  1.00  28  ++++++
   ========== Sol/s: 3455.8 Sol/W: 2.82  Avg: 3455.8 I/s: 1850.9 Sh: 204.00 1.00  28

This is example from Readme.txt, but when that star (*) notify that Dev Fee is taken, will it take in this example case just one share or all of those 8 shares,
or is there 9 shares and one is Dev Fee and those 8 shares is for miners own shares ?

Sorry this dummy question.

[korenchkin]

Just a few quick questions...  so when, "server sets difficulty",.. is it set and locked?.. because when I up the settings on my cards while running in afterburner,.. I would expect my sol/s to go up.. but they stay the same.
Maybe I should launch cards with higher settings (in afterburner) to get a better difficulty rate?
Should I not change card settings after launching bat file?
Also, if I change afterburner settings while running,. does it stay on the same pool?.. Or is it better to restart miner to reconnect.. where it looks like it does the "server sets difficulty" again.

thx all

i mine on coinfoundry and server sets difficulty dynamically,after each ~3-10 lines in dstm for me on 1080ti,it's probably regulating depending on my mining luck (your results will vary depending on hash power i guess)

[dstm]

Emergency shutdown:
Yes, I can add something like this.
However what exactly should happen after the temp-limit is reached on one of the GPUs? should zm terminate immediately?
Also don't forget, a user-space program can't guarantee you to react properly with respect to this (the hardware or the driver can get unresponsive) - however it should work in most cases.

I'd say stop using overheated GPU and keep informing about it in console, like Claymore's or EWBF's behavior. I know, the driver or hardware will shutdown it in case of overheat, but 100° is not healthy.
Maybe --temp-target can handle sudden rise of temperature and we don't need the emergency shutdown at all, but it's just not obvious from the description.

I've put this to my notes - will think about it, thx.

[dstm]

Hi,

I have been using DSTM miner for zcash for some time now and first I have to say BIG THANK YOU it´s really good and stable miner.
But one question about Dev Fee

Code:

ZM's output on system with 7 GPUs:

>  GPU0 42°C  Sol/s: 739.0  Sol/W: 2.85  Avg: 739.0  I/s: 390.1  Sh: 54.00  1.00  29  ++++++++++++++++++
>  GPU1 44°C  Sol/s: 459.0  Sol/W: 2.91  Avg: 459.0  I/s: 243.5  Sh: 27.00  1.00  29  +++++++++
>  GPU2 46°C  Sol/s: 451.3  Sol/W: 2.77  Avg: 451.3  I/s: 243.5  Sh: 15.00  1.00  28  +++++
>  GPU3 43°C  Sol/s: 449.7  Sol/W: 2.83  Avg: 449.7  I/s: 242.8  Sh: 24.00  1.00  29  ++++++++*
>  GPU4 42°C  Sol/s: 449.0  Sol/W: 2.76  Avg: 449.0  I/s: 243.5  Sh: 36.00  1.00  28  ++++++++++++
   GPU5 43°C  Sol/s: 446.4  Sol/W: 2.79  Avg: 446.4  I/s: 243.6  Sh: 30.00  1.00  28  ++++++++++
   GPU6 42°C  Sol/s: 461.4  Sol/W: 2.84  Avg: 461.4  I/s: 243.8  Sh: 18.00  1.00  28  ++++++
   ========== Sol/s: 3455.8 Sol/W: 2.82  Avg: 3455.8 I/s: 1850.9 Sh: 204.00 1.00  28

This is example from Readme.txt, but when that star (*) notify that Dev Fee is taken, will it take in this example case just one share or all of those 8 shares,
or is there 9 shares and one is Dev Fee and those 8 shares is for miners own shares ?

Sorry this dummy question.

*' denotes one dev-share, so in this particular example 8 user shares and one dev share were found.

[dstm]

New Version 0.6.1

I'm releasing 0.6.1 (an update of the 0.6 branch) instead of the planned 0.7 (based on new architecture) - mainly because 0.7's development takes more time than expected and due the recent events. It contains some bug fixes and improvements you have asked for. 0.6.1 improves the performance on linux-system by about 2% - unfortunately it's not possible to take advantage of this particular improvement on windows-systems. I've slightly changed the terminal-ui so if you're parsing it be aware of it. There is a second incompatibility: the cmd-line parameter '--temp-target' supports now the configuration of individual GPUs, it's syntax has changed because of this.

0.6.1
- fix failover-pool not switching back on ssl errors
- fix failover-pool not switching back on some servers
- add support for stratum's client.reconnect rpc
- support configuration of 'temp-target', 'intensity', 'pool' via cmd-line parameters
- report current difficulty and target on term-ui
- sort output by gpu_id on term-ui
- colorize temperature above 70°C on term-ui
- report intended fan speed on term-ui, web-ui, json-rpc
- report power consumption on term-ui
- improve performance on linux systems by ~2%

[BinaryFarming]

Where can I find detailed info on all the config file options? Specifically how does one add failover pools in a config file?

[smajser]

Hi @dstm,

when I use version 0.6.1, miner shows big network latency time.
In version 0.6.0 everything works normally.

http://i63.tinypic.com/x3cvop.jpg


Best regards

[akuci]

Great work @DSTM!
Very friendly console output now.

[chaostic]

sorry I'm kinda new here.
I have somequestion, first the correct format for my worker name on nanopool is --user[SPACE]Mywalletaddress[DOT]Worker'sname[SLASH]Email right?
And does this miner have API option like EWBF's one
Thank you

Everything you just asked for is in the readme man.

[jpl]

New Version 0.6.1

I'm releasing 0.6.1 (an update of the 0.6 branch) instead of the planned 0.7 (based on new architecture) - mainly because 0.7's development takes more time than expected and due the recent events. It contains some bug fixes and improvements you have asked for. 0.6.1 improves the performance on linux-system by about 2% - unfortunately it's not possible to take advantage of this particular improvement on windows-systems. I've slightly changed the terminal-ui so if you're parsing it be aware of it. There is a second incompatibility: the cmd-line parameter '--temp-target' supports now the configuration of individual GPUs, it's syntax has changed because of this.

0.6.1
- fix failover-pool not switching back on ssl errors
- fix failover-pool not switching back on some servers
- add support for stratum's client.reconnect rpc
- support configuration of 'temp-target', 'intensity', 'pool' via cmd-line parameters
- report current difficulty and target on term-ui
- sort output by gpu_id on term-ui
- colorize temperature above 70°C on term-ui
- report intended fan speed on term-ui, web-ui, json-rpc
- report power consumption on term-ui
- improve performance on linux systems by ~2%

Thx!!

Question,. I'm getting one card color as dark orange sometimes on the end.. almost red.. says 605?    .. what is this?

[ripcurrent]

I was wondering what might be the reason for low amount of "+" for a gpu . Its seems like I do not get very many submitted shares. I have a 6 gpu rig running smooth about 690 sols per card  , no overclock ....any thoughts?