home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.suse      Suse is actually not that bad      138,051 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 136,816 of 138,051   
   Carlos E.R. to All   
   Re: GKrellM question   
   27 Jul 19 05:02:38   
   
   From: robin_listas@es.invalid   
      
   On 27/07/2019 04.00, Sidney_Kotic wrote:   
   > On 7/26/19 2:45 PM, Carlos E.R. wrote:   
   >> Hi,   
   >>   
   >> I use gkrellm   
   >   
   > Hi Carlos,   
   > I downloaded it and have no solutions for you.   
   > But I do have a question.   
   >   
   > This machine can get hot.  On my dimwitted Raspberries I wrote a simple   
   > script to check the temperature every so often and email me if things   
   > started getting hot.  In a worse case scenario, where I don't resolve   
   > it, they shut the critter down after a certain amount of time.  They   
   > just sit there 24X365 and run boinc, but fans fail, plus I'm gone for   
   > probably close to 6 months out of the year. I'd like to duplicate that   
   > on the INTEL/AMD machines, for the all the same reasons.   
   >   
   > Do you, or anyone else, know of a way to check the processor temperature   
   > via a script?   
      
   I can think of it. But it is CPU dependent.   
      
   [...]   
      
   I think I have seen something in /proc or /sys. But, there is the   
   command "sensors", which prints output:   
      
   Telcontar:~ # sensors   
   coretemp-isa-0000   
   Adapter: ISA adapter   
   Core 0:       +69.0°C  (high = +74.0°C, crit = +100.0°C)   
   Core 1:       +60.0°C  (high = +74.0°C, crit = +100.0°C)   
   Core 2:       +62.0°C  (high = +74.0°C, crit = +100.0°C)   
   Core 3:       +65.0°C  (high = +74.0°C, crit = +100.0°C)   
      
   f71882fg-isa-0a00   
   Adapter: ISA adapter   
   +3.3V:        +3.36 V   
   in1:          +1.23 V  (max =  +2.04 V)   
   in2:          +0.31 V   
   in3:          +2.04 V   
   in4:          +0.95 V   
   in5:          +1.09 V   
   in6:          +0.40 V   
   3VSB:         +3.30 V   
   Vbat:         +3.23 V   
   fan1:         960 RPM   
   fan2:        1199 RPM   
   fan3:         791 RPM   
   fan4:           0 RPM  ALARM   
   temp1:        +62.0°C  (high = +85.0°C, hyst = +81.0°C)   
                          (crit = +100.0°C, hyst = +96.0°C)  sensor =   
   transistor   
   temp2:        +39.0°C  (high = +85.0°C, hyst = +81.0°C)   
                          (crit = +100.0°C, hyst = +96.0°C)  sensor =   
   transistor   
   temp3:          FAULT  (high = +70.0°C, hyst = +68.0°C)   
                          (crit = +85.0°C, hyst = +83.0°C)  sensor = transistor   
      
   Telcontar:~ #   
      
   Try other options, such as "sensors -u".   
      
      
   From that, you can build a script that calls it periodically and parse   
   some output. Or a cronjob.   
      
   And the first time, use "sensors-detect" to find the available sensors   
   in the machine.   
      
   >   
   > Thanks.  BTW, thanks again for all your help.  The last kernel upgrade   
   > took care of my video problem, except of the silliness caused by the   
   > nvidea card and the error message:   
   > libGL error: unable to load driver: nouveau_dri.so   
   > But at least I'm running a current kernel, again, and up to date on   
   > patching.   
      
   Ok :-)   
      
   --   
   Cheers, Carlos.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca