It returns the same:
m1@m1-desktop:~$ GPU 0, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 1, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 2, Target temp: 65, Current: 57, Diff: 8, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 3, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 4, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 5, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 6, Target temp: 65, Current: 61, Diff: 4, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 7, Target temp: 65, Current: 59, Diff: 6, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 8, Target temp: 65, Current: 63, Diff: 2, Fan: 55, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 9, Target temp: 65, Current: 64, Diff: 1, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 10, Target temp: 65, Current: 60, Diff: 5, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 11, Target temp: 65, Current: 62, Diff: 3, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ GPU 12, Target temp: 65, Current: 63, Diff: 2, Fan: 50, Power: [Not Supported]
GPU: command not found
m1@m1-desktop:~$
m1@m1-desktop:~$ Sun Dec 17 10:43:54 MST 2017 - All good, will check again in 13.5 seconds

OK, that's the answer! The bad thing is that it does not only fails to read, but what is more important to set power limit. On older driver it did both correctly, I checked that with wattmeter.

what can I type in the terminal to modify GPU settings while miner is running for each GPU individually? i.e Power limit, oc core, & fan speed

It is running in the background
In a guake tab run

@cryptatome

   OK papmp, got the time stamp going but had to put the change into the WTM check and not auto switch as it is off.  I am only wanting at this time to see what coins are bobbing to the top and for how long and what kind of frequency that they will have.  Years ago I did an AI program for the stock market and it did quite well for a long time until they found out I had it running and changed the game.  Then "08 came and wiped out all I did. 
   I see patterns and that is what I am looking for here as well.  Once I have a sufficient data set to work with, I will be able to predict which will be the best to run... I hope..

Crypto as soon as I get the thing soused out I will be glad to pass on to you. It will be a simple form of which you will extract the data comma delimited and import to excel like pgm.

You will have to extend the size of the log file for What to min check so you can capture a large amount of data

Hello,
in the PAPAMPI WTM_AUTO_SWITCH settings, what is the exact role of the setting:

WTM_AUTO_SWITCH_SYNC_INTERVAL="3"

I suppose the units here are minutes.

Cheers

Hello everyone.

I want just to say thanks to anyone who makes our lives easier with this great distro...

I noticed a problem/bug with the community build. it was working great on ast Fullzero release 1.4 and i'm talking about wi-fi networking. Yes i'm using one rig with wi fi for obvious resons, and it was working great (tp-link 722n - chipset rtl8801eu), but since i made the update to community build the wi fi after every restart just hangs, stops working. usb stick isnt recognized. if i take it out of usb and reconnect everything starts working.


any idea what could be or what to do. can anyone take a look. maybe some boot priority for usb drivers?


thx

As per my post #6160 (https://bt.irlbtc.com/view/1854250.msg26247720#msg26247720), I think the only "changes" made in 19-2.0 that could be responsible for this are normal Ubuntu updates made by the upgrade script. As such, the next time you try the upgrade, change this line of the script and see if it resolves the issue:


to


So, what that will do is upgrade your nvOC version to 19-2.0 but will not make any changes to your underlying Ubuntu system such as driver updates which I think are probably to blame here.

Give it a go and let us know if it works for you.

Black screen tells me you are probably running LOCAL. Have you tried to ssh (putty) into it from a windows machine? When I have seen that black screen on my rigs, I have found that GPU0 has changed and the display is showing on another GPU that I am not connected to. If possible (open air rig), you could try connecting your monitor to the other GPUs until you find it. Or, if you are on 19-2.0, you can use the nvOC utility's gpumap function to find it:


Hope this helps.