Topic: [OS] nvOC Nvidia Mining OS FORK v PXA-1.9.6.1 ( UPDATED 1.10.2018 ) - page 3. (Read 3779 times)

Just ignore him.
If you don't want to donate, turn it off.
If you still don't like it, go somewhere else.
No one is holding a gun to your head.

I'm new to mining, and nvOC.

I started to move my rigs to this fork and really amazed with the fact that poisonxa most of the time available for questions and support on discord.
He helps me to debug error in custom changes that I made to 8Coins. I have no problem donating less than 1% to him because his attitude and support worth far more.

ya optipessi... im not sure why youre taking so much time out of your day to attack this fork.

at least for me who is new to mining... i tried nvoc 19. didnt work.  tried 19.4 , worked great.  wanted to update so i tried the community build and the temp control was broken.  so i went back to 19.4.  wanted to update again so i tried pxa fork. hopped on discord and was able to get instant answers direct from pxa.  now its working great and im happy again. 

not saying the community build isnt as fast on discord at all, i just didnt try them yet.

but bringing me back... are you mad you didnt fork ? or are you mad someone is forking and making money? im just confused

I don't know what your problem is optipessi

Poison is working on this project ALOT - many many hours.

If he wants to create a good quality fork and ask for donations - that is completely allowed.

You could do it too - no one is stopping you.

There is no problem with anything he has done.  Your bad mouthing him won't change anything.  Everyone is free to do with open source as they please....that is kinda the point.

Feel free to go and use the Community edition that doesn't have the donate option.

I am happy to pay for something where I get just about instant support (on the discord channel) and he is using the product himself for his own rigs, so he knows the value creating the best mining OS.

A much better analogy (IMHO) is Linux itself.  Linus made this great OS and gave it free to the world.  RedHat comes along and puts their own branding on it and charges a fee if you decide you want to buy it and get support etc.  This is perfectly fine and encourages developers to create their own versions.  And they have - SUSE Linux, Ubuntu, etc.

We stand on the shoulders of those that came before us.  We thank those that contributed, but it doesn't mean we stop innovating - thank you so much to fullzero for creating this in the first place. Thanks to Poison for continuing to make it better!

If you want to use it, great.  If you don't, great.  Please stop coming here and bad mouthing Poison for something that everyone has agreed is ok for him to do.

Jim

In the beginning of your statements you've rigorously stressed users to make the donations! then you have changed the statements over and over again, now here we are.

Out of those past 8 months of the official nvOC haven't seen the original developer @fullzero or any other devs never asked for a donations like you did (they only had their address in the bash code or somewhere but never asked aggressively like you, I swear), you probably think that they don't have babies or family to feed and they never had time/don't know how to create donation button like you did!!!

I still don't understand, why on earth you even have a donation button on the first version of fork given you have forked 8 months of work from others, was it really a high priority & are you going to share the revenue to the official version DEVS? (I really doubt that).

This shows how cheap you are. period.

Your feature set :


You just check your feature list again and see what you are actually providing something new??


Awww! so nice to see that you are sorry that you are not sorry  (Thank your writer for the above line)

I guess you got a problem with my questions!

How about this ??

No one forced you to fork.
No one forced you to ask for donations and take 1% mining shit either form users for copying others code by simply calling it a fork!
But you are doing it shamelessly anyway!

I would suggest you to get a real job and feed your family, stop copying others work & finally stop begging using others work. JUST my 2cents.

I guess its not even a month from the start of your fork (copied 8 months of work from official version) and what you have got in your 1st version is AUTO_OC (which partly works), DONATION button (works perfectly well because that's what you are really after).

Is that what all you got? Sorry, that's what you are, a PARASITE and now you go back to your own spoon.

PS0 : I probably should fork your version and start up a new OS and start begging by bringing my kids, family & ex-girlfriends into it
PS1 : I bet you have asked someone to write this reply(FORKED reply) because all you do is COPY &&&&&
         PASTE of-course
PS2 : I am really sorry for the long post

Hi! tell me please how to switch to default repo after I was looking for workaround and added this repo sudo add-apt-repository ppa:graphics-drivers
so now cant do your instructions ((

Thank you in advance

Thanks for all the help tonight guys....
One of the two test rigs up and running..
The autoOC pretty cool.


Now if we can just find me some video cards for the big rig that are reasonably priced...


...and that @Yeti hasnt snagged

OK, give me a few. I'm driving home in a bit.
I didn't try HD raw copy until it had given my that error a few times with the flash tool that comes in the ZIP file.

Thank you

Come to the discord channel to assist u quicker but it looks like you'll need to reflash with etcher that sounds like u used hdd. Raw copy

Hello All,
New User, and moderate user of the original nvOC. Thanks for the work. I came here to check it out and see the differences.

Last night i put the current version 6.1 on an Z270-A PRO mobo, with older dissimilar cards to look at/test the overclocking features. After doing some updates (I had updates turned off?) the next screen began to load until i got the following error. I was mining "ETH" in the select coin block.

/home/m1/Resources: line 62: let: \e[0m: syntax error: operand expected (error token is "\e[0m")

Any help would be appreciated, I did take a look at the Resources file, but with my limited knowledge nothing stood out at me in the section mentioned by the error.

Thanks....

I used fiirst version of fork. All was ok, but 2 days ago all my rigs crash and dont boot. And I updated to last version.

Did you run it before and not have the problem?  I spoke with the developer last night on Discord and he felt that it was my card being locked somehow, so I've been trying to track it down on my side - but if it worked before and doesn't now, that would definitely help me.

I've been using nvoc 1.9.4 for a few weeks now (tried 1.9 2? i guess. the community build but was having temp control issues)
going to be setting this up tonight and giving it a go but i wanted to say that the level of support im seeing on this thread is incredible (also in the other nvoc thread for that matter).  I feel like i get better support from all of the nvoc dev's/members than i do from microsoft and the other brands i have.

tl:dr - trying nvoc 1.9.6 tonight, GJ devs!

I have the same problem on last version PXA-1.9.6.1

Forks are a common phenomenon in the software development community, they are also common in anything in this life.

Look at the three major cloud computing providers, AWS, Azure, and Google Compute..... We all know that AWS revolutionized the cloud. Do you expect Microsoft to walk away from a billion dollar industry because AWS exists ? No, absolutely not.

Did you expect Ford not to make a pickup truck after Dodge did simply because Dodge beat them to it? No, absolutely not.

One of the biggest forks that I can think of to this date is the fork from Owncloud to Nextcloud. I'm not sure what you're problem is with forking something to make it better---but seriously, chill out.

Same principle applies to nvOC. All initial designing and coding gets accredited properly. The only difference is, we see an opportunity to make something good, great. And because of that, we're devoting, time, resources, and money to improving the nvOC platform in a way that is driven differently from the Community Edition.

Got a problem with it? We're sorry, but we're not sorry. No one forced you to use the fork. Go back to the spoon.

I thought of giving it a go and tried this OS and there is no difference at all in my hash rate
using AUTO_OC, on top of that, it has crashed my RIG which was running from past 3 weeks, lost 28 hours of mining.

These guys are absolute bonkers, WTF!! forking an existing established open source nvOC (for what, god only knows)

There is no link to the official source on the OP, at least they added the credits!!

Now what? you rename this OS and start selling it and create your own coin ??

Such a RIP off from the others work! Just like all those filthy token airdrops.

I will switch back to the original version. Hope people understand this mockery and stay away from this filth.

Also heard that there is a BAD BLOOD in this fork!!

PS : Hope we don't see another fork rain 😀

What version are u running with these issues?? Come into discord and pm me I would like to see what's going on.

I just downloaded your version (1.9.6.1) to check out... Navigating the settings wasn't super intuitive, but I finally got the hang of it and setting it to remote for SSH made my life much simpler.  I made the following changes:

COIN=ZEC
WTM_AUTO_SWITCH="NO"
WTM_PROFIT_CHECK="NO"
TEMPERATURE_CONTROL="YES"
LOCALorREMOTE="REMOTE"
TEAMVIEWER="NO"
DO_UPDATES="NO"
TELEGRAM_ALERTS="NO"
ZEC_ADDRESS="my address"

I'm particularly interested in the auto OC functionality - I'm also just running it first on a test rig with two 1080TI in it.

I watched the script running in the screen session, it said it was making changes to the mem speed, but when I tried "pxa gpu" in another window, the values weren't changing - is this expected behavior?  I tried the previous version and
it didn't seem to change the power limit, basically it was always at 260w - this one started out at 150w.  As I watch it increase the Core and Mem values, it doesn't appear to have any effect on the miner either - it just cruises along at the same hash rate as when it started.  Am I missing something?

Also, the script does print this error:

ERROR: Error assigning value 50 to attribute 'GPUTargetFanSpeed'
       (m1-desktop:0[fan:0]) as specified in assignment
       '[fan:0]/GPUTargetFanSpeed=50' (Unknown Error).

And the fans (obviously) don't appear to be controlled by the system...

It looks like a cool fork, and I'm looking forward to playing with it more once I understand how exactly it works.  

get on discord ill help you out