PupSysInfo-2.8.6

Message

oldaolgeezer · #101 Post by **oldaolgeezer** » Sat 26 Jan 2019, 19:26

bigpup and puppy_apprentice and radky:

When I looked in Pup-Sysinfo version 2.8 func script file:
/usr/local/Pup-SysInfo/func, as opposed to
my slacko 5.7.0 Pup-Sysinfo version 2.7.3 func, it looks like
there is special code for getting the CPU frequency from a different
directory location if the kernel version is newer than 4.13:
the Pup-Sysinfo version 2.8 func seems to look by using:
sed 's/...$//' /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq
but for older kernels, seems to look by using:
grep -a 'MHz' /proc/cpuinfo | awk '{print $4}' | cut -d '.' -f1

A little further on in the Pup-Sysinfo version 2.8 func code, the displayed
CPU value looks like it only displays the CPU frequency values that
were plugged in by the newer than 4.13 kernel version's code.

People that are better script coders than me should examine this further
(It might be an easy fix.)

bigpup · #102 Post by **bigpup** » Sun 27 Jan 2019, 01:03

radky wrote:
bigpup wrote:Sometime after version 2.7.3
Pup-Sysinfo stopped showing speed for each core in a CPU.

Tried with version 2.8.2
@bigpup,

May I assume you tested PSI 2.7.3 and 2.8.2 in your N2840 PC while using Bionicpup64 7.9.8 CE RC with kernel 4.19.12 ?

Thanks

Sorry

Yes, all were run in Bionicpup64 7.9.8 CE RC with kernel 4.19.12

I noticed puppy_apprentice's posted image shows CPU max speed.
Not shown in the Pup-Sysinfo's I tried.
Could be a CPU thing, but would seem a N3050 is not that different from a N2840.

perdido · #103 Post by **perdido** » Sun 27 Jan 2019, 01:16

bigpup wrote:Sometime after version 2.7.3
Pup-Sysinfo stopped showing speed for each core in a CPU.

Tried with version 2.8.2

Version 2.8.1 from upupbb 18.05 shows cpu speed

bigpup · #104 Post by **bigpup** » Sun 27 Jan 2019, 01:28

Pup-Sysinfo 2.8.1 is in Bionicpup64 7.9.8
It does not show each core speed for me.

Using Bionicpup64 7.9.8
I tried Pup-Sysinfo V2.8.1 in another computer.
Different CPU.
I get this info.

bigpup · #105 Post by **bigpup** » Sun 27 Jan 2019, 01:40

deleted.

radky · #106 Post by **radky** » Sun 27 Jan 2019, 03:43

bigpup wrote:Sometime after version 2.7.3
Pup-Sysinfo stopped showing speed for each core in a CPU.

@bigpup, puppy_apprentice, oldaolgeezer, perdido, or other users

As time permits, please test the revised function file below.

Remove the fake gz extension and place the file as follows: /usr/local/Pup-SysInfo/func. Make file executable.

Thanks

EDIT: test file removed. Please see post below for current release of PupSysInfo.

http://murga-linux.com/puppy/viewtopic. ... 411#579411

gyro · #107 Post by **gyro** » Sun 27 Jan 2019, 04:10

When I boot Bionicpup64 7.9.8 CE RC with the boot parameter "intel_pstate=disable", PupSysInfo shows the speed of each core.
When I boot Bionicpup64 7.9.8 CE RC without the boot parameter "intel_pstate=disable", PupSysInfo does not show the speed of each core.

gyro

perdido · #108 Post by **perdido** » Sun 27 Jan 2019, 05:53

radky wrote:
bigpup wrote:Sometime after version 2.7.3
Pup-Sysinfo stopped showing speed for each core in a CPU.
@bigpup, puppy_apprentice, oldaolgeezer, perdido, or other users

As time permits, please test the revised function file below.

Remove the fake gz extension and place the file as follows: /usr/local/Pup-SysInfo/func. Make file executable.

Thanks

Hi radky, No changes in my upupbb-18.05 system with Pupsysinfo-2.8.1
Works and provides the same data, all good.

I notice a difference between Freq. scaling driver of my system and bigpup's.
Mine is using Freq. scaling driver : acpi-cpufreq
bigpup is using Freq. scaling driver intel_pstate , the same as gyro and has the same problem with the intel_pstate driver enabled
that gyro references and supplies the fix for.

This thread about frequency scaling problems with intel_pstate seems related.
Xenialpup 7.5 32&64 bit cpu frequency scaling not working

.

bigpup · #109 Post by **bigpup** » Sun 27 Jan 2019, 07:20

As time permits, please test the revised function file

Using Pup-Sysinfo 2.8.2
That file change fixed it for my computer.

bigpup · #110 Post by **bigpup** » Sun 27 Jan 2019, 07:24

Now I wonder about intel_pstate, after seeing what is being posted about it.

When I boot Bionicpup64 7.9.8 CE RC with the boot parameter "intel_pstate=disable", PupSysInfo shows the speed of each core.
When I boot Bionicpup64 7.9.8 CE RC without the boot parameter "intel_pstate=disable", PupSysInfo does not show the speed of each core.

Well, that worked for me also.

Pup-Sysinfo 2.8.2
Right now I am using "intel_pstate" with the new func file.
it also works to let all cores show speed.

Having fun radky?

Nothing has an affect on showing CPU max speed.
Still not showing that.

gyro · #111 Post by **gyro** » Sun 27 Jan 2019, 14:04

In Bionicpup64 7.9.8, I replaced the installed "func" file with the new one.

This seems to have fixed the issue for my machine.
I now get "Max speed" and "Current Speed of Core" for each core using either "acpi-cpufreq" or "intel_pstate".

Not sure if it's relevant, my CPU is an Intel i3.

gyro

Marv · #112 Post by **Marv** » Sun 27 Jan 2019, 15:06

Tested with func replacement in LxPupSc 19.01 +1 running the 4.20.4 64b kernel. PupSysInfo-2.8.1 in this pup. With either the intel_pstate or the acpi_cpufreq governors running, both the maximum cpu speed and the current core speeds are displayed correctly.

Code: Select all

▶—— CPU ——◀

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

Frequency governor   : conservative
Freq. scaling driver : acpi-cpufreq

Code: Select all

▶—— CPU ——◀

Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz
Socket Designation: Onboard
Manufacturer: Intel(R) Corporation
Voltage: 1.2 V
External Clock: 100 MHz
Max Speed: 2500 MHz
Current Speed of Core 0:925 MHz, 1:961 MHz, 2:870 MHz, 3:1387 MHz
Core Count: 2
Thread Count: 4
64-bit capable

Frequency governor   : powersave
Freq. scaling driver : intel_pstate

radky · #113 Post by **radky** » Sun 27 Jan 2019, 19:29

@bigpup, puppy_apprentice, oldaolgeezer, perdido, gyro, Marv:

Thanks for your reports. Very much appreciated!

---

bigpup wrote:Nothing has an affect on showing CPU max speed.
Still not showing that.

PupSysInfo calls the dmidecode tool (DMI table decoder) to extract information about the system's hardware components including CPU maximum speed.

Code: Select all

dmidecode -t 4 | grep 'Max Speed'

Alternatively, you could try the lscpu tool which provides information about CPU speed.

Code: Select all

lscpu | grep 'CPU max'

If the dmidecode and lscpu utilities do not define CPU maximum speed, possibly your processor is not supported.

puppy_apprentice · #114 Post by **puppy_apprentice** » Sun 27 Jan 2019, 20:18

Your last patch and

Code: Select all

intel_pstate=disable

as kernel option works.

bigpup doesn't see max speed of cores i see wrong speed for my N3050:

The boost speed on the N3050 goes up to 2.16GHz, while the N3060 can go up to 2.48GHz.

https://laptoping.com/cpus/product/intel-celeron-n3050/

PSI shows 2400Mhz.

will check this later in Bionic:

Code: Select all

lscpu | grep 'CPU max'

Tried in Xenial but there is not lscpu command. I've tried to download pet with util-linux but got errors.

BTW. On bigpup PSI picture i see speed of 2 cores, but max cores value is 16. Is this count hyperthreading (virtual cores?)

bigpup · #115 Post by **bigpup** » Sun 27 Jan 2019, 22:57

I think some of this is dealing with different CPU's.

BTW. On bigpup PSI picture i see speed of 2 cores, but max core count value is 16. Is this count hyperthreading (virtual cores?)

That 16 number seems to me to be very wrong.
At most it should be 4.

intel_pstate=disable may not be something you really want to do.

Found this added info about it.
intel_pstate offers only two governors: powersave and performance.

1. intel_pstate can be disabled at boot-time with intel_pstate=disable or compile it out
2. the old problem with ondemand (and conservative) governors is and was, that they don't know the specific capabilities of the cpu
3. executing some tasks with highest-frequency possible is consuming less power, than taking more time with lower frequency e.g. arithmetic stuff
4. this is not true for all tasks e.g. loading something from main-memory
5. here comes intel_pstate: it knows how the specific cpu works and does it job better than a generic solution, also it seems to handle "boost" better
6. furthermore intel_pstate offers only two governors: powersave and performance
even "powersave" is faster than the generic acpi based approach with "performance" (maybe handles "boost" better)
also "performance" doesn't enforce the default frequency as "lower limit", like the old generic approch, but performance is anyway only ~ 1% faster

puppy_apprentice · #116 Post by **puppy_apprentice** » Sun 27 Jan 2019, 23:36

I've found that info:

intel_pstate is a part of the CPU performance scaling subsystem in the Linux kernel (CPUFreq). It is a scaling driver for the Sandy Bridge and later generations of Intel processors. Note, however, that some of those processors may not be supported.

source:
https://www.kernel.org/doc/html/v4.12/a ... state.html

I wonder if my N3050 is suported by intel_pstate. Have tried to ask uncle Google but without any result.

radky · #117 Post by **radky** » Mon 28 Jan 2019, 00:00

puppy_apprentice wrote:bigpup doesn't see max speed of cores i see wrong speed for my N3050

As noted in a prior post above, PupSysInfo uses the dmidecode tool to probe the system BIOS for information about PC hardware including CPU capabilites.

Information in the BIOS is provided by the system manufacturer and the reliability of this information may vary depending on the manufacturer. In other words, sometimes incorrect information in the dmidecode report is due to faulty BIOS information provided by the manufacturer.

bigpup · #118 Post by **bigpup** » Mon 28 Jan 2019, 02:25

No there is just no way that could happen!

Well this is a Chromebook I am using.
I am sure the bios is not very good at providing info on hardware.

I am just happy Puppy Linux will boot on it.

I tried lscpu | grep 'CPU max'

root# lscpu | grep 'CPU max'
CPU max MHz: 2167.0000

So that gives the CPU max speed.

radky · #119 Post by **radky** » Mon 28 Jan 2019, 20:32

Pup-SysInfo-2.8.3
- Bugfix: In some scenarios, failed detection of CPU speed when the frequency scaling driver is intel_pstate (thanks puppy_apprentice and bigpup)

puppy_apprentice · #120 Post by **puppy_apprentice** » Mon 28 Jan 2019, 22:34

Thx radky.

Maybe now off-topic but have made some more tests in Bionic:

Code: Select all

lscpu | grep "CPU MHz\|CPU max\|CPU min"

acpi_cpufreq_ondemand (read from BIOS: Power Technology: Energy Efficient, picture CPU1):

Code: Select all

CPU MHz:             943.009
CPU max MHz:         1601.0000
CPU min MHz:         480.000

intel_pstate_powersafe (BIOS: Power Technology: Energy Efficient):

Code: Select all

CPU MHz:             2024.458
CPU max MHz:         2160.0000
CPU min MHz:         480.0000

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

PupSysInfo-2.8.6

PupSysInfo-2.8