is no one monitoring this thread?

i dont understand, on the site it says the token sale starts in 43 days, but i can already buy now in a "pre-sale" and i get a bonus depending on what week we are in the this presale? then why does the bonus not apply when i enter an ETH number in the contribution box? doesn't work on the main token sale page and doesn't work on the confirmation page with the contribution address, shows 0 bonus.

please advise.

Hello again fullzero,

Haven't checked the thread since page 84 so i'm sure i have plenty to catch up to, i see you and some of the posters went ahead and made a monitoring script, kinda sorry i've been out of the loop since i too made a monitoring script because of my recurring soft/hard crashes.


i'm not sure if your script covers the same thing mine does, or if they can be merged so i'll let you be the judge, basically what it does is monitor the system load average and if it goes over a specified amount (in my case over 2.0 means i had a soft crash and soon the load average will climb until not even SSH works) it reboots the machine and sends me an email after the rig is back up, the script also checks the external IP of the rig and sends an email if the IP changed (i have a dynamic IP).


this script is initiated from crontab every 1 minute, needs to be located in root/jobs.

please tell me if this is redundant considering the additions to v18.

Hey fullzero, i have a question,

without a doubt my biggest problem right now is that when my miner crashes it takes the whole rig down with it, everything gets stuck, SSH barely works, average system load jumps to 14.5!! and Xorg takes up 100% of the CPU, its so bad that none of the standard reboot commands work, they just do nothing, the only thing that actually reboots the rig in this state is "echo b > /proc/sysrq-trigger" so i've set up a script that checks the average system load and if its over 2 it uses the command to reboot, and it works, but i dont like this "solution", yesterday after a reboot nvOC got corrupted somehow, lost my customized oneBash and the whole system became read-only (thankfully i had a oneBash backup that was only a few days behind).

so the question is, what can i do to relive this Xorg error, i run a 7 card rig and never plan on going for a higher number, what can i do with Xorg that would fix this?

Thanks.

i see, i cant dual mine on anything less then 120 pl if i want the memory clocks to be 1000+ and still be stable.

The dcri value is only for dual mining, if you're only mining Ethereum theres no point in using dcri, theres no point in even using claymore miner, genoil miner is just as fast but with no fee for strictly ETH mining.

if you are dual mining just search for "dcri" in oneBash, the default setting is 70, i recommend changing it to 40.

7 x 1070 rig here, i've found that if my clocks are even slightly too high it doesn't matter which miner i'm using the rig just hangs forever unless i restart it remotely via SSH, i'm using dcri 40 and i think its the best setting right now, its about 31.5Mh/s for ETH and 410 Mh/s for SIA, on claymore 9.5 it was more like 29.8/390..

Whats your power limit and clocks if you dont mind me asking? i'm on 125pl/0/1400.

Hey guys, any clue what might account for the difference in PCIE utilization? asking because GPU6 is my least stable card that requires the lowest clocks of the bunch and evidently it also has the lowest PCIE utilization.
http://i.imgur.com/pwxDFAQ.png

I see, well i guess its back to monitoring xorg and rebooting if its running at 100% cpu for more then a few minutes..



Just added the new version and on the exact same clocks and power limit i went from dual mining ETH/SIA @ 204/2750 Mh/s to 217/2900 Mh/s, quite the improvement! thats like 6%!

For everyone that have stability problems where the OS hangs or slows down to a halt, this is due to Xorg taking 100% of one of the cpu cores, as far as i can tell this usually only begins after some kind of soft crash from overclocking/undervolting, i've googled my ass off and found a few references of people claiming to have solved this problem by configuring Xorg to run from the integrated intel GPU and leaving the nvidia cards to pure computations, my linux know how is Very limited so this is more of a question for fullzero.

what do you think Fullzero?

Sorry for the late response, right now i'm trying to initiate a system reboot in the event that Xorg service takes up 98% or more cpu for for 10 seconds or longer, which happens every time any miner crashes, Xorg always shoots up to 99-100% cpu and stays there, trying to use monit for this, will update if it works.

