Bitcoin Forum
May 23, 2018, 03:54:41 PM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 [37] 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 ... 163 »
  Print  
Author Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.1 (Linux / Windows)  (Read 205234 times)
chancefx
Member
**
Offline Offline

Activity: 142
Merit: 10

In Decentralization We Trust


View Profile
October 24, 2017, 03:59:27 PM
 #721



help me

https://www.microsoft.com/en-us/download/details.aspx?id=52685

1527090881
Hero Member
*
Offline Offline

Posts: 1527090881

View Profile Personal Message (Offline)

Ignore
1527090881
Reply with quote  #2

1527090881
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
SpecialX
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
October 24, 2017, 04:14:22 PM
 #722

--telemetry=0.0.0.0:42000

It can not work
crazydane
Full Member
***
Offline Offline

Activity: 308
Merit: 149



View Profile
October 24, 2017, 04:22:38 PM
 #723

Right, use the actual IP of the miner.
chancefx
Member
**
Offline Offline

Activity: 142
Merit: 10

In Decentralization We Trust


View Profile
October 24, 2017, 04:23:10 PM
 #724

--telemetry=0.0.0.0:42000

It can not work


you need to edit 0.0.0.0 to you local rig address

SpecialX
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
October 24, 2017, 04:38:05 PM
 #725

http://upimg.org/image.php?di=AO3R
ypsi
Full Member
***
Offline Offline

Activity: 322
Merit: 158


The Wheel weaves as the Wheel wills


View Profile
October 24, 2017, 05:04:37 PM
 #726

[-img]http://upimg.org/image.php?di=AO3R[/img]
Did you put that address in the telemetry command line? If you did then you need to check your FW.

--ypsi

UrsaUrsa
Member
**
Offline Offline

Activity: 103
Merit: 10


View Profile
October 24, 2017, 05:34:46 PM
 #727

Hi.

Tried out your miner. It is, in fact, about 10% faster than EWBF. However, it has a nasty bug that forced me to go back to EWBF.

I mine ZEC on nanopool, recently they've had some service disruptions. So, if pool drops connection, EWBF simply tries to reconnect and succeeds finally, while dstm's ZM miner goes into "0 connection closed by server - reconnecting..." infinite loop, scrolling text very fast and never actually resumes mining.

Using Linux version under Ubuntu 16.04 LTS.

Thanks!

Hi,

I got the same problem with suprnova pool. I am using 0.5.2 on windows.
Infinite loop.

I just looked if I can had a list of pools but it seems impossible...

Could you pls post the suprnava server and port you're using, I'll test the current dev branch against it.

The one time my miner had disconnected it was the same and zm did not reconnect.
B00gieman
Jr. Member
*
Offline Offline

Activity: 47
Merit: 0


View Profile
October 24, 2017, 05:38:58 PM
 #728

Hello.
Tested on 8x Gigabyte NVIDIA 1700 rig on W64.
Connected to Flypool.

460/470 sol's
1100w PowerDraw

Keep testing and waiting for BTG  Wink

promomei
Sr. Member
****
Offline Offline

Activity: 376
Merit: 252



View Profile
October 24, 2017, 06:24:38 PM
 #729

make video set it up on youtube XD
will be nice  Grin

Ill try it later with my 1060 farm-let you know guys

sp_
Legendary
*
Offline Offline

Activity: 1414
Merit: 1035

Ccminer developer


View Profile
October 24, 2017, 06:30:27 PM
 #730

Did a test with 60 workers. Unstable at first, but then I added a simple failover script and it seems to work..


balkeep
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
October 24, 2017, 06:40:40 PM
 #731

Hi.

Tried out your miner. It is, in fact, about 10% faster than EWBF. However, it has a nasty bug that forced me to go back to EWBF.

I mine ZEC on nanopool, recently they've had some service disruptions. So, if pool drops connection, EWBF simply tries to reconnect and succeeds finally, while dstm's ZM miner goes into "0 connection closed by server - reconnecting..." infinite loop, scrolling text very fast and never actually resumes mining.

Using Linux version under Ubuntu 16.04 LTS.

