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

h2-1 · 12-05-2021, 01:24 PM

truepatriot76, those look good, thanks.

fourtysixandtwo · 12-05-2021, 02:08 PM

Quote:

Originally Posted by h2-1

fourtysixandtwo, can you post your full /proc/cpuinfo from that system?

I'm not clear why the flags item is returning that error, that may be some unhandled value in the flags field.

Bogomips too.

Code:

# cat /proc/cpuinfo 
processor       : 0
vendor_id       : unknown
cpu family      : 4
model           : 0
model name      : 486
stepping        : unknown
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : no
cpuid level     : -1
wp              : yes
flags           :
bogomips        : 33.17

h2-1 · 12-05-2021, 02:52 PM

fourtysixandtwo, the error was my doing something dumb, that's corrected.

The bogomips was inxi not having seen a 486 cpu before and not believing it when it told it had 33.17 bogomips.

https://tldp.org/HOWTO/BogoMips/bogo-list.html

My slowest cpu is my pentium mmx which runs at a fairly blistering 200 MHz and 400 some odd bogomips.

Now pinxi will only disbelieve the bogomips count if it is a RISC type cpu, AND if it's less than 50 bogomips. That's because there is a common bug in cpuinfo for ARM that assigns a fairly comically low bogomips to the arm cpu, far too low to be real, so inxi rejected that out of hand always. I think I had just made the test general, and I think it was specific to arm before, so that's corrected.

Your example shows how important it is to show bogomips, another item I'd had doubts about the value of, because in your example,this is literally the only way to get any indication of how fast or slow the cpu actually is since it has no core speed listed.

Both of these issues are corrected in pinxi 3.3.09-31

I've also added your 486 cpuinfo to the permanent set of fake cpuinfo values so I can readily test changes to avoid this type of error in the future on updates or changes, since that is basically the least data inxi will see on an x86 type cpu in cpuinfo.

Code:

CPU:
  Info: single core model: 486 bits: 64 type: UP arch: N/A cache: N/A
  bogomips: 33
  Speed: N/A min/max: N/A core: No per core speed data found.
  Flags: N/A

PS, these are absolutely fantastic fringe/corner case hardware examples, exactly what I had hoped to get, but actually much much better than I had hoped for since these are going back further than I had expected, and of course, the less expected data there is, the higher the odds of tripping expected data being missing failures.

Note the 'bits:' item comes from my live system, so ignore that.

Out of curiousity, how long does: pinxi -zv8
take to run on that system? Can you paste the output of that?

It takes about 15 seconds on my Pentium MMX.

fourtysixandtwo · 12-05-2021, 04:11 PM

Quote:

Originally Posted by h2-1

Out of curiousity, how long does: pinxi -zv8
take to run on that system? Can you paste the output of that?

It takes about 15 seconds on my Pentium MMX.

h2-1, it's nice to put this old beast of a machine to use for something. The output requested is below and is the 2nd run. First run was about 6-7 seconds real time slower.

I'd have more old boxes to test but I pruned my collection about 8 years ago. This 486 is in a massive all black case ~25" tall and is SCSI so I had to keep it! Hard to believe it was an Image RIP that booted off just a floppy for about 7 years. It was retired shortly after I started that job. I then put slackware on it so I had a Linux workstation there. It had slackware 3.x until I upgraded it to 11 last year.

Code:

# time ./pinxi -zv8 --dmidecode
System:
  Kernel: 2.4.37 i486 bits: 32 compiler: gcc v: 3.4.6
  parameters: auto BOOT_IMAGE=custom-2.4.37 ro root=801
  Console: pty pts/0 Distro: Slackware 11.0.0
Machine:
  Smbios: No SMBIOS data for dmidecode to process
Battery:
  Smbios: No SMBIOS data for dmidecode to process
Memory:
  RAM: total: 29.3 MiB used: 19.1 MiB (65.2%)
  RAM Report: smbios: No SMBIOS data for dmidecode to process
PCI Slots:
  Smbios: No SMBIOS data for dmidecode to process
CPU:
  Info: single core model: 486 bits: N/A type: UP arch: N/A family: 4
  model-id: N/A microcode: N/A cache: N/A bogomips: 33
  Speed: N/A min/max: N/A core: No per core speed data found.
  Flags: N/A
  Vulnerabilities: No CPU vulnerability/bugs data available.
