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

im getting teh "zm.exe is not responding" error too, wonder if its my 1080ti settings of 150+ core too high?

Hahah 300/1000 hahah... try 0/0, "see the Light"...

Good question, I've been asking myself that too.
Meantime, I found an android app to monitor my rigs via MPH pool.

Nope, recv failed: 10054 is a socket error. Please fix this issues, it seems that your miner is very good on the hashrate but need some fix on network side.

What API?
What exports this API function?

Hi,
Is there a way to get the device name from API? I can see the device name while accessing the miner with a web browser, but it is not included if I perform a API call.

Thank you.

anyone having issues with good sol rates, but poor submitted shares? 

>  GPU0  55C  Sol/s: 500.0  Sol/W: 2.85  Avg: 464.7  I/s: 262.1  Sh: 1.33   1.00 469
>  GPU1  54C  Sol/s: 495.7  Sol/W: 2.95  Avg: 462.0  I/s: 259.6  Sh: 1.33   1.00 469 +
>  GPU2  57C  Sol/s: 489.2  Sol/W: 2.88  Avg: 466.1  I/s: 264.8  Sh: 0.67   1.00 469
>  GPU3  55C  Sol/s: 493.3  Sol/W: 2.89  Avg: 467.4  I/s: 263.9  Sh: 2.00   1.00 463 +
   ========== Sol/s: 1978.3 Sol/W: 2.89  Avg: 1860.2 I/s: 1050.4 Sh: 5.32   1.00 467
   GPU0  54C  Sol/s: 492.7  Sol/W: 2.87  Avg: 467.5  I/s: 263.5  Sh: 1.20   1.00 469
   GPU1  53C  Sol/s: 492.2  Sol/W: 2.96  Avg: 465.0  I/s: 259.7  Sh: 1.49   1.00 470 +
   GPU2  56C  Sol/s: 493.6  Sol/W: 2.91  Avg: 468.8  I/s: 265.0  Sh: 0.90   1.00 588 +
   GPU3  54C  Sol/s: 511.1  Sol/W: 2.92  Avg: 471.8  I/s: 264.0  Sh: 2.10   1.00 468 +
   ========== Sol/s: 1989.6 Sol/W: 2.92  Avg: 1873.2 I/s: 1052.1 Sh: 5.69   1.00 498
   GPU0  53C  Sol/s: 489.1  Sol/W: 2.89  Avg: 469.5  I/s: 258.5  Sh: 1.36   1.00 465 +
   GPU1  52C  Sol/s: 485.6  Sol/W: 2.97  Avg: 466.9  I/s: 259.7  Sh: 1.36   1.00 470
   GPU2  55C  Sol/s: 497.2  Sol/W: 2.92  Avg: 471.4  I/s: 265.0  Sh: 0.82   1.00 588
   GPU3  54C  Sol/s: 492.3  Sol/W: 2.93  Avg: 473.7  I/s: 264.1  Sh: 1.91   1.00 468
   ========== Sol/s: 1964.1 Sol/W: 2.93  Avg: 1881.4 I/s: 1047.2 Sh: 5.44   1.00 497
>  GPU0  53C  Sol/s: 473.2  Sol/W: 2.90  Avg: 469.8  I/s: 255.9  Sh: 1.25   1.00 465
>  GPU1  52C  Sol/s: 492.0  Sol/W: 2.98  Avg: 469.0  I/s: 259.8  Sh: 1.25   1.00 470
>  GPU2  55C  Sol/s: 495.1  Sol/W: 2.94  Avg: 473.4  I/s: 264.9  Sh: 0.75   1.00 588
>  GPU3  54C  Sol/s: 491.7  Sol/W: 2.94  Avg: 475.2  I/s: 264.2  Sh: 1.75   1.00 468


four Asus Strix GTX 1070 8GB OC (300, 1000).  Linux Ubuntu 16.04. 

I've noticed that when too many recons happen then my mining client crashes. right now ive been mining 18hrs with only one reconnection and the rigs are running flawlessly. It's obviously an issue with maintaining a connection to the mining pool. Hopefully that gets sorted out soon enough. I've had this issue on 0.5.7 and 0.5.8 so rolling back to the previous version makes no difference. Right now I'll work on integrating this free open source watchdog script (https://bitcointalksearch.org/topic/cmd-farmwatchbot-ewbf-claymore-bminer-dstm-cc-eth-castxmr-phoenix-2071108) that will reboot the mining client on crash and reboot my rigs on regular intervals just to manage the issue until the pool and client are working well together again.

I have the same problem on v0.5.8. Miner works for a day, and suddenly goes "zm.exe is not responding". At this point I must manually restart the Miner. This never happend to me on v0.5.7.

the same issue, I get disconnected every 5 minutes with eu-ru01.miningrigrentals.com
but without disconnections to zec-eu1.nanopool.org
it is a pity, can't use with so many disconnections
Can it be an issue with low capacity of RAM? I have only 2gb Ram on my PC. Lan network.

see README.txt file & you want to switch from EWBF because gain more speed & more hpower to try use this:


there are other option to combine with this miner app but way not keep thing simple

cheers

any monitoring http protocol or soft for this?
I'm struggling with ewbf + it has no more updates, would like to switch to another one with centralized monitoring

Howsit, thanks for your reply it was meaninful and helpful.
I missed the " --dev            Space separated list of cuda devices" in the readme.txt

Thanks.

Dear dstm,

When you write in your Change log:
"con: add support for protocol v.01000020"

What does the "con" mean ?
Do you use any other mysterious abbreviations ?

Also what protocol  v01000020 are you referring to?

for select what gpu you want to use > --dev number < is what you need to add in command line, if you was read README.txt is there
- first run zm --list-devices to see how gpu are listed then
- aka if you want to use gpu 1 2 3 then: --dev 0 1 2 you need to use or a combo like that see first step

cheers

https://en.wikipedia.org/wiki/RTFM

how to mine with ZM using only xyz GPU card?

If u have 5 GUPS and only want to use GPU 1-3

what is the syntax / command for this , please?

Hy there, new to this mining thing. Playing with my gaming pc and w8ing for my first rig. This is what i get with GTX960 4GB:
https://i.imgur.com/4auVx62.jpg
What do you think, can i get better?
In pool i get ±170 avg. and power consumption from wall ~130w
Working for 12h+ now, no crashes or any turn off's

I have this exact same issue, every 3hrs my rigs get disconnected and reconnect for 5min before they start mining again. Internet is not the problem btw and the rigs dont have anti-virus or firewalls up.