Newer CPU temperature display

[ozsouth]

Version 3 released (hopefully final):

- Uninstall other cpu temperature programs (if any), then install v3 version (32 or 64 bit).
- Keep sensors .pet if installed or install appropriate version (see below). Then restart X.
- If no valid module found, gives error message & exits program whereas v2 showed zero & kept running.
- Has more efficient code & anyone can change inputs/outputs by editing /usr/bin/cpucurtemp.sh
[Thankyou pre-testers - this is slightly different from the v2u1 test files.]

NOTES: Program checks the CPU raw temps 1-5 & reports the highest temperature (checks up to 4 cores). Refreshes every 5 seconds & re-starts every hour to mitigate small memory leak. Clicking/hovering on taskbar icon shows CPU frequencies. Tested in several pups on different pcs. Run at own risk.
This program by default utilises the common modules for AMD (k10temp) and Intel (coretemp) - used in machines made after 2011 (& some before). If no usable modules available, displays error message 'CPUCURTEMP FAILED' - i.e. not working for you. May be possible to find a usuable module, but some boards just aren't capable.

If it doesn't work for you (i.e. you have an old PC) you need to know what module is used for temperature - i.e. k8temp or it87 or lm85 or w83627hf or smsc47b397 or adt7463 or atk0110 ... etc.
If you have the appropriate sensors .pet loaded, can install (at own risk) sensors-detect-min .pet & in terminal run: sensors-detect-min
This should tell you what module is needed & opening screen detects CPU - AMD or Intel.
For AMD - edit 2nd line of /usr/bin/cpucurtemp.sh to list your module (replacing k10temp) & reboot (saving session).
For Intel - edit 3rd line of /usr/bin/cpucurtemp.sh to list your module (replacing coretemp) & reboot (saving session).

[bigpup]

Thanks for this!

Installed in Bionicpup64 8.0
Had to install both the cpucurtemp64.pet and the sensors64u.pet.

in a terminal run sensors -Will tell you what module is being used - i.e. k8temp or it87 or w83627hf or smsc47b397 etc.

I am not seeing this info.
This is what I get when run sensors in terminal:

Code: Select all

root# sensors
nouveau-pci-0100
Adapter: PCI adapter
fan1:        1123 RPM
temp1:        +41.0°C  (high = +95.0°C, hyst =  +3.0°C)
                       (crit = +105.0°C, hyst =  +5.0°C)
                       (emerg = +135.0°C, hyst =  +5.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +37.0°C  (high = +84.0°C, crit = +100.0°C)
Core 0:        +31.0°C  (high = +84.0°C, crit = +100.0°C)
Core 1:        +34.0°C  (high = +84.0°C, crit = +100.0°C)
Core 2:        +26.0°C  (high = +84.0°C, crit = +100.0°C)
Core 3:        +27.0°C  (high = +84.0°C, crit = +100.0°C)

root#

[ozsouth]

@bigpup - second para says that sensors test should only be run if the display doesn't work - i.e. you have an older PC which could use one of several modules. Glad you ran it, as I took a shortcut based on laptops I could access & yours has a different output again (man this is tricky!). Yours uses 'coretemp' (as do all intel) & would show 37 C based on your screeny, using the 'Package id' figure, instead of 'Core 0' which all PCs I tested use. Does that display value change?

[bigpup]

I have an Intel processor.
i5 6400
Changed to the updated version of cpucurtemp64.
It now seems to follow what the core 0 is doing.

That is some strange download counts for those pet packages.
You would think, they would all be close to each other, for the number of downloads.
Could just be the forum download counter not doing a very good job!

[peebee]

Should these pets find their way to the official repositories so they can be included in woof-ce builds??

Are they common to all pups - and can they go into common32 and common64?

Could the sensors pets be made common by detecting which pup variant they were running on and adapting accordingly?

(pmcputemp is currently build specific........)

[rufwoof]

My tray temp seems to align with

Code: Select all

cat /sys/class/thermal/thermal_zone*/temp

[ozsouth]

LIKELY UPDATE COMING.

[ozsouth]

Version 2 released - SEE FIRST POST. (Thanks to pre-testers - is different from test v2).

[Marv]

I am running version 2 in LxPupSc 19.01 +6 with the lxpup 5.04 64b kernel. The hardware is:

Code: Select all

System:    Host: puppypc21956 Kernel: 5.0.4-lxpup64 x86_64 (64 bit) Desktop: LXDE (Openbox 3.6.1)
           Distro: LxPup-Sc 19.01
Machine:   Device: laptop System: FUJITSU product: LIFEBOOK S761 serial: R2500459
           Mobo: FUJITSU model: FJNB225 UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.17 date: 03/14/2012
Battery    CMB1: charge: 56.0 Wh 100.0% condition: 56.0/56.0 Wh (100%)
CPU:       Dual core Intel Core i5-2520M (-HT-MCP-) speed/max: 1084/3200 MHz
Graphics:  Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller
           Display Server: X.org 1.20.4 drivers: intel (unloaded: modesetting,vesa) FAILED: fbdev
           tty size: 134x32 Advanced Data: N/A for root
Network:   Card: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) driver: ath9k
Drives:    HDD Total Size: 120.0GB (35.6% used)
Weather:   Weather data failure: Fri Mar 29 17:35:00 CDT 2019
           Error: weather info downloaded but no data detected.
