Topic: [ mining os ] nvoc - page 176. (Read 418546 times)

At the risk of derailing an otherwise good topic:

• Bitcoin Gold is not a Bitcoin fork
• Bitcoin Gold is a Bitcoin Core fork and a new premined coin

• Replay protection implementation still is not implemented, so do not use a wallet for mining that you have BTC on
• Bitcoin Gold still doesn't build properly in most instances

• Bitcoin Gold is not a Bitcoin fork
• Bitcoin Gold is a Bitcoin Core fork and a new premined coin

The above may seem harsh, but facts are what facts are.
While many of us are going to mine it (myself included) for purely speculative reasons (mostly in hopes to turn a good profit), always be sure to protect yourself (and your prior investments) and don't get sucked in by buzzwords that say one thing and mean another. Don't just blindly trust; do due diligence.  

I have posted a how to fix for telegram and web info yesterday just roll back a page or 2 you will find it
But 1.4 is coming any time soon, and hopefully all will be fixed.
So its easier to wait a bit.

fullzero is working on 1.4 to release before BTC Gold fork,
I havent heard none of the pool names they posted in their site : btcgpu
Any one have any experience with any of them let us know to pick default pool.

Stay tuned for 1.4 release.

my papampi telegram message, as you can see below, does not return values about Temp, Fan, Power.

How to solve this problem?

-------------------------------------------------
Worker: nv074
Boot Time: 2017-10-19 21:05:30
System Up Time: up 2 hours, 51 minutes
Miner Uptime:    02:50:55
Currently Mining: "ZEC"
Reboot Required: No
GPU Count: 6
GPU Utilization:
100 100 100 100 100 99
Temp, Fan, Power:

Stay tuned for that update guys, once I see the pool and other info I will post it here instantly so that all our nvOC users can take advantage of it.

PS : Looking forward to it 

Perfect explanation.

Like papampi said we can have individual nicehash coins prepared, but it takes lot of effort and not really sure whether it is worth a shot!

It creates more complications rather help, I would suggest to use independent switches and not to merge them unless you are expert at it.

There is 2 miners available for Equihash on 19-1.3
dstm and ewbf

Hi all, I just want to know if possible can we mine ZEC using another miner? Currently I using NVOC v19.

Another thing, BTG will coming in another two days after BTC hard fork. They will using equihash algorithm which definitely provide us another coin to mine. So what you all thinking about this new coin?

Is there a new ethminer update available?

It think the fork was 5 days ago. I still use an old fork of ethminer and it runs just fine.

Does anyone know if we need to update Ethminer if we plan on using it (instead of Claymore) after the Byzantium fork?

Good catch MentalNomad, I didn't check wtm json and thought it's nicehash tag is the same as other coin tags
So that make it so hard to implement them in wtm auto switch

@Rumo, I think it's failing because the naming conventions don't match up for NiceHash between nvOC and WTM.

Most straight coins have Tags in the WTM JSON like this:

"Ethereum":{"id":151,"tag":"ETH","algorithm":"Ethash"
"Zcash":{"id":166,"tag":"ZEC","algorithm":"Equihash"
"Zencash":{"id":185,"tag":"ZEN","algorithm":"Equihash"

There's only one of each tag per coin, even if many coins use the same algo, and the same names are used in 1bash for those coins. I think that's the field @papampi's switcher is using.

But for NiceHash, they ALL use the tag "NICEHASH."

"Nicehash-Ethash":{"id":15,"tag":"NICEHASH","algorithm":"Ethash"
"Nicehash-Equihash":{"id":19,"tag":"NICEHASH","algorithm":"Equihash"

Basically, nvOC and Papampi's switch look at things per coin (and each coin has one algo.) NiceHash is designed to look at things per algo. (And each algo has multiple coins, but you never see that because you're renting hash to NiceHash, not knowing what you're actually mining.)

WTM puts them in a single list for comparison, but that can cause complications at our end.

Well, not 345622. That would be an illegal number...

Port number only goes up to 65535.

ICANN allows registration of ports from 1024-49151 if  company wants to claim it for their protocol (like a particular game or application), but you're usually safe using one of these. If you have a game that suddenly doesn't work well, check if you've grabbed the port range it wants to use, but most games will try to find another port to connect on.

Ports below 1024 should be avoided as "well-known" ports that lots of people use, such as 22 being SSH and 80 being http.

I find it easier to leave them on port 22, and use the routers to deal with it.

I give my rigs static IPs... 192.168.1.254, ...253, ...252, ...251.

Then, on the router, I set up inbound routes for traffic for specific ports to go to those machines:

Inbound port 11254 -> 192.168.1.254 port 22
Inbound port 11253 -> 192.168.1.253 port 22
Inbound port 11252 -> 192.168.1.252 port 22
Inbound port 11251 -> 192.168.1.251 port 22


At all locations, I set up the port forwarding for a whole slew of rigs. That way I can move my rigs around locations without having to worry about which port is open, where.

The nvOC automation files are not designed for that, and there's a lot to do without trying to add that complexity.

That beings said, some mining software does allow you to do that. For example, Claymore lets you specify which GPUs you want it to use. You can fire up one instance of Claymore with 7 cards, and then another instance with 6 cards, each on a different algo that Claymore supports.

I don't know which miners support picking/choosing GPUs, just that Claymore does.

That said... why do you want to do this? It doesn't make a lost of sense to me.

When there's a hot Equihash coin, like Zclassic is at the moment, usually all the NVidia GPUs seem to profit more on it than on, say, ETH, so you might as well point them all at it...

Meanwhile, if you're looking to split up your mining so that you can accumulate two different coins, you can just mine one day per coin, and keep switching back and forth. You'll still accumulate... and the rig will probably be more efficient running a single miner process, and managing/supporting it will be easier to troubleshoot & etc. than if you tired to run two different mining processes.

(Personally, I've separated all my rigs into AMD-only/1060-only/1070-only rigs, so as not to mix GPUs specifically in order to avoid having to split the GPUs.)

Just FYI, my preliminary testing:

While some of my 1070s GPUs support power limits as low as 75 watts, taking them down to, say 85 watts, severely reduces hashrate - drops from 30 Mh/s for ETH to 26 Mh/s. Raising them back to around 100 watts bumps up the performance.

The GPUs that insist on 110 watts minimum don't seem to perform better than those running at 100 watts, but that's just based on rough eyeballing. I'll need longer run averages to be sure... and the higher-power GPUs may allow for more OC. Time will tell.

I won't be able to work hard on tweaking and refining until I sort out some instability issues on a couple of rigs - instability in a rig causing the mining process to restart often sacrifices much more mining than having a slightly lower OC - like @FullZero says, stability is more important that great OC!

I think settings included in nvOC for nicehash are for salfter_nicehash_auto_switch and not individual mining
Maybe damNmad can help you with individual nicehash miners for WTM_AUTO_SWITCH (or at least some of the good ones)

@fullzero
@damNmad

You redirect the ports by NAT/PAT on your router ! ssh port is always the same ! You could change it but it is not a good solution.

Search on the internet how to redirect with address and port transaltion from the internet to your machine at home. We have all the same problem ! it is better to not rediect directly the ssh port to your rig. It is risky to do that.

You must redirect from external wan address to local IPs and Ports like 45022 or 345622 for example. Otherwise you risk attacks.

Ok, from the result I can clearly see that you are not using the suprnova settings properly.

To use suprnova you don't need to add wallet address and set worker password as 'x' on suprnova dashboard

Assuming 'dcrminer' is your suprnova worker name and 'zbfountain' is your suprnova login name please use the below settings in your 1bash


Remove all the additional details you have added in 1bash for DCR.

Now replace 'DUAL_ETH_DCR' & 'DUAL_ETC_DCR' settings in 3main with your

Open 3main file, search for 'DUAL_ETH_DCR' and replace the below lines as is in the right place.


Open 3main file, search for 'DUAL_ETC_DCR' and replace the below lines as is in the right place.



Let me know if it worked for you.