i like your port-knocking idea.

i'm actually dreading the 0018 release... i've made so many changes to the 0017 oneBash and nvOC in general that moving them to the new version is gonna take forever.. currently working on automatic rig reboot in the event of a system freeze from the miner crashing.

Any idea why when i try to SSH into nvOC as root with miner1 as my password i get "Permission denied" but as m1 it works? turns out one of my cards is problematic and cant handle much lower clocks then the rest of the cards and the whole system gets stuck to the point where i cant even reboot it remotely with SSH, at least not with "sudo reboot", "sudo shutdown -r now" or "sudo init 6", even "sudo systemctl --force --force reboot" doesnt work, just hangs there without even giving me an error message, i want to try using "sudo echo b > /proc/sysrq-trigger" but i cant do that unless im on root.

just fuck my ubuntu up..
http://i.imgur.com/0pSDR1p.png

help.

EDIT: nevermind figured it out, my linux knowledge is very limited so i wasn't aware i can jump into root with "sudo su", anyhow after that "sudo echo b > /proc/sysrq-trigger" did manage to restart the rig.

I wish there was a way, i've been looking for over a week now, maybe it can only be done on windows? or maybe the tool/command just doesn't exist on linux yet?

If anyone is interested my 7 card rig with all GTX1070 FE is finally stable running for the past 72 hours with the following clocks and pl:

__CORE_OVERCLOCK_0=000
MEMORY_OVERCLOCK_0=1400

__CORE_OVERCLOCK_1=000
MEMORY_OVERCLOCK_1=1400

__CORE_OVERCLOCK_2=000
MEMORY_OVERCLOCK_2=1300

__CORE_OVERCLOCK_3=000
MEMORY_OVERCLOCK_3=1600  

__CORE_OVERCLOCK_4=000
MEMORY_OVERCLOCK_4=1400

__CORE_OVERCLOCK_5=000
MEMORY_OVERCLOCK_5=1300

__CORE_OVERCLOCK_6=000
MEMORY_OVERCLOCK_6=1200


INDIVIDUAL_POWERLIMIT_0=125

INDIVIDUAL_POWERLIMIT_1=125

INDIVIDUAL_POWERLIMIT_2=120

INDIVIDUAL_POWERLIMIT_3=130

INDIVIDUAL_POWERLIMIT_4=125

INDIVIDUAL_POWERLIMIT_5=120

INDIVIDUAL_POWERLIMIT_6=120

i determined the power limit for the cards by their individual temperature and lowered/increased their clocks accordingly, if i give them all the same power limit GPU 3 is 10 degrees C cooler then GPU 2/5/6 while GPU 0/1/4 are right in the middle, at the current power limits all the cards are pretty much the same temp plus or minus 1 degree.

i might be able to push GPUs 1-5 further, i suspect GPU 6 was causing my crashes since the last crash when it was clocked @ 1300 it was the only GPU to lose its sensor connections, since lowering it to 1200 everything is stable so there might be room for higher clocks on the rest of the cards.

wish there was a way to determine which are samsung and which are micron..

This bothered me too so i added this to oneBash, just slap it anywhere:

xrandr --fb 1360x768




Didnt work for me either, my solution was to uninstall teamviewer, go to the teamviewer site and download the .deb file, install that and add teamviewer to startup applications so it starts when the rig boots, You also have to disable the part about teamviewer in the onebash script or else it will not work, either delete all mention of teamviewer or add a # in front of the lines of code to disable them.

Thanks but i've tried that already, theres nothing there that i can use to find out the memory vendor, i've tried every command or system info tool that can provide information on the GPU, as far as i can tell theres nothing that lists the memory vendor..

Nvidia.

Does anyone have any idea how i can check if my cards are Samsung or Micron memory in ubuntu? i've looked but i cant find anything that will tell me this info.