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

[dstm]

I'm not sure if this information is accessible through nvidia's official APIs.

It would be very usefull, with at least the brand name : GPU-Z manages to display brands.

Probably it uses it's own database to do so.

[1714147895]

1714147895

[1714147895]

1714147895

[1714147895]

1714147895

[1714147895]

1714147895

[1714147895]

1714147895

[1714147895]

1714147895

[sPzAbt]

I'm not sure if this information is accessible through nvidia's official APIs.

It would be very usefull, with at least the brand name : GPU-Z manages to display brands.

Probably it uses it's own database to do so.

ccminer can also display the vendor names

maybe this link is helpful:

http://docs.nvidia.com/gameworks/content/gameworkslibrary/coresdk/nvapi/structNV__CHIPSET__INFO__v2.html

NV_CHIPSET_INFO_v2::szVendorName or NvU32 NV_CHIPSET_INFO_v2::vendorId ?

i would also really appreciate if you coud add vendor info - would be helpfull in mixed setups

[The_Immortal]

dstm, thank you.

And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.

Could you tell me please why is that? ZM cannot properly work with proxy under Linux?

No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.

Code:

zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x

192.168.32.119 - proxy-server
7777 - port which is mapped to eu1-zcash.flypool.org:3333

Well, should I open the port 3443 on proxy-server as well? And where should I map it then?

eu1-zcash.flypool.org:3443

Well, I set mapping local tcp port 3443 to eu1-zcash.flypool.org:3443 on proxy-server - the same result: Connection refused

Code:

#  GPU0 connected to: 192.168.32.119:7777
connect: Connection refused

Again, linux EWBF works properly with the same settings:

Code:

+-------------------------------------------------+
|         EWBF's Zcash CUDA miner. 0.3.4b         |
+-------------------------------------------------+
INFO: Used config file: miner.cfg
INFO: Current pool: 192.168.32.119:7777
INFO: Selected pools: 1
INFO: Solver: Auto.
INFO: Devices: All.
INFO: Temperature limit: 82
INFO: Api: Listen on 127.0.0.1:42000
---------------------------------------------------
INFO: Target: 0004189374bc6a7e...
INFO: Detected new work: 0687cb34a03daf960acb

How can I get what is the problem?

[dstm]

dstm, thank you.

And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.

Could you tell me please why is that? ZM cannot properly work with proxy under Linux?

No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.

Code:

zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x

192.168.32.119 - proxy-server
7777 - port which is mapped to eu1-zcash.flypool.org:3333

Well, should I open the port 3443 on proxy-server as well? And where should I map it then?

eu1-zcash.flypool.org:3443

Well, I set mapping local tcp port 3443 to eu1-zcash.flypool.org:3443 on proxy-server - the same result: Connection refused

Code:

#  GPU0 connected to: 192.168.32.119:7777
connect: Connection refused

Again, under Windows with the same config there is no problem with connection...
And again, linux EWBF works properly with such settings.

How can I get what is the problem?

Sry, I forgot to mention you have to do some more configuration.                                                               
I'll think about a better solution later.

This might be helpful.
https://bitcointalk.org/index.php?topic=2021765.msg23213269#msg23213269

[The_Immortal]

dstm, thank you.

And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.

Could you tell me please why is that? ZM cannot properly work with proxy under Linux?

No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.

Code:

zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x

192.168.32.119 - proxy-server
7777 - port which is mapped to eu1-zcash.flypool.org:3333

Well, should I open the port 3443 on proxy-server as well? And where should I map it then?

eu1-zcash.flypool.org:3443

Well, I set mapping local tcp port 3443 to eu1-zcash.flypool.org:3443 on proxy-server - the same result: Connection refused

Code:

#  GPU0 connected to: 192.168.32.119:7777
connect: Connection refused

Again, under Windows with the same config there is no problem with connection...
And again, linux EWBF works properly with such settings.

How can I get what is the problem?

Sry, I forgot to mention you have to do some more configuration.                                                              
I'll think about a better solution later.

This might be helpful.
https://bitcointalk.org/index.php?topic=2021765.msg23213269#msg23213269

Well, I see the solution:

I've managed to solve it easily by additionally remapping local port AND pool hostname (3proxy+edited windows hosts file, in my case)

But have no idea how to do it... Need an example

It seems you've hardcoded pool addresses for devfee, so they don't actually went through proxy even if I forward the right port (3443 in my case).

Could you please simplify your code just to use an ordinary port forwarding?
The problem is all my rigs can connect only via proxy-server

[dstm]

dstm, thank you.

And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.

Could you tell me please why is that? ZM cannot properly work with proxy under Linux?

No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.

Code:

zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x

192.168.32.119 - proxy-server
7777 - port which is mapped to eu1-zcash.flypool.org:3333

