Topic: [ mining os ] nvoc - page 291. (Read 418549 times)

Love the v0018 release and all the functionality!  

However, POWERLIMIT NIGHTMARES!  

I have one major issue, I cannot lower the POWERLIMIT.  I run 8 rigs of 1050Ti and 125W is just way to high.  I have tried adjusting the base line and the individual POWERLIMIT settings and I am still seeing maximum power being utilized in NVIDIA-SMI and TEMP CONTROL.  I thought maybe the TEMP CONTROL was trumping the setting, but I don't think that is the case (at least based on what my 46 year old brain and eye balls looking at the 1bash code understands).  I thought maybe it was the correction in line 527, but that didn't change anything.

I tried "NO" for both WATCHDOG and TEMP CONTROL with POWERLIMIT set below MAX for the 1050Ti and I still see max power output.

I did notice during startup, of the three terminal screens that pop-up during startup that the second terminal session has the POWERLIMIT set correctly at 60.   However, something happens after the third terminal screen initiates (miner starting) that pushes the POWER back to MAX.

I added another rig of 1050Tis tonight and I saw more unusual behavior from POWER settings again where GPU0 goes to 125W as the max power limit and the rest of the GPUs all complied with my setting of 65Watts.   I have no idea what is causing this inconsistency in power limit settings.

I also noticed in the Guake terminal that the TEMP CONTROL module is displaying continuous notifications that 125W is not a valid power limit (even after changing the settings in the module to 60-65).

I normally run all my rigs at 60W, which keeps the current draw low enough to run 3 rigs of 8 GPUs on each 15 AMP circuit.  Also, extremely efficient.

I am still hunting for what is causing the forced 125W power setting.

Beats me Fullzero. My version of 1bash v. 18 has no way of executing the bash file Watchdog until I added it.
Just saying "yes" to the switch won't start it.

The other stuff does not work as I stated which is why I wrote my own part and edited out some stuff.

Maybe just me and my rig..shrug dunno.

I don't wanna mess up anyone with my crazy changes so I'll just keep em to myself for now unless I see others with similar issues.

This is getting big and complex. Ever consider client side program running in background and controlling stuff via a webpage?

Also, using separate files for settings and for the code allows you to share the settings in any module with a string "source ~/wallets" or "source ~/settings.sh"

I plan on using this pool - http://xvg-mg.idcray.com/

Thanks again for your work! Great resource to the community

Autotemp now working in SSH screen - That whole running part was not working.

echo $__FAN_ADJUST > '/home/m1/fa'
echo $POWER_ADJUST > '/home/m1/pa'
echo $ALLOWED_TEMP_DIFF > '/home/m1/td'
echo $RESTORE_POWER_LIMIT > '/home/m1/rpl'
echo ""
echo "LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL "

# HCD='/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL'
# running=$(ps -ef | awk '$NF~"Maxximus007_AUTO_TEMPERATURE_CONTROL" {print $2}')
# if [ "$running" == "" ]
# then
export DISPLAY=:0

if [ $LOCALorREMOTE == "LOCAL" ]
then
guake -n $HCD -r Maxximus007_AUTO_TEMPERATURE_CONTROL -e "bash /home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL"
  echo ""
  echo "process in guake terminal (f12)"
  echo ""
fi

if [ $LOCALorREMOTE == "REMOTE" ]
then
HCD='/home/m1/Maxximus007_AUTO_TEMPERATURE_CONTROL'
screen -dmS autotemp bash $HCD
  echo ""
  echo "process in screen autotemp; attach with: screen -r autotemp"
  echo ""
fi
fi

WATCHDOG ON SSH RESOLVED -

CODE:

if [ $IAmNotAJeep_and_Maxximus007_WATCHDOG == "YES" ]
then
HCD='/home/m1/IAmNotAJeep_and_Maxximus007_WATCHDOG'
screen -dmS watchdog bash $HCD
  echo ""
  echo "process in screen watchdog; attach with: screen -r watchdog"
  echo ""
fi

This works and watchdog is now running.
All I need to do is add the local remote part of the code in to finish it.

Now to tackle the temp part....

Can't wait to give v0018 a try - so many cool new features!

@fullzero
In the next version could you add this fix for Intel Hyperthreading being broken on Skylake and Kaby Lake processors - resulting in crashes?  For now people with these processors (Pentium up to Xeon) should disable Hyperthreading until BIOS fix.  Several of my boards don't have a BIOS update, and for Skylake processors, the microcode fix is better than the BIOS update (FYI, this is not Debian specific, but to any OS including Ubuntu, which is based on Deb)

https://lists.debian.org/debian-devel/2017/06/msg00308.html

Instructions are here:
https://wiki.debian.org/Microcode

It's good to see somebody got this board to work. I have problems with this board. I have a tons of PCIe bus errors. Are you sure you haven't changed anything in the bios? PCIe bus speeds auto or gen2, or above 4G MMIO? Also do you use the IGFX or one of the mining card?
Could you share your settings?

Was hoping to be able to mine XVG this release. Oh well, still really appreciate the work as always fullzero!

I may try and hack in XVG on myriad-groestl to the onebash, should it be easy enough?

Ok I added export DISPLAY=:0 to fist line of bash and now the script goes further.
But still I am getting the error I have posted below and no additional screens are starting.
Also I just discovered that the switch IAmNotAJeep_and_Maxximus007_WATCHDOG="YES" doesn't do anything! There is no code to go with the switch.
I will try to edit bash and stick it in there. I must be the only person using SSH lol. Why am I the only one finding all these issues?

Also we need discuss the new way to launch the miner using SSH and 2unix and 1bash. The way it's set up now is you use Putty or whatever and SSH to server. Then WITHOUT using a screen you execute " bash '/home/m1/2unix' ". Then what happens is the terminal displays some stuff and just stops when the bash launches the miner. So now you are left with a terminal screen that is just stopped and a miner screen you can't get to. The only way to get to it is terminate the terminal, re-log in and screen -r OR CTRL-c the current terminal screen and then screen -r. I am a Linux noob but seems to me there should be a better way. version 17 was simpler IMO. Open terminal, create a screen and execute bash. I think your doing it this way to automate a screen and miner in the case of a power up or reboot.

So in summary -

A: Watchdog not launching as code is missing
B: Errors on launch trying to execute something it can't find (BTW miner still launches and works in spite of error)
C: No idea if temp control working because I still can't get it to execute it's own screen
D: Funky startup procedure for SSH users

I love your work and really appreciate it. These are not criticisms, just notes to try to help...

dos2unix: converting file /home/m1/1bash to Unix format ...


workername: nv136


rig IP: 10.0.0.136


03:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
04:00.0 VGA compatible controller: NVIDIA Corporation Device 1b81 (rev a1)
22:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
23:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)


Tue Jul 18 09:47:50 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.47                 Driver Version: 384.47                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 106...  Off  | 00000000:03:00.0  On |                  N/A |
| 79%   58C    P8    12W / 125W |     94MiB /  3012MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1070    Off  | 00000000:04:00.0 Off |                  N/A |
| 54%   61C    P8    10W / 125W |     10MiB /  8114MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  GeForce GTX 106...  Off  | 00000000:22:00.0 Off |                  N/A |
| 56%   57C    P8    13W / 125W |      2MiB /  3013MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  GeForce GTX 106...  Off  | 00000000:23:00.0 Off |                  N/A |
| 57%   59C    P8    14W / 125W |      2MiB /  3013MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
|    0      1293    G   /usr/lib/xorg/Xorg                              69MiB |
|    0      1925    G   compiz                                          21MiB |
|    1      1293    G   /usr/lib/xorg/Xorg                               7MiB |
+-----------------------------------------------------------------------------+


ENVIRONMENTAL VARIBLES SET


Tue Jul 18 09:47:50 EDT 2017
Action: Removing ...
systemctl stop teamviewerd.service
Failed to stop teamviewerd.service: Unit teamviewerd.service not loaded.
fail

kill '/opt/teamviewer/tv_bin/script/teamviewer' - root (/home/m1/.local/share/teamviewer12 / /home/m1/.local/share/teamviewer12)



Failed to execute operation: No such file or directory
try again, full path...
Failed to execute operation: Invalid argument


LAUNCHING:  Maxximus007_AUTO_TEMPERATURE_CONTROL

  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:0]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:0]) assigned value
  1000.


  Attribute 'GPUGraphicsClockOffset' (m1-desktop:0[gpu:1]) assigned value 100.


  Attribute 'GPUMemoryTransferRateOffset' (m1-desktop:0[gpu:1]) assigned value
  1000.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:0]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:1]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:2]) assigned value 2.


  Attribute 'GPUPowerMizerMode' (m1-desktop:0[gpu:3]) assigned value 2.

I divided the settings into several files, so that it would be possible to set up purses and choose a currency, could be shared across several farms. And the map and system settings were locally configured.

Here is code to send email: It will try to install sendemail every time, but it is not problem. Or you can add apt-get in firstBOOT section of 1bash. All arguments must be loaded from 1bash using files. But I don't have time to do it, for now. I am using another way - I add "source ~/wallets # from this file we take $ADMAIL_EMAIL
source ~/settings.sh # from this file we take $RIG_EMAIL, $WORKER_NAME, $RIG_EMAIL_PASS, $RIG_SMTP
".

fullzero -- did you managed to get ccminer_alexei78 into this new v18 build?

Hi All,
i made a telegram script to report hash rates and other stats using telegram bot, the stats consists of power draw, temperature and fan speed on my little mining rig.

the code below, i got the command from older posts, currently the hash rates obtained from claymore or other miner that supports web-api, this script only works for claymore, can be modified if you are using ewbf, other stats is miner agnostic obtained from nvidia-smi
 

put the script on crontab and specify how often you wanted the report ex: 5 mins, then put this on your crontab
dont forget to chmod 700 on the script to make it executable

Hope this script helps...
any suggestion is appreciated

Go to the first page of this post and you can find change log for every release.

You are welcome.

Oh Sorry, didn't realize that they are integreated. Anyhow i like your work Keep going
When i have Mined enough Coins i will send you a Little Tip. Actually im Mining DeepOnion Coins...

Cheers

I'm planning to experiment with Salfter's NiceHash switcher, but by reading the relevant code in 1bash and switch, it seems that the individual OC settings (per card) defined in 1bash won't be used at all - only the ones set per coin, applied to all the cards. Since I have a mix of different cards, each one must take different core and mem OC values. I have an initial idea of the code changes needed, but before doing that, I'd like to check if there's another way to do that already implemented (which I missed), or something already being developed in that sense.

Thanks!

Where is the changelog for v18?

GParted Partition Editor is already included in the build mate! Use the top left button to search and start typing GPAR ...it's there. Trust me. nv0018 build has it at least.