Graphics:
  Message: Device data requires root.
  Display: server: No display server data found. Headless machine?
  tty: 200x60
  Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
  Message: Device data requires root.
  Sound Server-1: OSS v: N/A running: yes
Network:
  Message: Device data requires root.
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Missing: Required tool lvs not installed. Check --recommends
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 4.99 GiB used: 1.52 GiB (30.6%)
  ID-1: /dev/sda maj-min: 8:0 model: N/A size: 1006.4 MiB type: N/A
  serial: N/A scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 model: N/A size: 2 GiB type: N/A serial: N/A
  scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 model: N/A size: 2 GiB type: N/A serial: N/A
  scheme: MBR
  Floppy-1: /dev/fd0
  Floppy-2: /dev/fd1
  Floppy-3: /dev/fd2
  Floppy-4: /dev/fd3
  Optical-1: /dev/scd0 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-2: /dev/scd1 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-3: /dev/scd10 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-4: /dev/scd11 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-5: /dev/scd12 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-6: /dev/scd13 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-7: /dev/scd14 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-8: /dev/scd15 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-9: /dev/scd2 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-10: /dev/scd3 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-11: /dev/scd4 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-12: /dev/scd5 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-13: /dev/scd6 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-14: /dev/scd7 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-15: /dev/scd8 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-16: /dev/scd9 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-17: /dev/sr0 vendor: N/A model: N/A rev: N/A dev-links: cdrom
  Features: speed: 40 multisession: yes audio: yes dvd: yes rw: none
  state: N/A
  Optical-18: /dev/sr1 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-19: /dev/sr10 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-20: /dev/sr11 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-21: /dev/sr12 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-22: /dev/sr13 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-23: /dev/sr14 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-24: /dev/sr15 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-25: /dev/sr2 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-26: /dev/sr3 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-27: /dev/sr4 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-28: /dev/sr5 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-29: /dev/sr6 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-30: /dev/sr7 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-31: /dev/sr8 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-32: /dev/sr9 vendor: N/A model: N/A rev: N/A dev-links: N/A
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
Partition:
  ID-1: / size: 899.9 MiB used: 122 MiB (13.6%) fs: ext3 dev: /dev/sda1
  maj-min: 8:1 label: N/A uuid: N/A
  ID-2: /iso size: 21.73 TiB used: 17.41 TiB (80.1%) fs: nfs
  remote: 192.168.1.10:/volume2/iso
  ID-3: /usr size: 1.94 GiB used: 1.4 GiB (72.4%) fs: ext3 dev: /dev/sdb1
  maj-min: 8:17 label: N/A uuid: N/A
Swap:
  Message: No admin swap data available.
  ID-1: swap-1 type: partition size: 235.3 MiB used: 1.3 MiB (0.6%)
  priority: -1 dev: /dev/sdc2 maj-min: 8:34 label: N/A uuid: N/A
Unmounted:
  ID-1: /dev/sda2 maj-min: 8:2 size: 77 MiB fs: swap label: N/A uuid: N/A
  ID-2: /dev/sdc1 maj-min: 8:33 size: 1.77 GiB fs: ext3 label: N/A uuid: N/A
USB:
  Message: No USB data found. Server?
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Repos:
  Packages: note: see --pkg pkgtool: 1
  slackpkg repos in: /etc/slackpkg/mirrors
  1: http://mirror.csclub.uwaterloo.ca/slackware/slackware-11.0/
Processes:
  CPU top: 5 of 34
  1: cpu: 94.3% command: perl pid: 582 mem: 12.4 MiB (42.3%)
  2: cpu: 0.0% command: init pid: 1 mem: 0.25 MiB (0.8%)
  3: cpu: 0.0% command: [keventd] pid: 2 mem: 0.00 MiB (0.0%)
  4: cpu: 0.0% command: [ksoftirqd_cpu0] pid: 3 mem: 0.00 MiB (0.0%)
  5: cpu: 0.0% command: [kswapd] pid: 4 mem: 0.00 MiB (0.0%)
  Memory top: 5 of 34
  1: mem: 12.4 MiB (42.3%) command: perl pid: 582 cpu: 94.3%
  2: mem: 1.68 MiB (5.7%) command: -su pid: 255 cpu: 0.0%
  3: mem: 1.57 MiB (5.3%) command: -sh pid: 245 cpu: 0.0%
  4: mem: 1.53 MiB (5.2%) command: sshd: pid: 244 cpu: 0.0%
  5: mem: 0.92 MiB (3.1%) command: sh pid: 587 cpu: 0.0%
