Do we have a progpow miner on nvoc? Antone tried this yet?

I'm having a problem on new flashed images where the miner temp control bugs out and causes Nvidia driver errors? Tried flashing multiple versions of nvOC. Any thoughts?

I cross posted this to the discord bug reports with images. Can't post photos here yet as my account is newb

---

So I reverted to loading from disk image 19-2.1 and it is working fine now. I had previously been loading from image 19-3.X

There were no issues until recently.

I am having a repeating problem, but only with one rig, when ubuntu login screen asks for password after i enter the correct password it goes to a green screen but is totally frozen and will not progress to the desktop. This happens every reboot with only this one rig. Have reflashed the USB multiple times.

I finally just had to reflash the USB until it took. It still gets the error but it doesn't stop the miner from starting now, thankfully. Overall it was a bigger pain to initial boot compared to 19 - 2.0 but with the new cuda enhancements I can run a much more efficient miner. ~50% more hash rate and efficiency per watt!
Thanks for your continued work and support for nvoc!

I'm having an issue with the new version. Error attributing OC settings no matter what value I try, including same values I used for nvoc 2.0. After this error process terminates and tries again. Any tips? Been using nvoc 2.0 for months with no issue

AH, I'm only on 2.0 Should I wait for a new release or get 2.1 hmmm

Thanks, I'm basically just trying to run the newest CryptoDregde.

Is CUDA 9.1 implementation coming soon? To install it myself now requires too much hand holding from someone else. I'm losing a lot of possible hash by not being able to run better miners.

**EDIT** Couple posts above says in a week or so?

Okay, yeah maybe that's why it wasn't working for me. I've never used Cuda before, does it operate independently of our nvoc bash files?
I've compiled a couple miners before but they were always straight forward

Can anyone help me with a compile for Z-enemy 1.12a? Papampi add it to the miner update??

Trying to get some better hash rates on LUX, PHI2 algo.

I fixed that issue, I forgot to capitalize dmSL.
SO now the miner will start running for about 2 minutes, connect to the pool begin mining and then unexpectedly freeze and relaunch the miner.
It's been doing that for the last couple hours relaunching miner then rebooting rig.

Finally now it seems to be running stable for about 10 minutes while I was typing this reply. I made no changes so not sure the problem. Z-Enemy miner unstable?

**EDIT: been running stable for a few hours now**

One of my rigs keeps getting an error thought It seems to have been set up identically to the rigs that are already running
here's the error:

/home/m1/2unix: line 44:  2100 Terminated             bash '/home/m1/3main'
nvoc v0019-2.0 - Community Release


Then it just tries to keep cycling the miner to the same error..
Maybe I sshould just re-image the drive?

Also what is the password for Teamviewer? I tried root. No luck

NVRMND

One of my rigs keeps getting an error thought It seems to have been set up identically to the rigs that are already running
here's the error:

/home/m1/2unix: line 44:  2100 Terminated             bash '/home/m1/3main'
nvoc v0019-2.0 - Community Release


Then it just tries to keep cycling the miner to the same error..

Okay. Should I then also edit 1bash? Besides COIN == LUX must I add the address, worker etc information in 1bash??

Z-enemy or ANXccminer to mine LUX

I downloaded and ran the new miner updates for 19-2.0 but I don't understand hot to implement them into 1bash. I get this is a dumb question but I am a noob to GPU mining. Appreciate some hand holding lol

My wallet has been unlocked and not encrypted. I have gotten STATUS: not in masternode list for about 18 hours now so it doesn't seem to be a sync issue.

See my previous answer to marvel directly above for other info.
How can I be getting masternode payouts without ever successfully starting the node and it claiming be be not in masternode list?

If there is a command to search for my specific IP in the masternode list I wont worry as i'm still getting mining payouts BUT what does worry me is that the 5000 coins in the masternode only show on my dashboard and not in my coin control.
Is that odd? or would they become available again after stopping masternode in my VPS commands?

And how can masternode payouts be blank in the debug console while the MN is literally paying out mining rewards?

I appreciate your answers here guys. I'm noob as fuck but this still doesn't make logic...

I cannot send myself 5000 coins again as it states that I have insufficient funds even though the 5000 show as available on my dashboard. In my coin control is shows my original amnt over 5000 as (change) and shows 2 masternode payouts but the 5000 actually in the masternode doesn't show up.
In transactions the payment to myself (masternode) is shown as the -0.0001 SYNX fee.

So if my vin cannot be allocated yet the masternode is somehow still paying out what is going on?

The masternode.conf file is correct but when i type masternode outputs in debug console it comes back blank.

The masternode has given me 2 rewards since yesterday but still has (STATUS: not in masternode list) and (Error: Could not allocate vin) when trying to start.
Shouldnt the 5000 coins of the masternode being showing in my coin control tab?

In what ways can I check with debug console, a web browser or putty that the node is actually enabled though the wallet may state otherwise?

I followed u3mur4's guide to set up my masternode but am running into an issue when starting the node.

I continually get Error: could not allocate vin. Everything is inputted correctly in the create node tab as well as both of my .conf files.
Any input on a solution?
Maybe pertinent, when looking in coin control features the 5000SYNX for my node does not show up but on my dashboard is stated they are available.

When creating the masternode I send the 5000SYNX to an internal wallet as I already had a couple staking rewards. This hasnt been an issue with any other masternodes I have set up.