Well, should I open the port 3443 on proxy-server as well? And where should I map it then?

eu1-zcash.flypool.org:3443

Well, I set mapping local tcp port 3443 to eu1-zcash.flypool.org:3443 on proxy-server - the same result: Connection refused

Code:

#  GPU0 connected to: 192.168.32.119:7777
connect: Connection refused

Again, under Windows with the same config there is no problem with connection...
And again, linux EWBF works properly with such settings.

How can I get what is the problem?

Sry, I forgot to mention you have to do some more configuration.                                                              
I'll think about a better solution later.

This might be helpful.
https://bitcointalk.org/index.php?topic=2021765.msg23213269#msg23213269

Well, I see the solution:

I've managed to solve it easily by additionally remapping local port AND pool hostname (3proxy+edited windows hosts file, in my case)

But have no idea how to do it... Need an example

It seems you've hardcoded pool addresses for devfee, so they don't actually went through proxy even if I forward the right port (3443 in my case).

Could you please simplify your code just to use an ordinary port forwarding?
The problem is all my rigs can connect only via proxy-server

I see. There is currently no better solution, it's on my todo list.

[The_Immortal]

dstm, thank you.

And there is one thing. I had issues on version 0.5.2 (Linux) by connecting ZM via proxy - it showed "Connection refused". I tried to do the same on Windows - everything is ok. And of course I've tested EWFB version on Linux too - no problem as well.

Could you tell me please why is that? ZM cannot properly work with proxy under Linux?

No, there are no issues with proxies on linux, some people use zm with proxies.
How do you setup your proxy?
Are you blocking ports? ZM requires port 3443 to be open to be able to submit it's dev fee shares, it won't work if it's not able to do so.

Code:

zm --server 192.168.32.119 --port 7777 --user my_wallet.worker_name --pass x

192.168.32.119 - proxy-server
7777 - port which is mapped to eu1-zcash.flypool.org:3333

Well, should I open the port 3443 on proxy-server as well? And where should I map it then?

eu1-zcash.flypool.org:3443

Well, I set mapping local tcp port 3443 to eu1-zcash.flypool.org:3443 on proxy-server - the same result: Connection refused

Code:

#  GPU0 connected to: 192.168.32.119:7777
connect: Connection refused

Again, under Windows with the same config there is no problem with connection...
And again, linux EWBF works properly with such settings.

How can I get what is the problem?

Sry, I forgot to mention you have to do some more configuration.                                                              
I'll think about a better solution later.

This might be helpful.
https://bitcointalk.org/index.php?topic=2021765.msg23213269#msg23213269

Well, I see the solution:

I've managed to solve it easily by additionally remapping local port AND pool hostname (3proxy+edited windows hosts file, in my case)

But have no idea how to do it... Need an example

It seems you've hardcoded pool addresses for devfee, so they don't actually went through proxy even if I forward the right port (3443 in my case).

Could you please simplify your code just to use an ordinary port forwarding?
The problem is all my rigs can connect only via proxy-server

I see. There is currently no better solution, it's on my todo list.

But could you tell me please what should I put into Windows hosts file then? Something like that:

Code:

localhost:3443        eu1-zcash.flypool.org

?

It hasn't changed anything tho...

[dstm]

But could you tell me please what should I put into Windows hosts file then? Something like that:

Code:

localhost:3443        eu1-zcash.flypool.org

?

It hasn't changed anything tho...

You have somehow to redirect eu1-zcash.flypool.org:3443 to your proxy. However I can't lookup the details for you, sry.

[The_Immortal]

But could you tell me please what should I put into Windows hosts file then? Something like that:

Code:

localhost:3443        eu1-zcash.flypool.org

?

It hasn't changed anything tho...

You have somehow to redirect eu1-zcash.flypool.org:3443 to your proxy.

On client (Linux) side you mean?

[dstm]

But could you tell me please what should I put into Windows hosts file then? Something like that:

Code:

localhost:3443        eu1-zcash.flypool.org

?

It hasn't changed anything tho...

You have somehow to redirect eu1-zcash.flypool.org:3443 to your proxy.

On client (Linux) side you mean?

Yes, on the host zm is running on.

[ZenFr]

Heelo DSTM,
When will be the next release (Linux/Ubuntu users) ?
Any improve/upgrade for the hashrate ?
Any specifics news about BTC Gold mining and DSTM equihash miner ?
Thanks :-).

[santan]

I know dstm, you are heavily loaded now with tons of things to fix ... and feature requests from users.... However regarding the info of Bitcoin Gold...
Here is what BTG Guys says about it.......

Code:

"The change of the protocol that is introduced in BTG. The first 4 bytes of the reserved header field from zcash blockformat are actually the block height. Currently the protocol is being tested."