Info:
  Processes: 34 Uptime: 3h 57m Init: SysVinit v: 2.84 runlevel: 3 default: 3
  tool: /etc/rc.d Compilers: gcc: 3.4.6 alt: 3.4.6 Shell: Bash v: 3.1.17
  running-in: pty pts/0 pinxi: 3.3.09-31

real    0m59.339s
user    0m45.220s
sys     0m4.870s

h2-1 · 12-05-2021, 04:27 PM

Wow, no errors, that's very good. I don't understand why it didn't get lspci data, I've tested on 2.4 kernels and they were largely fine, 2.2 kernels is where I see a real drop off in the data. Impressive you got 2 GiB drives running on that.

Looks like the error message slightly failed for dmidecode, that's because you forced --dmidecode use, which has no data since there is probably no dmi table on the system. But that message shouldn't have shown 'requires root', but dmidecode errors are the most complicated in inxi since there are so many possible variants of errors for the machine data parts in particular. Battery and Machine did show the right message, I'll have to check -G -A and -N to see what happened there.

What does lspci -nnv show?

I think some pattern there must have failed, I thought I'd gotten those all locked down but apparently not all variants are handled for those old kernels.

I'm surprised at what a tiny footprint slackware 11 takes on that system, on my pentium mmx laptop, running an ancient ibm server grade 1 GiB ssd, I think os takes about 667 MiB, but that's running X and fluxbox and some gui programs.

Execution time seems fairly in line with my pentium mmx proportionally speaking. Amazing to see it run without any errors, except for showing the wrong Device: error message for no data. Obviously wrong since you ran it as root, I'll take a look at that and see if I can figure it out, it might just be that lspci -nnv returned nothing so inxi assumed it needed root, not sure.

h2-1 · 12-05-2021, 04:36 PM

Double checked, lspci -n returned an error, and inxi just assumes if these standard commands are returning an error, it's a permissions error, however, it also knows that the user is root at that point so I will update that to 'unknown error' type case.

That one I can't fix however because can't do a simple is root test, that could be a BSD error for example where user needs to be in wheel group to run command, or whatever, not just root.

But looks like lspci -n is failing there, that's odd, I've tested this on 2.2 and 2.4 kernels and it worked without issues. But those are VMs, so that never reflects hardware reality correctly for this stuff.

fourtysixandtwo · 12-05-2021, 04:51 PM

No pci bus on this box, but I may have also disabled it in the custom kernel. I'll double check it.

I am running it as root so there won't be any permission issues.

Code:

# lspci -nnv
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

fourtysixandtwo · 12-05-2021, 04:59 PM

Yeah, didn't prune the kernel config much. Never actually tried lspci on a box with just an ISA bus before.

h2-1 · 12-05-2021, 05:42 PM

Oh, good, so no real issues. pinxi can't actually detect the real failure cause when it does its early tool testing, it just detects that there was a failure, and in this case, assumes it was permissions. ISA bus is fine, that's actually before inxi's time so not supporting that is ok. Important thing there was that it ran with no errors. That explains the lspci -n failure though. But this is a corner of a corner case, just an extreme test of pinxi/inxi handling of various platforms. Important thing there were no undefined value errors at all, which means everything was more or less correctly trapped and handled.

Thanks for confirming.

h2-1 · 12-05-2021, 05:53 PM

fourtysixandtwo

Quote:

Looks like I found bug. E7400 should be a Wolfdale socket 775

edit dmidecode does say Socket 423 while the pdf description of the box is correct with 775.

Almost forgot, that's a bug in the dmi data, inxi can't work around wrong data from that source since it has no other way to know.

You'd be surprised to see how much dmi data is simply wrong, that's because there are two types, one is actual real data from your running system, the other is strings vendors fill out, often wrong, that appears to be real data, but is actually gibberish that has to be tested for correctness.

