Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

inxi / pinxi 2.9.00 beta testers!

Message
Author
User avatar
rokytnji.1
Forum Regular
Forum Regular
Posts: 749
Joined: Sun Apr 13, 2014 9:06 pm

Re: inxi / pinxi 2.9.00 beta testers!

#141 Post by rokytnji.1 » Wed Mar 28, 2018 9:37 am

Started using the z flag to block network details on forum posts.

Code: Select all

harry@biker:~
$ sudo pinxi -v8z
System:    Host: biker Kernel: 4.15.9-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 
           Desktop: IceWM 1.4.2 dm: slim Distro: antiX-17_x64-full Heather Heyer 24 October 2017 
Machine:   Type: Laptop System: Dell product: Latitude E4310 v: 0001 serial: <filter> Chassis: type: 9 
           serial: <filter> 
           Mobo: Dell model: 0T6M8G v: A01 serial: <filter> BIOS: Dell v: A03 date: 07/08/2010 
Battery:   ID-1: BAT0 charge: 48.8 Wh condition: 40.3/48.8 Wh (82%) volts: 12.5/11.1 
           model: Samsung SDI DELL RM6618A type: Li-ion serial: N/A status: Full 
Memory:    Array-1: capacity: 8 GiB slots: 2 EC: None max module size: 4 GiB note: est 
           Device-1: DIMM_A size: 4 GiB speed: 1067 MHz type: DDR3 detail: synchronous bus width: 64 bits 
           total: 64 bits manufacturer: 80AD part-no: HMT351S6BFR8C-H9 serial: 2E71D725 
           Device-2: DIMM_B size: 4 GiB speed: 1067 MHz type: DDR3 detail: synchronous bus width: 64 bits 
           total: 64 bits manufacturer: 80AD part-no: HMT351S6CFR8C-H9 serial: 01BB7EB6 
PCI Slots: Slot: 0 type: x16 PCI Express x16 J5C1 status: Available length: Long 
           Slot: 1 type: x1 PCI Express J6C2 status: Available length: Short 
           Slot: 2 type: x1 PCI Express J6D2 status: In Use length: Short 
           Slot: 3 type: x1 PCI Express J7C1 status: In Use length: Short 
           Slot: 4 type: x1 PCI Express J7D2 status: Available length: Short 
CPU:       Topology: Dual Core model: Intel Core i5 M 520 type: MT MCP arch: Nehalem rev: 5 L2 cache: 3072 KB 
           bogomips: 19152 
           Speed: 1808 MHz min/max: 1199/2400 MHz Core speeds (MHz): 1: 2388 2: 2662 3: 1548 4: 2669 
           Flags: acpi aes aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de 
           ds_cpl dtes64 dtherm dts ept est flexpriority fpu fxsr ht ida lahf_lm lm mca mce mmx monitor msr 
           mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pni popcnt pse pse36 pti rdtscp 
           rep_good sep smx ss sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow tsc vme vmx vnmi vpid 
           xtopology xtpr 
Graphics:  Card-1: Intel Core Processor Integrated Graphics Controller driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0046 
           Display Server: X.Org 1.19.2 driver: intel resolution: 1366x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 13.0.6 direct render: Yes 
Audio:     Card-1: Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:3b57 
           Sound Server: ALSA v: k4.15.9-antix.1-amd64-smp 
Network:   Card-1: Intel 82577LM Gigabit Network Connection driver: e1000e v: 3.2.6-k port: 6040 bus ID: 00:19 
           chip ID: 8086:10ea 
           IF: eth0 state: down mac: <filter> 
           Card-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel bus ID: 02:00 chip ID: 8086:422c 
           IF: wlan0 state: up mac: <filter> 
           IP v4: <filter> scope: global broadcast: <filter> 
           IP v6: <filter> scope: link 
           WAN IP: <filter> 
Drives:    HDD Total Size: 55.90 GiB used: 23.76 GiB (42.5%) 
           ID-1: /dev/mmcblk0 model: SA04G size: 3.69 GiB serial: <filter> rev: 0x3 
           ID-2: /dev/sda model: KINGSTON_SV300S3 size: 55.90 GiB serial: <filter> rev: BBF0 
           Optical-1: /dev/sr0 vendor: TSSTcorp model: DVD+-RW TS-U633F rev: D500 dev-links: cdrom 
           Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram 
           state: running 
RAID:      Message: No RAID data was found. 
Partition: ID-1: / size: 7.63 GiB used: 3.70 GiB (48.5%) fs: ext4 dev: /dev/sda2 label: rootantiX 
           uuid: 78252287-6dbf-4719-9c7f-13d6bbc8143b 
           ID-2: /home size: 47.08 GiB used: 20.06 GiB (42.6%) fs: ext4 dev: /dev/sda1 label: homeantiX 
           uuid: 62a4a2cd-066a-47d3-a366-f8059a89cbcb 
Unmounted: ID-1: /dev/mmcblk0 size: 3.69 GiB fs: 3.7g label: N/A uuid: N/A 
           ID-2: /dev/mmcblk0p1 size: 3.68 GiB fs: vfat label: N/A uuid: 596C-0657 
USB:       Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Hub: 1:2 usb: 2.00 type: Intel Integrated Rate Matching Hub chip ID: 8087:0020 
           Hub: 2:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002 
           Hub: 2:2 usb: 2.00 type: Intel Integrated Rate Matching Hub chip ID: 8087:0020 
           Device-1: Dell DW375 Bluetooth Module bus ID: 2:3 usb: 2.00 type: Bluetooth chip ID: 413c:8187 
           Device-2: Broadcom BCM5880 Secure Applications Processor with fingerprint swipe sensor bus ID: 2:4 
           usb: 1.10 type: Application Specific Interface chip ID: 0a5c:5801 
Sensors:   System Temperatures: cpu: 49.0 C mobo: N/A sodimm: 43.0 C 
           Fan Speeds (RPM): cpu: 0 
Repos:     Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://repo.antixlinux.com/stretch stretch main nosystemd
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free
           2: deb http://security.debian.org/ stretch/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/onion.list 
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Processes: CPU top: 5 
           1: cpu: 48.0% command: firefox-esr pid: 2991 mem: 871.6MiB (11.0%) 
           2: cpu: 15.0% command: pinxi started by: perl pid: 24953 mem: 20.3MiB (0.2%) 
           3: cpu: 3.0% command: sudo pid: 24952 mem: 3.55MiB (0.0%) 
           4: cpu: 2.1% command: xorg pid: 2275 mem: 38.9MiB (0.4%) 
           5: cpu: 0.4% command: conky pid: 2745 mem: 10.4MiB (0.1%) 
           Memory top: 5 
           1: mem: 871.6 MiB (11.0%) command: firefox-esr pid: 2991 cpu: 11.0% 
           2: mem: 41.1 MiB (0.5%) command: python pid: 2692 cpu: 0.5% 
           3: mem: 38.9 MiB (0.4%) command: xorg pid: 2275 cpu: 0.4% 
           4: mem: 27.9 MiB (0.3%) command: volumeicon pid: 2680 cpu: 0.3% 
           5: mem: 24.7 MiB (0.3%) command: lxterminal pid: 24675 cpu: 0.3% 
Info:      Processes: 156 Uptime: 1:41 Memory: 7.72 GiB used: 1.09 GiB (14.1%) Init: SysVinit v: 2.88 
           runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6 Shell: bash (sudo) v: 4.4.12 
           running in: lxterminal pinxi: 2.9.08-6 

User avatar
richb
Administrator
Posts: 17041
Joined: Wed Jul 12, 2006 2:17 pm

Re: inxi / pinxi 2.9.00 beta testers!

#142 Post by richb » Wed Mar 28, 2018 9:48 am

Nice tip roky.
Forum Rules
Guide - How to Ask for Help

Rich
SSD Production: MX 17.1
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB, 350 GB HD

User avatar
Richard
Posts: 2023
Joined: Fri Dec 12, 2008 10:31 am

Re: inxi / pinxi 2.9.00 beta testers!

#143 Post by Richard » Tue May 01, 2018 1:25 am

I hope H2 is still reading this from time to time.
Not a biggie but Just noticed this in inxi-3.0.06:

Serial Number


richard@mx171:~
$ inxi -M
Machine: Type: Laptop System: LENOVO product: 2347AY1 v: ThinkPad T430 serial: N/A
Mobo: LENOVO model: 2347AY1 v: NO DPK serial: N/A UEFI [Legacy]: LENOVO
v: G1ET73WW (2.09 ) date: 10/19/2012

while on same laptop:
sudo dmidecode -t system

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x000F, DMI type 1, 27 bytes
System Information
Manufacturer: LENOVO
Product Name: 2347AY1
Version: ThinkPad T430
Serial Number: PB5232G
UUID: 5DE7EE81-51E6-11CB-A33A-F4F3D53BA4C8
Wake-up Type: Power Switch
SKU Number: LENOVO_MT_2347
Family: ThinkPad T430

and lshw also gets the Serial number.

$ sudo lshw
mx171
description: Notebook
product: 2347AY1 (LENOVO_MT_2347)
vendor: LENOVO
version: ThinkPad T430
serial: PB5232G
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
MX171 on Lenovo T430-2017: i5-3320M, 8 GBRAM, 4.15.0-1-amd64, intel_pstate, 119GB SSD
MX171 on AA1(ZG5) & EeePC-1005ha: Dual Core N270, 1 GBRAM, 4.15.0-1-686-pae, 150GB HDD
DC9, LibO61, Dbox, PM, FF, mPDFed, CherryT, Vbox. __ Linux Counter #208633

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 411
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#144 Post by h2-1 » Tue May 08, 2018 6:30 pm

Richard, missed this. inxi gets its machine data from /sys, which does not require superuser/root permissions, and is very fast. You can force it to use dmi decode like so: inxi -Mxxx --dmidecode
this overrides the default /sys data parsing for dmidecode parser.

What you're seeing there is a bug in /sys, it failed to show the serial for some reason.

The easiest way for me to figure out if the data is not there or is there with a different than expected path or file name is by running: inxi --debug 22

and letting me know the hostname of the system so I know which gz file it is.

I did just by the way find a really significant bug in /sys data for disk data, so /sys is not at all perfect, and is subject to bugs and glitches just like any other software.

In this case, it's a bug because the C based lshw and dmidecode did get the data, but this is not an inxi bug probably, though a quick look at your dataset, in particular the /sys parse tool output, will show me this conclusively.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
Richard
Posts: 2023
Joined: Fri Dec 12, 2008 10:31 am

Re: inxi / pinxi 2.9.00 beta testers!

#145 Post by Richard » Tue May 08, 2018 10:16 pm

System: Host: mx171 Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3

That is really a neat tool you've built for getting feedback on running systems.
MX171 on Lenovo T430-2017: i5-3320M, 8 GBRAM, 4.15.0-1-amd64, intel_pstate, 119GB SSD
MX171 on AA1(ZG5) & EeePC-1005ha: Dual Core N270, 1 GBRAM, 4.15.0-1-686-pae, 150GB HDD
DC9, LibO61, Dbox, PM, FF, mPDFed, CherryT, Vbox. __ Linux Counter #208633

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 411
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#146 Post by h2-1 » Wed May 09, 2018 2:25 am

Thanks, I like the debugger, it makes my job 100x easier, or more. For instance, I can report that the serial number does not appear in /sys anywhere. Also, there is no file for board_serial or product_serial at all, so that's simply not there. I can't account for that.

But then a sneaking suspicion hit, and I checked, and yes, those @#@@ in the kernel removed serial number from the machine data in /sys unless you are root. Why? Who the hell knows, some paranoid type person filed a bug report they were stupid enough to not reject maybe, very hard to say.

I see this in the kernels 4.16 I just updated to, and when run as root, sigh, serial shows.

I'm starting to lose faith in the reliability of the /sys data as a primary source to be honest, the recent disk model name truncation issue, and now this, that's not what I call reliable data sources.

So it appears that somewhere around 4.15 they removed serial for mobo from /sys, why? really, who knows, a sad event.

If you run inxi as root you'll get it, but that defeats the entire point of using /sys in the first place, the point was to get data without requiring root.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 411
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#147 Post by h2-1 » Wed May 09, 2018 2:27 am