So just to be sure.... do you think this change in reserved header.... is going to be break anything in your code... or should be fine with mining using zm.

[dstm]

Heelo DSTM,
When will be the next release (Linux/Ubuntu users) ?
Any improve/upgrade for the hashrate ?
Any specifics news about BTC Gold mining and DSTM equihash miner ?
Thanks :-).

Likely this weekend.
I'm currently working on cpu side.
There is no specification available for it as far as I know.

[dstm]

I know dstm, you are heavily loaded now with tons of things to fix ... and feature requests from users.... However regarding the info of Bitcoin Gold...
Here is what BTG Guys says about it.......

Code:

"The change of the protocol that is introduced in BTG. The first 4 bytes of the reserved header field from zcash blockformat are actually the block height. Currently the protocol is being tested."

So just to be sure.... do you think this change in reserved header.... is going to be break anything in your code... or should be fine with mining using zm.

this one should be fine

[mirny]

Hi dstm,
can I use failover pools somehow?
cheers

[Plumbus]

Is there a way to exit immediately if connection to the pool is lost?

Currently not, I'll add an option to disable reconnection.

Was this added to the newest version?

[auto_miner_01]

Hey dstm,

thx for the new version 0.5.3.

I am testing it at the moment on my testing rig and there seems to be a bug with the new latency messurement:

Code:

Oct 31 07:32:05 PM|#  telemetry server started
Oct 31 07:32:05 PM|#  GPU0 connected to: zen.suprnova.cc:3618
Oct 31 07:32:07 PM|#  GPU0 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
Oct 31 07:32:27 PM|>  GPU0 50C  Sol/s: 293.8  Sol/W: 3.23  Avg: 293.8  I/s: 156.7  Sh: 6.00  1.00 2077252204 ++
Oct 31 07:32:47 PM|   GPU0 50C  Sol/s: 290.2  Sol/W: 3.24  Avg: 292.0  I/s: 155.0  Sh: 7.50  1.00 3074318 +++
Oct 31 07:33:07 PM|   GPU0 51C  Sol/s: 288.3  Sol/W: 3.22  Avg: 290.8  I/s: 154.9  Sh: 5.00  1.00 3074318
Oct 31 07:33:27 PM|   GPU0 51C  Sol/s: 295.3  Sol/W: 3.24  Avg: 291.9  I/s: 154.9  Sh: 3.75  1.00 3074318
Oct 31 07:33:47 PM|   GPU0 51C  Sol/s: 283.5  Sol/W: 3.22  Avg: 290.2  I/s: 154.9  Sh: 3.60  1.00 -140462746 +

Looks like some kind of buffer overflow to me, but i am no expert.

Any idear what could cause this?

Greetings
AM01

[dstm]

Hi dstm,
can I use failover pools somehow?
cheers

No, there is no support for it currently.

[dstm]

Is there a way to exit immediately if connection to the pool is lost?

Currently not, I'll add an option to disable reconnection.

Was this added to the newest version?

I've released 0.5.3 earlier than planned because of cpu load reduction - so it doesn't contain this.

[dstm]

Hey dstm,

thx for the new version 0.5.3.

I am testing it at the moment on my testing rig and there seems to be a bug with the new latency messurement:

Code:

Oct 31 07:32:05 PM|#  telemetry server started
Oct 31 07:32:05 PM|#  GPU0 connected to: zen.suprnova.cc:3618
Oct 31 07:32:07 PM|#  GPU0 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
Oct 31 07:32:27 PM|>  GPU0 50C  Sol/s: 293.8  Sol/W: 3.23  Avg: 293.8  I/s: 156.7  Sh: 6.00  1.00 2077252204 ++
Oct 31 07:32:47 PM|   GPU0 50C  Sol/s: 290.2  Sol/W: 3.24  Avg: 292.0  I/s: 155.0  Sh: 7.50  1.00 3074318 +++
Oct 31 07:33:07 PM|   GPU0 51C  Sol/s: 288.3  Sol/W: 3.22  Avg: 290.8  I/s: 154.9  Sh: 5.00  1.00 3074318
Oct 31 07:33:27 PM|   GPU0 51C  Sol/s: 295.3  Sol/W: 3.24  Avg: 291.9  I/s: 154.9  Sh: 3.75  1.00 3074318
Oct 31 07:33:47 PM|   GPU0 51C  Sol/s: 283.5  Sol/W: 3.22  Avg: 290.2  I/s: 154.9  Sh: 3.60  1.00 -140462746 +

Looks like some kind of buffer overflow to me, but i am no expert.

Any idear what could cause this?

Greetings
AM01

Thx for reporting.
Does this always happen on your system? On every pool? Are you using ntp?