pinxi/inxi -m is packed with logic and consistency and coherence tests because the general vendor dmi data for the ram arrays is often complete fiction, the per ram stick data is usually quite solid, but the information about the arrays themselves is I believe mostly filled out by oem, and they often just cut and paste in the same values for different boards. Inxi does verify that what is being supplied does not violate logic, and will attempt to correct that data if it does, but that's only possible because the per stick data is solid and can be used as a baseline.

Stuff like sockets there is no other data source, so if the vendor/oem filled out the table wrong, there's no way to fix it. You'd think after going through all the time, effort, and energy, to make a whole new motherboard, they'd spend the probably 10 minutes required to correctly fill out the dmi tables, but no, it seems all too often that work is handed off to some clearly overworked and probably underpaid person who saves time by just copy/pasting in the same values for the entire series. Weird to see such odd little lapses so routinely, again, you'd think someone would at some point actually take pride in their work, but all too often they don't, and just churn the stuff out.

slac-in-the-box · 12-05-2021, 06:31 PM

FWIW: I didn't notice any errors at all

OLD LOGIC:

Code:

me@mysystem:/usr/local/bin ==> inxi -MCazy                                                                  
Machine:
  Type: Laptop System: LENOVO product: 80ST v: Lenovo ideapad 310-15ABR 
  serial: <filter> Chassis: type: 10 v: Lenovo ideapad 310-15ABR 
  serial: <filter> 
  Mobo: LENOVO model: LNVNB161216 v: SDK0J40700WIN serial: <filter> 
  UEFI: LENOVO v: 1LCN50WW date: 04/17/2017 
CPU:
  Info: Quad Core model: AMD A12-9700P RADEON R7 10 COMPUTE CORES 4C+6G 
  bits: 64 type: MCP arch: Excavator family: 15 (21) model-id: 65 (101) 
  stepping: 1 microcode: 6006118 cache: L2: 1024 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 19962 
  Speed: 1288 MHz min/max: 1300/2500 MHz boost: enabled Core speeds (MHz): 
  1: 1288 2: 1296 3: 1498 4: 1291 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  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 AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected

NEW LOGIC:

Code:

me@mysystem:/usr/local/bin ==> pinxi -MCazy1
Machine:
  Type: Laptop
  System: LENOVO
    product: 80ST
    v: Lenovo ideapad 310-15ABR
    serial: <superuser required>
  Chassis:
    type: 10
    v: Lenovo ideapad 310-15ABR
    serial: <superuser required>
  Mobo: LENOVO
    model: LNVNB161216
    v: SDK0J40700WIN
    serial: <superuser required>
  UEFI: LENOVO
    v: 1LCN50WW
    date: 04/17/2017

CPU:
  Info:
    model: AMD A12-9700P RADEON R7 10 COMPUTE CORES 4C+6G
    bits: 64
    type: MCP
    arch: Excavator
    family: 15 (21)
    model-id: 65 (101)
    stepping: 1
    microcode: 6006118
    bogomips: 4990
  Topology:
    cpus: 1
      cores: 4
    cache:
      L1: 320 KiB
        desc: d-4x32 KiB; i-2x96 KiB
      L2: 2 MiB
        desc: 2x1024 KiB
  Speed (MHz):
    avg: 1910
    high: 3282
    min/max: 1300/2500
    boost: enabled
    cores:
      1: 3282
      2: 1778
      3: 1287
      4: 1295
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
    Type: itlb_multihit
      status: Not affected
    Type: l1tf
      status: Not affected
    Type: mds
      status: Not affected
    Type: meltdown
      status: Not affected
    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 AMD retpoline, STIBP: disabled, RSB filling
    Type: srbds
      status: Not affected
    Type: tsx_async_abort
      status: Not affected

marav · 12-05-2021, 06:45 PM

Code:

blackstar :: /tmp » ./pinxi -r
Repos:
  slackpkg repos in: /etc/slackpkg/mirrors
  1: http://bsd-one.local/slackware/slackware64-current/
  slackpkg+ repos in: /etc/slackpkg/slackpkgplus.conf
  1: slackpkgplus ~ https://slakfinder.org/slackpkg+15/
  2: slackers ~ https://slack.conraid.net/repository/slackware64-current/
  3: alienbob ~ https://slackware.nl/people/alien/sbrepos/current/x86_64/

