Testers for inxi/pinxi redone -C CPU logic... huge internal changes

[Condobloke]

Thanks Stan !

I have edited my post above to show output from :

inxi -MCazy80

and

pinxi -MCazy1

to upgrade pinxi....run pinxi -U
returned,

[email protected]:~$ pinxi -U
Error 48: The file: pinxi is not writable!

 

[stan]

[email protected]:~$ pinxi -U
Error 48: The file: pinxi is not writable!

Oops! I think that needs sudo. I corrected my post above.

sudo pinxi -U

 

[Condobloke]

[email protected]:~$ sudo pinxi -U
[sudo] password for brian:
Starting pinxi self updater.
Using tiny as downloader.
Currently running pinxi version number: 3.3.09
Current version patch number: 10
Current version release date: 2021-11-26
Updating pinxi in /usr/local/bin using inxi-perl branch as download source...
Validating downloaded data...
Successfully updated to inxi-perl branch version: 3.3.09
New inxi-perl branch version patch number: 10
New inxi-perl branch version release date: 2021-11-26
To run the new version, just start pinxi again.
----------------------------------------

Skipping man download because branch version is being used.
[email protected]:~$

 

[Condobloke]

and after upgrade of pinxi..

[email protected]:~$ inxi -MCazy80
Machine:
Type: Desktop Mobo: ASRock model: B150M Pro4 serial: <filter>
UEFI: American Megatrends v: P1.60 date: 11/09/2015
CPU:
Topology: Dual Core model: Intel Pentium G4400 bits: 64 type: MCP
arch: Skylake-S family: 6 model-id: 5E (94) stepping: 3 microcode: EA
L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 13199
Speed: 3300 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 3300 2: 3300
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: disabled, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
[email protected]:~$ pinxi -MCazy1
Machine:
Type: Desktop
Mobo: ASRock
model: B150M Pro4
serial: <superuser required>
UEFI: American Megatrends
v: P1.60
date: 11/09/2015

CPU:
Info: Dual Core
model: Intel Pentium G4400
bits: 64
type: MCP
arch: Skylake-S
family: 6
model-id: 5E (94)
stepping: 3
microcode: EA
cache:
L1: 128 KiB
desc: d-2x32 KiB; i-2x32 KiB
L2: 512 KiB
desc: 2x256 KiB
L3: 3 MiB
desc: 1x3 MiB
flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 6599
Speed (MHz):
avg: 3300
min/max: 800/3300
cores:
1: 3300
2: 3300
Vulnerabilities:
Type: itlb_multihit
status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
Type: mds
mitigation: Clear CPU buffers; SMT disabled
Type: meltdown
mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling
Type: srbds
mitigation: Microcode
Type: tsx_async_abort
status: Not affected

[email protected]:~$

 

[h2-1]

CPU:
Info: Single Core model: Intel Atom N270 bits: 32 type: MT arch: Bonnell
family: 6 model-id: 1C (28) stepping: 2 microcode: 218 L2 cache: 512 KiB
flags: pae sse sse2 sse3 ssse3 bogomips: 6383

This is really great stuff, fantastic, bugs / failures to check:
Can you run these commands and paste the output somewhere:

for i in $(ls /sys/devices/system/cpu/{cpu*/topology,cpu*/cpufreq,cpu*/cache/index*,smt}/*);do echo -n "$i::";cat $i;done > cpu-sys.txt
cat /proc/cpuinfo > cpuinfo.txt

or just use

pinxi --debug 22 --debug-id brickwizard

to generate the full debugger dataset which will upload automatically if you prefer.

I have seen some other L1 cache failures, and want to see if I missed a possible syntax for L1 cache types.

 

[Brickwizard]

Can you run these commands and paste the output somewhere:

not tonight, I am still trying to get my 20 yr old acer to work with a usb [the main drive i think may be shot... will do it tomorrow

 

[KGIII]

I'm going to go ahead and sticky this thread for a few days. Given my current state of ill health, I'm going to also ping @wizardfromoz who may remember to unstick the thread should I forget.

 

[Brickwizard]

Given my current state of ill health

take things easy pal..

 

[KGIII]

take things easy pal..

Thanks. I'll be fine. My assumption is I picked it up over the holiday. I've been in worse shape and won't derail the thread. I'll survive. Only the good die young.

 

[stan]

Given my current state of ill health

Get well soon!

 

[Brickwizard]

this is from my 2000 acer [21 yrs old on Christmas eve]
[email protected]:/usr/local/bin$ inxi -MCaxy88
Machine:
Type: Laptop System: Acer product: TravelMate 2410 v: 0100 serial: <root required>
Mobo: Acer model: Morar v: Rev serial: <root required> BIOS: Phoenix v: 1.07
date: 09/26/2005
CPU:
Topology: Single Core model: Intel Celeron M bits: 32 type: MCP arch: M Dothan
family: 6 model-id: D (13) stepping: 8 microcode: 20 L2 cache: 1024 KiB
flags: pae sse sse2 bogomips: 2992
Speed: 1496 MHz min/max: N/A Core speed (MHz): 1: 1496
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf status: Vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: tsx_async_abort status: Not affected

[email protected]:/usr/local/bin$ pinxi MCazy1
bash: /usr/local/bin/pinxi: Permission denied
[email protected]:/usr/local/bin$ sudo pinxi -
sudo: pinxi: command not found
[email protected]:/usr/local/bin$ sudo pinxi -MCazy1
sudo: pinxi: command not found
[email protected]:/usr/local/bin$ pinxi -MCay1 --force cpuinfo
bash: /usr/local/bin/pinxi: Permission denied

 

[stan]

[email protected]:/usr/local/bin$ pinxi MCazy1
bash: /usr/local/bin/pinxi: Permission denied
[email protected]:/usr/local/bin$ sudo pinxi -
sudo: pinxi: command not found
[email protected]:/usr/local/bin$ sudo pinxi -MCazy1
sudo: pinxi: command not found
[email protected]:/usr/local/bin$ pinxi -MCay1 --force cpuinfo
bash: /usr/local/bin/pinxi: Permission denied

Hmmm, what's happening, Brian? You shouldn't need sudo to run pinxi (but you do to install or upgrade it). Did you 'chmod +x' it? Or did you install with the full string:

cd /usr/local/bin && sudo wget -O pinxi smxi.org/pinxi && sudo chmod +x pinxi

 

[Brickwizard]

did you install with the full string:

copy and paste full string.. I have put it away for tonight, nearly time for old wizards to rest their bones. oh and i gave sudo a try as first try was permission refused, I managed to force Mint lmde 32 bit to load on it after trying 8 other distributions [busy afternoon evening]

 

[stan]

Okay, rest well... sounds like a productive day! I've been doing about the same thing here all day. Some of these computers I have are going to find a new home soon, I hope.

I think you've won the 'oldest computer' contest so far!

 

[wizardfromoz]

Given my current state of ill health, I'm going to also ping @wizardfromoz who may remember to unstick the thread should I forget.

In good hands (well, my hands, anyway), get well from Revenge of the Turkey soon, David.

 

[Condobloke]

you mean this turkey....?

 

[Brickwizard]

sorry no pinxi.. unless you can suggest a way round this

[email protected]:~$ cd /usr/local/bin && sudo wget -O pinxi
@stan No luck on the old acer



smxi.org/pinxi && sudo chmod +x pinxi
[sudo] password for wizard:
--2021-11-29 07:15:07-- http://smxi.org/pinxi
Resolving smxi.org (smxi.org)... 216.92.30.83
Connecting to smxi.org (smxi.org)|216.92.30.83|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://smxi.org/pinxi [following]
--2021-11-29 07:15:07-- https://smxi.org/pinxi
Connecting to smxi.org (smxi.org)|216.92.30.83|:443... connected.
ERROR: The certificate of ‘smxi.org’ is not trusted.
ERROR: The certificate of ‘smxi.org’ has expired.
[email protected]:/usr/local/bin$ pinxi -MCazy
bash: /usr/local/bin/pinxi: Permission denied
[email protected]:/usr/local/bin$ pinxi -MCazy1
bash: /usr/local/bin/pinxi: Permission denied
[email protected]:/usr/local/bin$
[email protected]:~$ sudo pinxi -U
[sudo] password for wizard:
sudo: pinxi: command not found
[email protected]:~$

 

[Brickwizard]

I think you've won the 'oldest computer'

it may be old and the battery knackerd, and slow to start the OS but it runs great for its age , a few tweaks needed at some point but no rush
edit.. mint lmd 32 bit runs fine but wont update so today will swap it to debian 11 32 bit, so no more on this forum for a couple of hours

 

[h2-1]

brickwizard, I have the same ssl issue when updating pinxi on my debian 5, pentium mmx, certificates are out of date.

To get around this, you can use this to install pinxi the first time:

Note the different url, this is my server, not the redirect to github, which this doesn't work for:

cd /usr/local/bin && sudo wget -O pinxi --no-check-certificate smxi.org/in/pinxi && sudo chmod +x pinxi

pinxi can then be updated whenever you want like so:

sudo pinxi -U 3 --no-ssl

All old operating systems will have old expired cerfificates, and github won't let you connect with those, but my server doesn't care. -U 3 means update from my server, not the redirect to github.

pinxi is updated every night from github to my server, so that version is usually up to date unless being actively developed, then I use a small local tool to instantly update it using rsync, that helps. I use -U 3 usually because github has an annoying tendency to throttle commits and make you wait after the 3rd or 4th quick commit, so -U 3 gets around that by bypassing github completely.

Note I couldn't get to anything today but will check in here tomorrow, had to fix a ton of stuff from user data that showed a lot of issues, some issues remain unfortunately with cache detection, but many issues have been resolved today, so make sure to get the latest pinxi!

 

[Brickwizard]

@h2-1
I have wiped the travelmate now, just waiting for Deb 11 to download on the main computer..its been at it nearly an hour and only downloaded 10% so it will be later today before its back up and running,