Info:      Processes: 160 Uptime: 2 days Memory: 401.4/3780.4MB Client: Shell (bash) inxi: 2.3.8 

There is a noticeable difference between the CPU usage reported at idle between v1 and v2. I have rechecked several times and have tried to keep all the relevant parameters the same. The pup is running the intel_pstate powersave governor. I also will include the output of PupSysInfo below, again as near to idle as I can make things:

Code: Select all

Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
Socket Designation: Onboard
Manufacturer: Intel(R) Corporation
Voltage: 1.2 V
External Clock: 100 MHz
Min/Max Speed: 800/3200 MHz
Current Speed of Core 0:826 MHz, 1:962 MHz, 2:867 MHz, 3:809 MHz
Core Count: 2
Thread Count: 4
64-bit capable: yes

Version 1 seems to fall pretty close (but not exact) to the PupSysInfo values and also to what I have observed over a long period of time with pmcputemp. Offered in the spirit of testing.

Cheers,

[ozsouth]

Thanks Marv - appreciate feedback. Would you mind posting output of sensors -u
Will tell me what v2 is picking up. It should be more accurate, as v1 only picked up the first core - often not the highest.

[ozsouth]

Version 3 (hopefully final) is released - see first post

[ahoppin]

Unfortunately this isn't working for my system. It's an Asus M2N68-AM+ board, 2gb core. I'm running Bionic-32 8.0.

EDIT: The processor is an AMD Phenom 8550 3-core.

The sensors-detect-min utility identifies the temp sensor as an it87, but replacing the original module in cpucurtemp.sh with that one didn't help.

EDIT: the chip is detected as an IT8712F.

After editing cpucurtemp.sh, when I start cpucurtemp from a console, I get:

CODE:
modprobe: ERROR: could not insert 'it87' : Device or resource busy
Specified sensor(s) not found!
(above line repeated 4 more times)
Terminated
END-CODE

The default Bionic pmcputemp doesn't work.

pmcputemp version 0.63a from here

http://www.murga-linux.com/puppy/viewto ... 76#1008276

(installed after removing the default pmcputemp)

also fails with this message:

CODE:
Failed to find file
Unable to create configuration file.
END-CODE

An interesting discovery:

The ancient CPUtemp-1.7.pet utility, which I've used for 5 years on Lucid 5.2.5, works perfectly as installed, without any tweaks, on this setup.

http://www.murga-linux.com/puppy/viewto ... 546#432546

It even reads the fan RPM correctly.

I haven't tried the updates to it yet - wasn't even aware that they existed.

EDIT: CPUtemp version 2.0 also works. Neither 1.7 nor 2.0 is able to read the CPU speed.

It would be nice to get pmcpmtemp or similar working, since the readout in the tray is nice to have, as is the red-icon "hot" warning.

Any thoughts? Suggestions?

Thanks!

[norgo]

@ahoppin

it87 oh yes I remember ( really a lot of years ago )
because of ACPI I/O resource conflicts
loading of the it87 module will prevented
you could try boot with parameter "acpi_enforce_resources=lax"
but to be honest this is not to recommend

Nice collection here

[enrique]

@ahoppin

Phenom are good CPU, but I guess they where on the FRONT of the war for AMD64 technology. So they are not perfect. You have an example, "AMD Phenom 8550 3-core" 3 cores because the 4th is defective. Point is this CPU has more in common with a heather than a CPU. That's a joke. So to hide that fact AMD was force to add a "quite" features. You can go to:
https://www.asus.com/Motherboards/M2N68AM_PLUS/
you can read about AMD Cool ´n´ Quiet! Technology & ASUS Q-Fan

So you should not be worry about controlling the fans on Linux. It has a fan control on the BIOS. I do not have that mother board but you should be able to find a Fan Control in the bios. Enable it. Ask it to Calibrate. In my own Motherboard, the Auto still to noise/High. So I set it to manual and Higher the temp set for the Fan to Turn and Start. I do not remember exactly mine I have it like 40 & 50 degrees Celcious. Then make sure Auto Shutdown is ON, I think I place it like in 90 or 100C, If you do not like it place it as High as you can but please set it ON. This can protect your CPU.

That's it. It will regulate your REALLY GOOD FAN, that is why it is noisy.


Regards sensors. ON LXDE the tray has its own default Temp Sensors that work on bionic. I bet you in jwm the tray should have it too. Se if that works.