Awesome!

fourtysixandtwo · 12-05-2021, 08:51 PM

Quote:

Originally Posted by h2-1

Oh, good, so no real issues. pinxi can't actually detect the real failure cause when it does its early tool testing, it just detects that there was a failure, and in this case, assumes it was permissions. ISA bus is fine, that's actually before inxi's time so not supporting that is ok. Important thing there was that it ran with no errors. That explains the lspci -n failure though. But this is a corner of a corner case, just an extreme test of pinxi/inxi handling of various platforms. Important thing there were no undefined value errors at all, which means everything was more or less correctly trapped and handled.

Thanks for confirming.

Stuck a 2.6 kernel on there as I thought you wouldn't mind seeing the differences. lspci just reports nothing without any errors now btw.

Re the dmi data...really makes me miss the old SUN stuff and sunsolve with engineer level access. Got spoiled with great hardware and information. It's much better now obviously but the x86 stuff has always been a bit of a mess. Kudos to you for putting in the work to even try dealing with it!

Code:

# time ~/pinxi -zv8 
System:
  Kernel: 2.6.39.4 i486 bits: 32 compiler: gcc v: 3.4.6
  parameters: BOOT_IMAGE=custom-2.6.39.4 ro root=801
  Console: pty pts/0 Distro: Slackware 11.0.0
Machine:
  Message: No machine data: try newer kernel. Is dmidecode installed? Try -M
  --dmidecode.
Battery:
  Message: No /sys data found.
Memory:
  RAM: total: 27.2 MiB used: 18.4 MiB (67.6%)
  RAM Report: smbios: No SMBIOS data for dmidecode to process
PCI Slots:
  Smbios: No SMBIOS data for dmidecode to process
CPU:
  Info: single core model: 486 bits: N/A type: UP arch: N/A family: 4
  model-id: N/A microcode: N/A cache: N/A bogomips: 31
  Speed: N/A min/max: N/A core: No per core speed data found.
  Flags: N/A
  Vulnerabilities: No CPU vulnerability/bugs data available.
Graphics:
  Message: No device data found.
  Display: server: No display server data found. Headless machine?
  tty: 200x60
  Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
  Message: No device data found.
Network:
  Message: No device data found.
  IF-ID-1: eth0 state: unknown speed: 10 Mbps duplex: half mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> scope: link
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Missing: Required tool lvs not installed. Check --recommends
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 4.99 GiB used: 1.55 GiB (31.0%)
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST31200N
  size: 1006.4 MiB block-size: physical: 512 B logical: 512 B type: N/A
  serial: <filter> rev: 8648 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST32430N size: 2 GiB
  block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
  rev: 0250 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST32430N size: 2 GiB
  block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
  rev: 0170 scheme: MBR
  Floppy-1: /dev/fd0
  Floppy-2: /dev/fd1
  Floppy-3: /dev/fd2
  Floppy-4: /dev/fd3
  Optical-1: /dev/cdrom0 vendor: N/A model: N/A rev: N/A dev-links: cdrom
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-2: /dev/dvd0 vendor: N/A model: N/A rev: N/A dev-links: dvd
  Features: speed: N/A multisession: N/A audio: N/A dvd: N/A rw: none
  state: N/A
  Optical-3: /dev/sr0 vendor: TOSHIBA model: DVD-ROM SD-M1401 rev: 1009
  dev-links: cdrom0,dvd0
  Features: speed: 40 multisession: yes audio: yes dvd: yes rw: none
  state: running
Partition:
  ID-1: / raw-size: 929 MiB size: 899.9 MiB (96.86%) used: 143.6 MiB (16.0%)
  fs: ext3 block-size: 4096 B dev: /dev/sda1 maj-min: 8:1 label: N/A
  uuid: 4ffc9544-328d-4772-82b7-2d36b46503a3
  ID-2: /usr raw-size: 2 GiB size: 1.94 GiB (96.87%) used: 1.4 GiB (72.4%)
  fs: ext3 block-size: 4096 B dev: /dev/sdb1 maj-min: 8:17 label: N/A
  uuid: ef300d0d-1585-41fc-b742-40917ac526d9
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 235.3 MiB used: 5 MiB (2.1%)
  priority: -1 dev: /dev/sdc2 maj-min: 8:34 label: N/A
  uuid: e41c4c40-ec80-4ee2-9045-251d8f4a5145