Actually, it's not so simple, something else appears to be going on, I just saw a 4.15 with the serial googling inxi stuff.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
h2-1
Forum Regular
Forum Regular
Posts: 411
Joined: Sat Nov 15, 2008 3:16 pm

Re: inxi / pinxi 2.9.00 beta testers!

#148 Post by h2-1 » Wed May 09, 2018 3:28 pm

After checking more, the issue is going to take some work, and may not be resolvable at all. Checking systems with 4.16, I find the /sys/class/dmi/id/board_serial (and all serial files for the system, product_uuid, chassis_serial, etc), have been made root owner read only.

I don't know which kernel version decided that users did not need to be able to see their system data in /sys, my guess is 4.15, but as noted, I saw an inxi sample that showed serial for 4.15, so there's more to this than meets the eye.

It may be a kernel compile flag, I'll have to see if I can find more information, but this is certainly a decision made, my guess is, by corporate linux like redhat, or by some excessively paranoid developer, very difficult to say without knowing where the original decision came from, whether it's a simple compile option, or if it's a core kernel change.

You can see for yourself what's going on with: ls -l /sys/class/dmi/id/

It's made more complicated by some systems never having shown serial in the first place.

I'll check with damentz of liquorix and see if he knows anything.
smxi/sgfxi site (manuals, how-to's, faqs) :: script forums :: Check out inxi sys info script!

User avatar
Richard
Posts: 2023
Joined: Fri Dec 12, 2008 10:31 am

Re: inxi / pinxi 2.9.00 beta testers!

#149 Post by Richard » Wed May 09, 2018 5:56 pm

Well, Hanlon's Razon comes to mind,
"Never attribute to malice that which is adequately explained by stupidity."
There's a lot of it going around.
MX171 on Lenovo T430-2017: i5-3320M, 8 GBRAM, 4.15.0-1-amd64, intel_pstate, 119GB SSD
MX171 on AA1(ZG5) & EeePC-1005ha: Dual Core N270, 1 GBRAM, 4.15.0-1-686-pae, 150GB HDD
DC9, LibO61, Dbox, PM, FF, mPDFed, CherryT, Vbox. __ Linux Counter #208633

sunrat
Forum Regular
Forum Regular
Posts: 200
Joined: Mon Mar 28, 2016 9:54 pm

Re: inxi / pinxi 2.9.00 beta testers!

#150 Post by sunrat » Wed May 09, 2018 10:35 pm

h2-1 wrote:I don't know which kernel version decided that users did not need to be able to see their system data in /sys, my guess is 4.15, but as noted, I saw an inxi sample that showed serial for 4.15, so there's more to this than meets the eye.
...
I'll check with damentz of liquorix and see if he knows anything.
I noticed today that serials don't show in my other system with liquorix-4.14. This is inxi, not pinxi:

Code: Select all

System:    Host: mx17-i5-brain Kernel: 4.14.0-8.1-liquorix-amd64 x86_64 bits: 64
           Desktop: Xfce 4.12.3 Distro: MX-17_x64 Horizon December 10, 2017
Machine:   Device: desktop System: Gigabyte product: N/A serial: N/A
           Mobo: Gigabyte model: H170-HD3-CF v: x.x serial: N/A
           UEFI: American Megatrends v: F4 date: 10/16/2015
This from an older machine, inxi report from 6 months ago:

Code: Select all

System:    Host: siduction-brain2 Kernel: 4.13.10-towo.2-siduction-amd64 x86_64 bits: 64
           Desktop: KDE Plasma 5.10.5
           Distro: siduction 17.1.0 Patience - kde - (201703051755)
Machine:   Device: desktop Mobo: Gigabyte model: EP45-UD3R v: x.x serial: N/A
           BIOS: Award v: F3 date: 09/18/2008
and this from 4 years ago, at least shows mobo model. Presumably inxi didn't look for serials back then:

Code: Select all

System:    Host: brain Kernel: 3.14-5.towo-siduction-amd64 x86_64 (64 bit) Desktop: KDE 4.13.2
           Distro: siduction 13.2.0 December - kde - (201312310241)
Machine:   Mobo: Gigabyte model: EP45-UD3R v: x.x Bios: Award v: F3 date: 09/18/2008

Post Reply

Return to “antiX”