PupSysInfo-2.8.6

[bigpup]

bigpup,

To show total RAM and all prefetchable RAM on one single line, could you test the attached func file.

Thanks

Here is what I get with this new func file.

VGA controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1)
• Kernel Driver: nvidia
• Memory Used by Driver: 16108.00 KB
• Path: /lib/modules/4.19.12/kernel/drivers/video/nvidia.ko
• Driver Version: 410.78
• Description: N/A
• Video RAM: 8192 M total, 256M 32M prefetchable

[radky]

Here is what I get with this new func file.

• Video RAM: 8192 M total, 256M 32M prefetchable

Thank you!

[radky]

Pup-SysInfo-2.8.5
- Adjust CPU report: switch from dmidecode to direct parsing of /sys/devices for Min/Max Speed, and /proc/cpuinfo for assessment of Core Count and 64-bit capability
- Adjust Video report: call glxinfo to assess total video memory, and lspci to determine prefetchable video memory

[foxpup]

On the same Optimus machine, I have tried PupSysInfo in Slacko64-6.3.2.
This is what it gives for display device:

====> Video <====

Display Specifications:
+ Screen Dimensions: 1920x1080 pixels (341x191 millimeters)
+ Screen Depth: 24 bits (planes)

Xorg Startup Log (/var/log/Xorg.0.log):
+ Xorg Driver in use: intel
+ Loaded Modules: dbe ddc extmod fb fbdevhw glx int10 kbd mouse shadow vbe vesa
+ X.Org version: 1.14.3

OpenGL 2D/3D Rendering:
+ Direct Rendering: Yes
+ Vendor: Mesa Project
+ Renderer: Software Rasterizer
+ Version: 2.1 Mesa 9.1.7

VGA compatible controller:
+ Intel Corporation Device 1916 (rev 07)
+ Video RAM: 256M prefetchable

I have tried both the original 2.6.3 version and 2.8.5, same result.

[radky]

On the same Optimus machine, I have tried PupSysInfo in Slacko64-6.3.2.

+ Video RAM: 256M prefetchable

Hi foxpup,

PupSysInfo-2.8.5 calls glxinfo to show video memory as part of the extended renderer information defined by GLX_MESA_query_renderer (if supported).

In legacy slacko64-6.3.2, glxinfo does not show extended renderer information, so total VRAM does not appear in the video report of PupSysInfo.

[foxpup]

Hi radky

Thanks for explaining.
I already thought it has to do with other version of glxinfo and/or lspci.
Just thought it was good to mention though.

PupSysInfo is a supertool! Like many others from your hand.

[radky]

Pup-SysInfo-2.8.6
- Add support for detection of lm85 chipsets in sensors report (assuming kernel support for same)
- Adjust compatibility with recent changes in Woof-CE -- properly parse WOOF_VERSION and os-release in Distro Specs report

[puppy_apprentice]

PSI shows always the same current (MAX) speeds for both cores.
FST shows always various current speeds (see screenshot).

So my question is why PSI is showing those values. Is options like eg. Mainboard/CPU or Devices/Sensors are consuming so much CPU power or those values are collected once when PSI starts?

[radky]

PSI shows always the same current (MAX) speeds for both cores.
FST shows always various current speeds (see screenshot).

@puppy_apprentice,

The code for assessing CPU 'core speed' is similar in PupSysInfo and wcpufreq (a.k.a CPU Frequency Scaling Tool).

However, PupSysInfo also integrates the 'core speed' with dmidecode data and this may add slightly to the overall CPU load as the report is generated. Possibly, for entry-level processors such as your Celeron N3050, generating the report may result in a transient spike to maximum cpu frequency.

[puppy_apprentice]

OK. I was afraid that powersafe governor not working.