Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 14. (Read 224621 times)
May 11, 2018, 10:47:07 AM
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
May 11, 2018, 06:30:12 AM
I had a crash this morning on Linux with DSTM Miner v0.6:
*** stack smashing detected ***: ./zmminer terminated
*** 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.
Only other option is a loose/malfunctioning riser, I suppose.
I think you set too low power
May 10, 2018, 11:21:20 AM
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. You can't download the latest version 0.7 because they do not exist : we are at 0.6 version.
May 10, 2018, 09:03:18 AM
Hello. Why I can't download the latest version 0.7 from drive.google? It says me there is a virus:
Hello,Quote
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
Only the owner is allowed to download infected files.
You can't download the latest version 0.7 because they do not exist : we are at 0.6 version.
May 10, 2018, 07:28:36 AM
Hello. Why I can't download the latest version 0.7 from drive.google? It says me there is a virus:
Quote
Sorry, this file is infected with a virus
Only the owner is allowed to download infected files.
Only the owner is allowed to download infected files.
May 10, 2018, 12:48:42 AM
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
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
May 09, 2018, 10:50:41 PM
I had a crash this morning on Linux with DSTM Miner v0.6:
*** stack smashing detected ***: ./zmminer terminated
*** 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.
Only other option is a loose/malfunctioning riser, I suppose.
May 09, 2018, 02:37:00 PM
On v.7 will some improvements? May be GDDR5X optimisation?
May 08, 2018, 05:56:13 PM
I think you should release 0.7 and then wait for the "asic" outcome to add the ne algos maybe.
May 07, 2018, 03:27:43 PM
I had a crash this morning on Linux with DSTM Miner v0.6:
*** stack smashing detected ***: ./zmminer terminated
*** 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)
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
May 07, 2018, 05:48:46 AM
Hi,
I am using SMOS and DSTM v0.6. I am trying to connect to suprnova.cc pool but understand how to connect. The string line command is losing me.
stratum+tcp://zen.suprnova.cc:3618
Here is the command lint that SMOS has for dstm but different pool. How do I change it make it work. With Suprnova.cc command line?
--server europe.equihash-hub.miningpoolhub.com --port 20570 --user youraccount.$rigName --pass x
I am using SMOS and DSTM v0.6. I am trying to connect to suprnova.cc pool but understand how to connect. The string line command is losing me.
stratum+tcp://zen.suprnova.cc:3618
Here is the command lint that SMOS has for dstm but different pool. How do I change it make it work. With Suprnova.cc command line?
--server europe.equihash-hub.miningpoolhub.com --port 20570 --user youraccount.$rigName --pass x
Looks ok. Have you added your workers?
May 07, 2018, 04:28:25 AM
Hi,
I am using SMOS and DSTM v0.6. I am trying to connect to suprnova.cc pool but understand how to connect. The string line command is losing me.
stratum+tcp://zen.suprnova.cc:3618
Here is the command lint that SMOS has for dstm but different pool. How do I change it make it work. With Suprnova.cc command line?
--server europe.equihash-hub.miningpoolhub.com --port 20570 --user youraccount.$rigName --pass x
I am using SMOS and DSTM v0.6. I am trying to connect to suprnova.cc pool but understand how to connect. The string line command is losing me.
stratum+tcp://zen.suprnova.cc:3618
Here is the command lint that SMOS has for dstm but different pool. How do I change it make it work. With Suprnova.cc command line?
--server europe.equihash-hub.miningpoolhub.com --port 20570 --user youraccount.$rigName --pass x
May 07, 2018, 03:26:27 AM
Some pools require to set the coin you want to mine. With ccminer, you can use -p as an option, for example:
How can I set this with your miner?
Code:
-p C=KMD
How can I set this with your miner?
May 06, 2018, 05:44:45 AM
May 05, 2018, 12:14:38 AM
Hey DSTM, just PMed you in regards to some upgrades that I thought I may be able to contribute to your miner. Thanks for all the work.
@DSTM - I've seen ragefarms functionality and it is pretty awesome. Instant upgrade for you miner and simplifies a lot of the things folks are talking about on this thread
OC, TDP, Fan, etc
May 04, 2018, 02:20:31 PM
May 04, 2018, 12:50:02 PM
When V0.7 ?
May 04, 2018, 12:30:16 PM
For people with NVIDIA cards specially those with GTX 1070 Ti.
Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??
I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.
Thanks everyone
Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??
I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.
Thanks everyone
yes I have, and its about the same, wasnt really that big of a downfall one the driver before that tho at least not enough to make me rollback a GPU driver, I use Kernel Mode, 91% TPD, +184/+852 on mine, i get around 538-540ish with my 1070 ti, u can take it atw up to 1000 at the TPD you're at tho lol i'd turn it up to 94-106% if i were u tho
No thanks
I can get the same performance you get with 80% TDP/ +200 clock/ +700 mem that is 530-535 sols/s ish using far less elecricity than what you are using. It actually seems you are wasting it so I assume you do not pay for it. I do not know what brand you are using but mines are EVGA and MSI and they do not like more than +750 mem. Combined clock and mem they do not like more than +220 clock/+730 mem otherwise they crash (at least that is my experience)
There is also a compromise between what you get from the cards, the electricity you pay and the life expectancy of the equipment and I would say with your settings last one is not going to be long enough to make profit out of them.
You will not get the same hash rate, and you are right I do not pay for Power, however if I did i'd still want the most hashrate I can get, life expectancy of cards is also irrelevant to me, and turning it down to you're level wont help that cause any if at all, to each their own I guess, I'd just rather have better hash rates, I also wouldnt rollback a driver lol for a few hashes, but from the looks of it, since the Zcash Founder is a complete and utter Moron, we'll be hunting for a new coin to mine shortly.
May 03, 2018, 12:58:41 PM
For people with NVIDIA cards specially those with GTX 1070 Ti.
Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??
I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.
Thanks everyone
Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??
I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.
Thanks everyone
yes I have, and its about the same, wasnt really that big of a downfall one the driver before that tho at least not enough to make me rollback a GPU driver, I use Kernel Mode, 91% TPD, +184/+852 on mine, i get around 538-540ish with my 1070 ti, u can take it atw up to 1000 at the TPD you're at tho lol i'd turn it up to 94-106% if i were u tho
No thanks
I can get the same performance you get with 80% TDP/ +200 clock/ +700 mem that is 530-535 sols/s ish using far less elecricity than what you are using. It actually seems you are wasting it so I assume you do not pay for it. I do not know what brand you are using but mines are EVGA and MSI and they do not like more than +750 mem. Combined clock and mem they do not like more than +220 clock/+730 mem otherwise they crash (at least that is my experience)
There is also a compromise between what you get from the cards, the electricity you pay and the life expectancy of the equipment and I would say with your settings last one is not going to be long enough to make profit out of them.
May 03, 2018, 12:15:28 PM
For people with NVIDIA cards specially those with GTX 1070 Ti.
Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??
I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.
Thanks everyone
Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??
I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.
Thanks everyone
yes I have, and its about the same, wasnt really that big of a downfall one the driver before that tho at least not enough to make me rollback a GPU driver, I use Kernel Mode, 91% TPD, +184/+852 on mine, i get around 538-540ish with my 1070 ti, u can take it atw up to 1000 at the TPD you're at tho lol i'd turn it up to 94-106% if i were u tho
Jump to: