chose any available and put --algo sha512256d into extra parameters.

WildRig Multi 0.32.3

- implemented sha512256d
- better intensity parameters for ghostrider

WildRig Multi 0.32.4

- improved sha512256d up to 12% on AMD and 2% on NVIDIA

As far as working on NH I don't think any of the antminers work well there my V9's wont hardly hash on that pool. It is appearing to be that they are more of a gpu mining site and not a site for asics

Correct, no Nicehash. I have spent a lot of time on that but now need to work with NH engineering. The action is on my side to do that at this point.

As far as the API goes, HiveOS is correct. On the box I actually insert the frequencies into the API for the web interface. Exporting that off box via the normal API is probably going to be a no. I will add it to the queue and see what I can do there, but the API handling inside cgminer is a mess of spaghetti.

Thank you,

Jason

Folk,

A question has come up on how to tune Z9 and Z9mini with the per hashboard feature. Here is a small writeup(copied in the original post now) that hopefully will explain:

To tune for best frequency

1) Set global frequency to 650. Set each other frequency to "Use Global".
2) Observe your boards for at least 10 minutes, if any drop out, on the next cycle decrease their frequency by 1 step in the pulldown.
3) Repeat this cycle until you have a stable minimum frequency for your boards.
4) To start the 'upwards tuning', choose one board (#1 for example) and increase it's frequency by 1 step.
5) Observe the board for at least 10 minutes to see if it is stable. If it is, repeat #4. If it is not, drop down 1 step and move to the next board.

Going through this process (which hopefully makes sense), you should be able to tune your units for your individual system maximums. It's best to do this with the fans set to 100% so you can remove thermals from the equation -- after which, set the fans back however you want them and see if your boards stay stable. If they do, good, of they don't, eithee decrease freqeuncy by 1 step or increase fan.

Please do note that sometimes a lower frequency produces a higher hash rate, so be mindful of that as you select for your environment.

Thank you,

Jason

... How did you managed to choose 762?

thanks

NiceHash: I've generated the traces requested by nicehash and submitted them for analysis. My eye does not see anything obvious as to the failure reasons, so I am reliant on them to provide information in order to try to add in support.

Other: I'm sure I'm forgetting something(s)... more soon.

Thank you for your patience and support,

Jason

Jason!

I, as a z9 mini user, are also ready to pay for the firmware.

Yeah, I've been through that, and the patches. The extranonce stuff actually appears to be working just fine unless there is something wrong in the calculations of the returned results. I have two traces that are exactly the same (as best I can tell) except for the work requested to be performed. nonce's the same, etc... one works, the other doesn't on NH.

When I connect to some of their stratum, they provide extranonce information back, on some they don't.... I may do a set of tests tomorrow without #xnsub and see what happens.

Here is an example -- one of NH's servers did provide me an extranonce setting:

{"id":null,"method":"mining.set_extranonce","params":["0000908e00"]}

Yet that format does not match their specification. It should have a second parameter option of '5' per their own documentation... I just don't know at this point in time.


Thank you for providing the link!

Jason

I've started collecting data on what is going on with nicehash. I'm going to have to contact them because I do not see obvious explanations for the failures. extranonce is supported by this firmware, it just does not function properly sometimes. I have just submitted the traces to nicehash to try to get some assistance in  understanding why this works sometimes, and fails sometimes.

Thank you,

Jason

I've started collecting data on what is going on with nicehash. I'm going to have to contact them because I do not see obvious explanations for the failures. extranonce is supported by this firmware, it just does not function properly sometimes. I have just submitted the traces to nicehash to try to get some assistance in  understanding why this works sometimes, and fails sometimes.

Thank you,

Jason

......
While trying to investigate this, I was banned from the flypool API.
--snip--

I've tried to reach out to them, but for the time being I am personally going to remove work from flypool until I can get an explanation.

Thank you,

Jason

Update:

Much to my dismay, I am not going to hit my self imposed deadline of tonight for the next update (paid users included). I am continuing to work on it and will release as soon as I am able to get all of the pieces together. This next update is reasonably large in terms of infrastructure support and will unify the paid and dev-fee supported images, as well as the Z9 and Mini images into one (not 100% locked on the mini yet).

The mini image has been running for about 24 hours stable, although I am not yet happy with the results as it requires a lot of effort to manually tune the units at the moment.

From an "internals" point of view, I am making very good progress on gaining control of other components of the system.

I apologize for the (continued) delay.

Thank you,

Jason