 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
Hey poisonxa,
Thanks for your fork. I'm looking forward to trying it.
Try running auto overclock and let me know if it worked
Currently on nvOC v0019-v1.3 mining ETH only with Claymore 10.0
I did a lot of work getting nvOC to run 19 OC'd P106-100s headless on a ME mobo but only managed to get 16 OC stable at 18.1 MH/s and 3 stock clocks at 17.5 MH/s.
Yes I know for P106 that's slow but they are Gigabyte with Hynix. ;-(
My apologies if this has been discussed already, but how does your fork handle >16 cards OC? And if that works, I'd love to hear how you did it as I ran into limits with X and thus had to customize xorg.conf device and screen sections to list only 16 screens but have 19 devices.
Thanks and hope to hear from you.
-z
I also have one rig with 12 x P106-100s and can't overclock them at all. I run nvoc PXA ver 1.9.6.1 and tried with headless mode on. I have also tried with CHOSN and it runs only in stock rates. I have another rig with 6 x P104-100s and they also run only in stock hashrate. How did you managed to OC those yours P106-100s? Try running autooverclock and let me know if it worked |
|
|
|
|
our xorg self populates on every reboot so no need to modify it and our autooverclocker clocks cards to perfection we will be releasing a new platform soon so stay tuned.
|
|
|
|
Evening all,
having a bit of trouble getting started.
Error reads:
There is no screen to be resumed matching miner, waiting for miner to load
and repeats about every 5-10 seconds.
Thanks for all you do.
to sum up possible reasons for this if it always does it: check your coin information make sure the workername,address,pool,port are all correct if they are then proceed to pressing f12 to launch guake and find a tab that free to type in. then type in pxa stop to stop the rig from running programs then type in pxa logs and go to the section that says troubleshooting section. copy or screenshot that section and paste it here to help you troubleshoot further. |
|
|
|
Evening all,
having a bit of trouble getting started.
Error reads:
There is no screen to be resumed matching miner, waiting for miner to load
and repeats about every 5-10 seconds.
Thanks for all you do.
Come to our discord to assist |
|
|
|
|
I actually like when optipessi comes and posts it makes the the following posts very interesting, and entertaining. Thank you.
|
|
|
|
This is a preview for the upcoming release sorry its taking so long but we are working hard to release it CHOSN PREVIEW:  Thank you all for your patiance and your support You can catch up on the newest updates and ETAs and previews on our discord channel found on OP. Thank you again the PXA Inc. Team. |
|
|
|
|
still come to the discord channel to discuss the other errors.
|
|
|
|
|
Restart miner see if error clears up
If not come to our discord for further troubleshooting
|
|
|
|
|
Any bugs that have not been resolved please inform us in our discord channel in the bug-reports or drop some bugs here to fix.
|
|
|
|
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....
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 |
|
|
|
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 😀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 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.  What version are u running with these issues?? Come into discord and pm me I would like to see what's going on. |
|
|
|
BETA VERSION 1.6.1 is out and live set your update to yes in 1bash and to beta ENJOY
CHANGELOG:
FIixed WTM ZZ issue
Added a floating coin to wtm for less usb io and to sync all other controllers
Redid fail safes to watchdog and temp control / overclocker
Fixed pl issue now it gets set prior to miner start
FIixed other small bugs and did performance tweaks to ai for faster response to temp/autooc
THANKS
Ok earlier today I realized my rig was offline and must of been whatever update that got pushed crashed my drive so i downloaded the latest os burned it now I cant get any miner running eth or zec and it seems stuff that was in 1bash is missing get on discord ill help you out |
|
|
|
|
guys if you have my telegram info saved as your telegram information please blank it out thank you im sorry for all the mixups
|
|
|
|
First I would like to thank you again. I set my max power to 130 watts with auto overclock only mining ZCL. The first two cards we're set to 120 watt max but the rest stayed at 150. Is it just a matter of tweaking the auto temperature control settings? I'm running 8 EVGA GTX 1070's. Also the default ZCL mining pool zclmine.pro is getting me nowhere near what I should and there are plenty of complaints on this board about the pool.
Come on discord to help u out to see what's up with your power settings |
|
|
|
|
Reuploaded a new image with bugs removed and renamed the image for clarity thanks you guys! sorry for the huge bug last night i promise this wont happen again!
|
|
|
|
|
You'll need to reetch new image uploaded
There was an update that was pushed that updated core drivers and now many systems stopped working
|
|
|
|
|
New image uploaded enjoy!
|
|
|
|
|
BETA VERSION 1.6.1 is out and live set your update to yes in 1bash and to beta ENJOY
CHANGELOG:
FIixed WTM ZZ issue
Added a floating coin to wtm for less usb io and to sync all other controllers
Redid fail safes to watchdog and temp control / overclocker
Fixed pl issue now it gets set prior to miner start
FIixed other small bugs and did performance tweaks to ai for faster response to temp/autooc
THANKS
|
|
|
|
|