Thanks!

Hi,

I got the same problem with suprnova pool. I am using 0.5.2 on windows.
Infinite loop.

I just looked if I can had a list of pools but it seems impossible...

Yep, having the same problem with suprnova and ZEN on win10 ltsb x64 and 0.5.2 version. Have to restart manually, but when I do it reconnects instantly.

zm --server zen.suprnova.cc --port 3618 --user balkeep.Stacey --pass XXXX --telemetry=192.168.1.10:42000
UrsaUrsa
Member
**
Offline Offline

Activity: 103
Merit: 10


View Profile
October 24, 2017, 06:55:36 PM
 #732

Did a test with 60 workers. Unstable at first, but then I added a simple failover script and it seems to work..



I assume your workers are running Linux?
sp_
Legendary
*
Offline Offline

Activity: 1414
Merit: 1035

Ccminer developer


View Profile
October 24, 2017, 07:03:13 PM
 #733

I assume your workers are running Linux?

No

The test is conducted with the Version 0.5.2 exe file
dstm
Full Member
***
Offline Offline

Activity: 308
Merit: 119


View Profile
October 24, 2017, 07:08:04 PM
 #734

is there any --log command? don't find on first page

There is currently no logfile support. I'll ad it in one of the next releases.
dstm
Full Member
***
Offline Offline

Activity: 308
Merit: 119


View Profile
October 24, 2017, 07:08:40 PM
 #735

Did a test with 60 workers. Unstable at first, but then I added a simple failover script and it seems to work..




What's failing?
sp_
Legendary
*
Offline Offline

Activity: 1414
Merit: 1035

Ccminer developer


View Profile
October 24, 2017, 07:25:36 PM
 #736

if you implement a accepted share count, and a rejected share count like other miners, it's easier to see wich of the workers that's just been restarted. Easier to troubleshoot
When a worker is restarted I loose hashrate.
dstm
Full Member
***
Offline Offline

Activity: 308
Merit: 119


View Profile
October 24, 2017, 07:53:19 PM
 #737

if you implement a accepted share count, and a rejected share count like other miners, it's easier to see wich of the workers that's just been restarted. Easier to troubleshoot

It's there, it's accessible via json-rpc or webui.
How do you monitor your workers? For large worker counts people usually use json-rpc.
Json-rpc will contain uptime and connection-time in the next release which is useful in this kind of situations.
If it's useful I'll output a/r shares also on terminal.

Quote
When a worker is restarted I loose hashrate.
Not sure if I understand this correctly. Do the GPUs perform slower after a restart?
PL84
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
October 24, 2017, 08:06:40 PM
 #738

@dstm

I sent message you about implementing your miner to EthOS. Have a look and reply if you are interested about it.
NameTaken
Hero Member
*****
Offline Offline

Activity: 630
Merit: 502


View Profile
October 25, 2017, 05:04:24 AM
 #739

Hi.

Tried out your miner. It is, in fact, about 10% faster than EWBF. However, it has a nasty bug that forced me to go back to EWBF.

I mine ZEC on nanopool, recently they've had some service disruptions. So, if pool drops connection, EWBF simply tries to reconnect and succeeds finally, while dstm's ZM miner goes into "0 connection closed by server - reconnecting..." infinite loop, scrolling text very fast and never actually resumes mining.

Using Linux version under Ubuntu 16.04 LTS.

Thanks!

Thx for reporting, this is a know bug, NameTaken had similar issues.
It will be fixed in the next release - this path is unlikely to hit, zm 0.5.2 should reconnect properly in almost all cases.
Woke up today to find all my rigs had stopped working due to this.
patinencomun
Jr. Member
*
Offline Offline

Activity: 43
Merit: 0


View Profile
October 25, 2017, 05:40:46 AM
 #740

Hi dstm's developer,

I found a "bug", if telemetry fails at boot, for example when a power lose / power restore situation occurs, the miner won't start. System reboots on power fails, and miner start on boot, but for the router is not started yet...

Could you fix this?
Thank you.

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 [37] 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 ... 163 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!