Quote from: TenaciousJ on July 20, 2017, 04:57:46 AM

Quote from: fullzero on July 19, 2017, 07:04:58 AM

Quote from: OverEasy on July 18, 2017, 07:39:12 PM

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?

Yes this is planned: monitor / push / update / dashboard app; keep getting sidetracked adding contributions / new coins.

The new 1bash should solve problems / start watchdog and autotemp in a screen when in remote.

Quote from: DJ ACK on July 18, 2017, 07:46:57 PM

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.

Try the new 1bash and additional files posted on the OP. Let me know if it doesn't solve this for you.

I tried updating to the newest posted 1bash files as you suggested to resolve a problem where I have set the powerlimits for my cards individually, but the script changes one of my 1080ti cards (250w) to the power limit set for the 1070s (140w) so the card is only pulling 550sol instead of the 750 it should be.

I've triple checked my individual power limit settings vs. the GPU ID from Nvidia xserver against the powerlimit ID in the script, and they match. But it's not processing properly.

So after updating to the new 1bash fileset, it gets to the point where the fan settings are modified, the script loads the EWBF miner (for HUSH), and promptly crashes with the 'screen is terminated' message. I also have disabled autotemp and watchdog, but the problem persists.

Here's a screen shot of the problem that set this chain in motion showing the power draw of the cards vs. the powerlimit settings in 1bash and the IDs that were used in Xserver to match the powerlimits, and of the current problem.

http://imgur.com/a/zwf2s

I can't figure out what might be causing the miner to crash immediately on load like it is.. I've tried zeroing overclocks in case it was related to that, but that was no help. I ruled out power mizer by disabling that as well, but it crashes still.

I'm also set to LOCAL mode.

I made an updated 1bash which should resolve these powerlimit / remote issues. With the powerlimits the autotemp was not reinitializing unless explicitly killed or the rig was logged out or rebooted. This had the effect of not allowing changes to the individual powerlimits until such killing or logout / reboot.

In your picture I can see another problem which is most likely what has been killing your 1bash prematurely.

By removing the unused individual powerlimit variables you have created a situation where later in 1bash those variables are undefined.

For now; don't delete unused variables.

I can add logic to check or otherwise avoid this type of problem in the future; but it is simple enough to leave the extra variables for now.