Unmounted:
  ID-1: /dev/sda2 maj-min: 8:2 size: 77 MiB fs: swap label: N/A uuid: N/A
  ID-2: /dev/sdc1 maj-min: 8:33 size: 1.77 GiB fs: ext3 label: N/A
  uuid: ce61d54e-b523-4ff2-a703-dda41c99e79b
USB:
  Message: No USB data found. Server?
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Repos:
  Packages: note: see --pkg pkgtool: 1
  slackpkg repos in: /etc/slackpkg/mirrors
  1: http://mirror.csclub.uwaterloo.ca/slackware/slackware-11.0/
Processes:
  CPU top: 5 of 48
  1: cpu: 92.3% command: pinxi started by: perl pid: 1712
  mem: 12.4 MiB (45.5%)
  2: cpu: 10.0% command: sh pid: 1717 mem: 0.93 MiB (3.4%)
  3: cpu: 0.4% command: udevd pid: 87 mem: 0.20 MiB (0.7%)
  4: cpu: 0.1% command: [rcu_kthread] pid: 6 mem: 0.00 MiB (0.0%)
  5: cpu: 0.1% command: [kswapd0] pid: 14 mem: 0.00 MiB (0.0%)
  Memory top: 5 of 48
  1: mem: 12.4 MiB (45.5%) command: pinxi started by: perl pid: 1712
  cpu: 92.3%
  2: mem: 1.11 MiB (4.0%) command: -su pid: 1535 cpu: 0.0%
  3: mem: 0.93 MiB (3.4%) command: sh pid: 1717 cpu: 10.0%
  4: mem: 0.86 MiB (3.1%) command: ps pid: 1718 cpu: 0.0%
  5: mem: 0.49 MiB (1.7%) command: -sh pid: 1525 cpu: 0.0%
Info:
  Processes: 48 Uptime: 59m Init: SysVinit v: 2.84 runlevel: 3 default: 3
  tool: /etc/rc.d Compilers: gcc: 3.4.6 alt: 3.4.6 Shell: Bash v: 3.1.17
  running-in: pty pts/0 pinxi: 3.3.09-31

real    1m11.688s
user    0m46.611s
sys     0m10.329s

h2-1 · 12-05-2021, 09:09 PM

Was there a comparable 'lsisa' tool to lspci for this type of hardware?

Thanks for showing the difference between 2.4 and 2.6 kernels. I have also found similar differences only more so between 2.2 and 2.4, inxi can barely get data off of a 2.2 kernel because the tools and syntax were quite different, but in my tests gets no errors, just even less data than you got here with 2.4 or 2.6.

My data shows Slackware 11.0 shipped with Perl 5.8.8, so in theory inxi could run down to Slackware 9.0, which shipped with Perl 5.8.0, but in practice I've found the very first Perl 5.8.0 had some very odd bugs and issues, some I have worked around in inxi, but they definitely had some non correct behaviors which are not predictable, though I found I could work around them using somewhat annoying hacks (which are well commented in the source code since otherwise it would make no sense to do it that way).

So this is also a very good confirmation that the backward compatibility of inxi is still working fine, that's something that glitches now and then when I forget to test it on big changes and something slips in that was only supported on later Perl versions.

Thanks for all the great data, now there's just that one irksome phantom L3 cache to resolve, and this is looking close to good for next inxi. I'll kick around the code a bit first though, see if I can snag a few hundreds of a second here and there, but it gets tricky to do that unless I accidentally looped something super inefficient.

By the way, I just got another AMD Phenom test sample, but that one had a real L3 cache so I couldn't use it to confirm what is going on.

fourtysixandtwo · 12-05-2021, 10:35 PM

No just dmesg and whenever /proc/devices,dma,etc became available mostly...and that's if the driver was loaded otherwise bupkis. I was reminded recently using an old ne2000 isa card that you needed to specify the io address to get it to work.

Nice that it works as well as it does on the old distributions and hardware.