Pages:
Author

Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 14. (Read 225062 times)

full member
Activity: 226
Merit: 100
I think you should release 0.7 and then wait for the "asic" outcome to add the ne algos maybe.
jr. member
Activity: 95
Merit: 2
I had a crash this morning on Linux with DSTM Miner v0.6:

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

 Huh


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
newbie
Activity: 8
Merit: 0
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

Looks ok. Have you added your workers?
member
Activity: 141
Merit: 10
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
newbie
Activity: 8
Merit: 0
Some pools require to set the coin you want to mine. With ccminer, you can use -p as an option, for example:

Code:
-p C=KMD

How can I set this with your miner?
newbie
Activity: 31
Merit: 0
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
jr. member
Activity: 62
Merit: 1
newbie
Activity: 22
Merit: 2
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




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 Grin

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.
jr. member
Activity: 108
Merit: 7
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




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 Grin

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.

newbie
Activity: 22
Merit: 2
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




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 Grin
newbie
Activity: 22
Merit: 2
How about a "Shutdown script" of some sort so that if it overheats for any reason, internet lags out for any reason for failover etc.., one that we can configure to for instance, restart the miner in 5mins or 8mins once network has become reconnected and or load an app like Afterburner, the computer restart idea is actually pretty good, just put an option for ppl if they dont wanna use it then they dont add the flag for it?
jr. member
Activity: 108
Merit: 7
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

newbie
Activity: 3
Merit: 0
Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

Yes ofc.

2% of the running time are used to calculate solutions for the dev shares.
The amount of submitted shares depends on the difficulty, which is set by the server.
So your example '2% could be 2 shares in 100 accepted shares?' is right for the case where the difficulty of 'your shares' is equal to the difficulty of the 'dev shares'.


Thanks for your reply... but I have another question, how could a difficulty of the 'dev shares' differ from the difficulty of 'my shares'?
From what I know and you also mentioned that the difficulty is set by the pool server. and only smallest hashes/Sols (which can possibly be accepted) are submitted to the server to lower the bandwidth of the network.

So when you're mining using ZM, You mine whatever Crypto you want that uses Equihash to resolve.  When the DevFee kicks in, it selects a specific server and difficulty to mine the dev fee (Which May or May not be what you are mining.)  Hope this helps

-Thanks DSTM for the Miner/Your effort

Yes, it does! Thanks!
newbie
Activity: 1
Merit: 0
Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

Yes ofc.

2% of the running time are used to calculate solutions for the dev shares.
The amount of submitted shares depends on the difficulty, which is set by the server.
So your example '2% could be 2 shares in 100 accepted shares?' is right for the case where the difficulty of 'your shares' is equal to the difficulty of the 'dev shares'.


Thanks for your reply... but I have another question, how could a difficulty of the 'dev shares' differ from the difficulty of 'my shares'?
From what I know and you also mentioned that the difficulty is set by the pool server. and only smallest hashes/Sols (which can possibly be accepted) are submitted to the server to lower the bandwidth of the network.

So when you're mining using ZM, You mine whatever Crypto you want that uses Equihash to resolve.  When the DevFee kicks in, it selects a specific server and difficulty to mine the dev fee (Which May or May not be what you are mining.)  Hope this helps

-Thanks DSTM for the Miner/Your effort
newbie
Activity: 3
Merit: 0
Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

Yes ofc.

2% of the running time are used to calculate solutions for the dev shares.
The amount of submitted shares depends on the difficulty, which is set by the server.
So your example '2% could be 2 shares in 100 accepted shares?' is right for the case where the difficulty of 'your shares' is equal to the difficulty of the 'dev shares'.


Thanks for your reply... but I have another question, how could a difficulty of the 'dev shares' differ from the difficulty of 'my shares'?
From what I know and you also mentioned that the difficulty is set by the pool server. and only smallest hashes/Sols (which can possibly be accepted) are submitted to the server to lower the bandwidth of the network.
newbie
Activity: 13
Merit: 0
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.
newbie
Activity: 1
Merit: 0
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.
newbie
Activity: 8
Merit: 0
I tried the --temp-target flag the other day and it seems like the miner just ignores it.  Temps stayed far above the limit.  Running ethOS 1.3.1 and dstm 0.6.0.1.  Any clues?  Thx

Pages:
Jump to: