Siduction Forum

Siduction Forum => Scripting & Kernelhacking => Scripting & Kernelhacking (EN) => Topic started by: h2 on 2018/03/05, 23:59:16

Title: New inxi ready for beta testing
Post by: h2 on 2018/03/05, 23:59:16
I've been working the last few months on the new inxi 3.0.0 release, which is a massive change.

Change one is inxi is moving from Gawk->Bash to Perl 5.x. Tested on Perl 5.08 to current 5.26. Design requirements remain the same: inxi 3.0.0 must run on everything anywhere no matter how old, which for Perl means 5.08 is the oldest realistic Perl release.

For development purposes, inxi 2.9.00 is called pinxi, so that inxi and pinxi can be run next to each other easily on the same system. I refer to bash/gawk inxi as binxi to avoid confusion.

To download and run pinxi:
Code: [Select]
wget -O /usr/local/bin/pinxi https://github.com/smxi/inxi/raw/inxi-perl/pinxi
chmod +x /usr/local/bin/pinxi

Update to latest patch release: pinxi -U

inxi-perl branch home page:
https://github.com/smxi/inxi/tree/inxi-perl

I have only a few things more to do, so I thought I'd get some beta testers, if any are around, now.

Unlike other projects who release the new major version in a raw alpha state condition, pinxi won't be released as inxi 3.0.0 until it is at least feature complete and bugless re inxi 2.3.56.

Note that essentially everything in pinxi has been changed, it's much faster than binxi, from around 50% to 400%, depending on the feature being run and the hardware.

it's also maintainable, and debuggable, which binxi is not. I'd received a few issue reports for various features that I literally could not do with the convoluted data structures I had to use to make gawk talk to bash, but those were fairly easy to resolve in Perl.

All the basic args are the same, plus they all have long forms now, and there are several new options, like --slots (pci slots); --usb, along with more customizable features, and better configuration options.

One of the biggest problems with binxi was the line width logic, which was just a bad hack that was super hard to do, the new pinxi has very smart width handlers, and also uses some space optimizations for narrow screens, so 80 column widths 'just work'.

To give an idea of the speed difference of the line printers, you can run
Code: [Select]
time inxi --help
real 0m1.537s
user 0m0.828s
sys 0m0.529s

vs
time pinxi --help
real 0m0.382s
user 0m0.337s
sys 0m0.071s

I may do some more internal speed optimizations, I did a lot earlier in the process, and I may do more once I have the stuff feature complete.

Note the following:

pinxi will support json/xml output options, the internal data logic is there, but the output feature isn't built yet.

pinxi will support language packs, for much of its output strings, that's been designed in, but is not yet implemented, mainly because I want to stabilize the key/value sets so I know what the translator would need. Basically people interested in providing such language support would use a template language.pl file, which would have all the values possible to translate. Pinxi was designed from the start with this potential in mind, something that was totally impossible to do with binxi.

Main signs of bugs:
A spray of 'undefined $val1' errors. I have left this in on purpose because it shows me where I've failed to properly test data being sent to the printer. That error will occur right before the line, and you'll probably see a blank item in one of the values for the keys of that line, which would tell me where the error happened.

The debugger is likewise enhanced.

Visually the main difference you'll see is most places where data was appended like key: something (extra) the (extra) has been moved to a dedicated key value pair, so it would be like so: key1: something key2: extra

This is required for reasonable json / xml output, plus it's more clear.

All actual bugs will be show stoppers for the 3.0.0 inxi release, since I will follow the debian stable strategy of fixing all bugs before, NOT after, release, which is the way all software should be released in my opinion.

I've tested this on FreeBSD so most issues are resolved, but I don't have full access to bsds, can't for example read dmesg.boot data so there's a real restriction on what I can test for and debug.

BSD support is significantly enhanced, and all features have at least stubs for possible future bsd support. I've also discovered that at least OpenBSD and DragonFlyBSD support non root battery, sensors, and hardware data. Those stubs will be completed at some point, but since none of that works now in binxi, I don't consider those show stoppers, though I may end up fixing them if I can get access to bsds that have those values in sysctl -a or from some other source.

As always, feedback, issues, bugs, all are appreciated. My goal is to have a seamless pinxi -> inxi release.

User config files do not require any changes, and use the same syntax as binxi, so nothing has to be changed there, though there are many new config options available, those are still not documented on smxi.org/docs/ but soon will be.

Current pinxi 2.9 man page:
https://smxi.org/docs/inxi-man.htm

Current pinxi 2.9 options:
https://smxi.org/docs/inxi-options.htm

I'm looking to get this completed quickly because I've been working on it way too long, and have to get back to other things, but I will certainly fix all issues before 3.0.0 is released.

On an advanced level, I've been using Perl execution optimizers, which allow nano second analysis of the program execution, and basically what it comes down to is that about 90% of pinxi execution time is caused by running subshells for commands (and the initial import of a few core Perl modules), reading files is 10 x 30x faster, and reading ram data is of course fastest. Perl itself is insanely fast, so there's a limit on how much I can really gain in pinxi re speed by optimizing the perl itself, the real win is getting rid of any unneeded subshell execution and replacing it with a file read or something like that. The worst culprits so far are lsusb, which is almost comically slow, though I have to recheck the stuff to find what new optimizations might be called for.

Note you can run --sleep 0.1 or --sleep 0 to get rid of the CPU pause prior to getting cpu speeds, the current delay is I think 0.35 seconds, which usually lets most systems spin down enough to reflect non pinxi cpu speed state.

pinxi --recommends will show what needs what. That's also completely redone, and much improved, since now it does not show GNU/Linux users BSD options, and it doesn't show BSD users Linux only options. Basically except for perl 5.08 or newer, pinxi has no dependencies, just recommends. though for best WAN IP speeds, I do strongly recommend installing dig. Package install advice is also enhanced, and now only shows for the package manager present.

pinxi uses only core Perl modules for its main features, though it will use a json and xml module probably for export, but that will only matter for users who want to export the data.
Title: Re: New inxi ready for beta testing
Post by: unklarer on 2018/03/06, 21:05:57
the difference between user and root is not clear to me

Code: [Select]
$ pinxi -v7
System:    Host: sidLXDE Kernel: 4.15.7-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: LXDE info: lxpanel dm: lightdm 1.18.3 Distro: Debian GNU/Linux buster/sid
Machine:   Type: Desktop Mobo: ASUSTeK model: P5Q-PRO v: Rev 1.xx serial: N/A BIOS: American Megatrends v: 2102
           date: 02/23/2009
Memory:    RAM Report: permissions: Unable to run dmidecode. Are you root?
CPU:       Topology: Quad Core model: Intel Core2 Quad Q9400 type: MCP arch: Penryn rev: 10 L2 cache: 3072 KB
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 21331
           Speed: 2002 MHz min/max: 2003/2670 MHz Core speeds: 1: 2000 2: 2004 3: 2000 4: 2000
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Barts XT [Radeon HD 6870] driver: radeon v: kernel
           bus ID: 01:00.0 chip ID: 1002:6738
           Display Server: x11 (X.Org 1.19.6) driver: radeon,ati unloaded: fbdev,vesa,modesetting
           resolution: 1680x1050~60Hz
           OpenGL: renderer: AMD BARTS (DRM 2.50.0 / 4.15.7-towo.1-siduction-amd64 LLVM 5.0.1)
           version: 3.3 Mesa 17.3.6 compat-v: 3.0 direct render: Yes
Audio:     Card-1: Intel 82801JI (ICH10 Family) HD Audio Controller driver: snd_hda_intel v: kernel
           bus ID: 00:1b.0 chip ID: 8086:3a3e
           Card-2: Advanced Micro Devices [AMD/ATI] Barts HDMI Audio [Radeon HD 6790/6850/6870 / 7720 OEM]
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aa88
           Sound Server: ALSA v: k4.15.7-towo.1-siduction-amd64
Use of uninitialized value $if in string eq at /usr/local/bin/pinxi line 7993.
Use of uninitialized value $if in string eq at /usr/local/bin/pinxi line 7993.
Network:   Card-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet driver: ATL1E v: N/A
           port: cc00 bus ID: 02:00 chip ID: 1969:1026
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
           IP v4: 192.168.178.45/24 scope: global broadcast: 192.168.178.255
           IP v6: fe80::222:15ff:fe2c:b991/64 scope: link
           Card-2: Techsan Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card
           driver: b2c2_flexcop_pci v: kernel port: ec00 bus ID: 05:01 chip ID: 13d0:2103
           WAN IP: 85.212.141.174
Drives:    HDD Total Size: 465.77 GB used: 36.70 GB (7.9%)
           ID-1: /dev/sda model: ST3250820AS size: 232.89 GB serial: 5QE2CS2G rev: E
           ID-2: /dev/sdb model: WD2502ABYS size: 232.89 GB serial: WD-WCAT19173754 rev: 3B04
           Floppy-1: /dev/fd0
           Optical-1: /dev/sr0 vendor: PHILIPS model: DVDR824P rev: P1.2 dev-links: cdrom,cdrw,dvd
           Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw state: running
Partition: ID-1: / size: 22.41 GB used: 10.53 GB (47.0%) fs: ext4 dev: /dev/sda10 label: N/A
           uuid: ff169da5-8f35-467e-92c3-d117823796f7
           ID-2: /media/Distris size: 99.72 GB used: 21.21 GB (21.3%) fs: vfat dev: /dev/sdb6 label: Distris
           uuid: 6EDE-B072
           ID-3: /media/DATEN size: 98.58 GB used: 4.97 GB (5.0%) fs: vfat dev: /dev/sda6 label: N/A
           uuid: C61C-895C
           ID-4: swap-1 size: 14.63 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda5 label: N/A
           uuid: 045398f2-dfbc-4cc5-99c5-dca098051969
RAID:      Message: No RAID data was found.
Unmounted: ID-1: /dev/sda1 size: 15.04 GB fs: root required label: N/A
           uuid: ae213508-5a3f-44b6-80c1-48862dda5ffb
           ID-2: /dev/sda11 size: 45.14 GB fs: root required label: N/A
           uuid: ef032757-1572-40fc-902f-1264499961a4
           ID-3: /dev/sda7 size: 9.99 GB fs: root required label: N/A
           uuid: 6a35d32a-5647-4f6d-befb-d2e2335fc38d
           ID-4: /dev/sda8 size: 16.54 GB fs: root required label: N/A
           uuid: aeac8153-a888-4389-b866-b1c72247c28a
           ID-5: /dev/sda9 size: 10.01 GB fs: root required label: N/A
           uuid: 6b5a5113-7ea2-496e-97ca-d39e2c0c372d
           ID-6: /dev/sdb1 size: 10.67 GB fs: root required label: N/A
           uuid: f79f077c-40de-4a56-9885-d8d898704be9
           ID-7: /dev/sdb5 size: 14.88 GB fs: root required label: arch
           uuid: 477ed122-0acb-4b5c-a7fd-767584be97e0
USB Info:  Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Hub: 2:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 3:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 4:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Hub: 5:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 6:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 7:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 8:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Device-1: Logitech Unifying Receiver bus ID: 8:2 usb: 2.00 type: Mouse chip ID: 046d:c52f
Sensors:   System Temperatures: cpu: 41.5 C mobo:  Temperature C gpu: radeon temp: 41 C
           Fan Speeds (in RPM): cpu: 709 psu: 1454 sys-1: 229 sys-2: 795
Info:      Processes: 160 Uptime: 24 min Memory: 7.79 GB used: 1.93 GB (24.8%) Init: systemd v: 237 runlevel: 5
           Compilers: gcc: 7.3.0 alt: 5/6/7 Shell: bash 4.4.18 running in: lxterminal pinxi: 2.9.00-348-p

Code: [Select]
# pinxi -v7
System:    Host: sidLXDE Kernel: 4.15.7-towo.1-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: LXDE info: lxpanel dm: lightdm 1.18.3 Distro: Debian GNU/Linux buster/sid
Machine:   Type: Desktop Mobo: ASUSTeK model: P5Q-PRO v: Rev 1.xx serial: MS1C86BLWK01327
           BIOS: American Megatrends v: 2102 date: 02/23/2009
Memory:    Array-1: capacity: 8 GB note: est slots: 4 EC: None max module size: 2 GB
           Device-1: DIMM0 size: 2 GB info: double-bank speed: 800 MT/s type: DDR2 detail: synchronous
           bus width: 64 bits total: 64 bits manufacturer: N/A part-nu: N/A serial: N/A
           Device-2: DIMM1 size: 2 GB info: double-bank speed: 800 MT/s type: DDR2 detail: synchronous
           bus width: 64 bits total: 64 bits manufacturer: N/A part-nu: N/A serial: N/A
           Device-3: DIMM2 size: 2 GB info: double-bank speed: 800 MT/s type: DDR2 detail: synchronous
           bus width: 64 bits total: 64 bits manufacturer: N/A part-nu: N/A serial: N/A
           Device-4: DIMM3 size: 2 GB info: double-bank speed: 800 MT/s type: DDR2 detail: synchronous
           bus width: 64 bits total: 64 bits manufacturer: N/A part-nu: N/A serial: N/A
CPU:       Topology: Quad Core model: Intel Core2 Quad Q9400 type: MCP arch: Penryn rev: 10 L2 cache: 3072 KB
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 21331
           Speed: 2000 MHz min/max: 2003/2670 MHz Core speeds: 1: 2000 2: 2000 3: 2225 4: 2012
Graphics:  Card-1: Advanced Micro Devices [AMD/ATI] Barts XT [Radeon HD 6870] driver: radeon v: kernel
           bus ID: 01:00.0 chip ID: 1002:6738
           Display Server: x11 (X.Org 1.19.6) driver: radeon,ati unloaded: fbdev,vesa,modesetting
           resolution: 1680x1050~60Hz
           OpenGL: renderer: AMD BARTS (DRM 2.50.0 / 4.15.7-towo.1-siduction-amd64 LLVM 5.0.1)
           version: 3.3 Mesa 17.3.6 compat-v: 3.0 direct render: Yes
Audio:     Card-1: Intel 82801JI (ICH10 Family) HD Audio Controller driver: snd_hda_intel v: kernel
           bus ID: 00:1b.0 chip ID: 8086:3a3e
           Card-2: Advanced Micro Devices [AMD/ATI] Barts HDMI Audio [Radeon HD 6790/6850/6870 / 7720 OEM]
           driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 1002:aa88
           Sound Server: ALSA v: k4.15.7-towo.1-siduction-amd64
Use of uninitialized value $if in string eq at /usr/local/bin/pinxi line 7993.
Use of uninitialized value $if in string eq at /usr/local/bin/pinxi line 7993.
Network:   Card-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet driver: ATL1E v: N/A
           port: cc00 bus ID: 02:00 chip ID: 1969:1026
           IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter>
           IP v4: 192.168.178.45/24 scope: global broadcast: 192.168.178.255
           IP v6: fe80::222:15ff:fe2c:b991/64 scope: link
           Card-2: Techsan Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card
           driver: b2c2_flexcop_pci v: kernel port: ec00 bus ID: 05:01 chip ID: 13d0:2103
           WAN IP: 85.212.141.174
Drives:    HDD Total Size: 465.77 GB used: 36.70 GB (7.9%)
           ID-1: /dev/sda model: ST3250820AS size: 232.89 GB serial: 5QE2CS2G rev: E temp: 39 C
           ID-2: /dev/sdb model: WD2502ABYS size: 232.89 GB serial: WD-WCAT19173754 rev: 3B04 temp: 34 C
           Floppy-1: /dev/fd0
           Optical-1: /dev/sr0 vendor: PHILIPS model: DVDR824P rev: P1.2 dev-links: cdrom,cdrw,dvd
           Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw state: running
Partition: ID-1: / size: 22.41 GB used: 10.53 GB (47.0%) fs: ext4 dev: /dev/sda10 label: N/A
           uuid: ff169da5-8f35-467e-92c3-d117823796f7
           ID-2: /media/Distris size: 99.72 GB used: 21.21 GB (21.3%) fs: vfat dev: /dev/sdb6 label: Distris
           uuid: 6EDE-B072
           ID-3: /media/DATEN size: 98.58 GB used: 4.97 GB (5.0%) fs: vfat dev: /dev/sda6 label: N/A
           uuid: C61C-895C
           ID-4: swap-1 size: 14.63 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda5 label: N/A
           uuid: 045398f2-dfbc-4cc5-99c5-dca098051969
RAID:      Message: No RAID data was found.
Unmatched ) in regex; marked by <-- HERE in m/ext2) <-- HERE [\s,]/ at /usr/local/bin/pinxi line 10961.


My evaluation
Both show this error
Code: [Select]
Use of uninitialized value $if in string eq at /usr/local/bin/pinxi line 7993.
and root additionally
Code: [Select]
Unmatched ) in regex; marked by <-- HERE in m/ext2) <-- HERE [\s,]/ at /usr/local/bin/pinxi line 10961.
Title: Re: New inxi ready for beta testing
Post by: towo on 2018/03/06, 22:19:26
I'm not getting such errors.

Code: [Select]
~
towo:Defiant> pinxi -v7
System:    Host: Defiant Kernel: 4.16.0-rc4-siduction-amd64 x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: Gnome 3.26.2 info: gnome-shell,org.gnome.chrome_gnome_shell.json dm: lightdm 1.18.3
           Distro: siduction 13.2.0 December - xfce - (201312310323)
Machine:   Type: Desktop System: MSI product: MS-7850 v: 1.0 serial: N/A
           Mobo: MSI model: H87-G41 PC Mate(MS-7850) v: 1.0 serial: N/A BIOS: American Megatrends v: V3.9
           date: 07/17/2014
Memory:    RAM Report: permissions: Unable to run dmidecode. Are you root?
CPU:       Topology: Quad Core model: Intel Core i5-4670K type: MCP arch: Haswell rev: 3 L2 cache: 6144 KB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27200
           Speed: 1900 MHz min/max: 800/3800 MHz Core speeds: 1: 1900 2: 1900 3: 1900 4: 1900
Graphics:  Card-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 390.25 bus ID: 01:00.0
           chip ID: 10de:1c82
           Display Server: x11 (X.Org 1.19.6) driver: nvidia resolution: 1920x1080~60Hz
           OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 version: 4.6.0 NVIDIA 390.25 direct render: Yes
Audio:     Card-1: Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel v: kernel
           bus ID: 00:1b.0 chip ID: 8086:8c20
           Card-2: NVIDIA GP107GL High Definition Audio Controller driver: snd_hda_intel v: kernel
           bus ID: 01:00.1 chip ID: 10de:0fb9
           Sound Server: ALSA v: k4.16.0-rc4-siduction-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169
           v: 2.3LK-NAPI port: d000 bus ID: 03:00 chip ID: 10ec:8168
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 44:8a:5b:2f:3a:bf
           IP v4: 192.168.178.10/24 virtual: noprefixroute eth0 scope: global broadcast: 192.168.178.255
           WAN IP: 146.52.62.51
Drives:    HDD Total Size: 3.87 TB used: 1.11 TB (28.8%)
           ID-1: /dev/sda model: ST3000VN000 size: 2.73 TB serial: W73033RL rev: SC60
           ID-2: /dev/sdb model: Crucial_CT750MX3 size: 698.64 GB serial: 161412643EA2 rev: R040
           ID-3: /dev/sdc model: Crucial_CT500MX2 size: 465.76 GB serial: 14500E6F6009 rev: MU04
           Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH24NSB0 rev: LN00
           dev-links: cdrom,cdrw,dvd,dvdrw
           Features: speed: 12 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
           state: running
Partition: ID-1: / size: 687.55 GB used: 132.28 GB (19.2%) fs: ext4 dev: /dev/sdb1 label: system
           uuid: ca638ba5-c0a7-4e1c-8e99-63feb65c1124
           ID-2: /tmp size: 7.80 GB used: 524 KB (0.0%) fs: tmpfs dev: /dev/ label: N/A uuid: N/A
           ID-3: /media/home-to size: 775.56 GB used: 155.77 GB (20.1%) fs: ext4 dev: /dev/sda1 label: Towo
           uuid: da5cacee-fbe1-4bdf-a456-8fbccca1d88a
           ID-4: /media/daten size: 1.91 TB used: 853.60 GB (43.6%) fs: ext4 dev: /dev/sda2 label: Daten
           uuid: bfbe0f2f-35b9-4146-97d3-ccb192bd8d3e
           ID-5: swap-1 size: 16.60 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda3 label: N/A
           uuid: 591c1ac7-d4d6-4d70-bf31-155c9f84c4f9
RAID:      Message: No RAID data was found.
Unmounted: ID-1: /dev/sdc1 size: 100.0 MB fs: root required label: System-reserviert uuid: D28CD61C8CD5FB45
           ID-2: /dev/sdc2 size: 150.83 GB fs: root required label: N/A uuid: 02D25082D2507BBB
           ID-3: /dev/sdc3 size: 450.0 MB fs: root required label: N/A uuid: 80920C48920C44DE
           ID-4: /dev/sdc5 size: 314.39 GB fs: root required label: Volume uuid: CE2E495E2E4940A7
USB Info:  Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Device-1: Microsoft Xbox360 Controller bus ID: 1:2 usb: 2.00 type: Vendor Specific Class
           chip ID: 045e:028e
           Device-2: Logitech Unifying Receiver bus ID: 1:3 usb: 2.00 type: Keyboard chip ID: 046d:c52b
           Hub: 1:4 usb: 2.00 type: VIA Labs VL812 Hub chip ID: 2109:2812
           Hub: 1:5 usb: 2.00 type: Genesys Logic Hub chip ID: 05e3:0608
           Hub: 2:1 usb: 3.00 type: Full speed (or root) hub chip ID: 1d6b:0003
           Hub: 2:2 usb: 3.00 type: VIA Labs VL812 Hub chip ID: 2109:0812
           Hub: 3:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Hub: 3:2 usb: 2.00 type: Intel Full speed (or root) hub chip ID: 8087:8008
           Hub: 4:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Hub: 4:2 usb: 2.00 type: Intel Full speed (or root) hub chip ID: 8087:8000
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 35 C
           Fan Speeds (in RPM): N/A
Info:      Processes: 234 Uptime: 5:39 Memory: 15.60 GB used: 9.88 GB (63.4%) Init: systemd v: 237 runlevel: 5
           default: 5 Compilers: gcc: 7.3.0 alt: 4.4/4.6/4.8/4.9/5/6/7 Shell: bash 4.4.18 running in: guake
           pinxi: 2.9.00-348-p

Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/06, 23:17:59
290-0349-p fixes a wide range of bugs and errors. There were issues with starting pinxi with sudo, now resolved, and another bug reporter found an issue starting it with su -c "pinxi -v7"

Those are resolved now.

290-0351-p fixes a further range of cpu core count bugs, and some other stuff you are less likely to see.

Try updating and see if these issues are corrected, they look similar to what you show here, thanks.

I know I just fixed the failure after RAID, I got that myself today.

The $if error is not clear yet, I'll have to look into that. The actual error data is now suppressed by testing better that the $if is actually found, so that will resolve the errors there, but I'm unclear why pinxi decided that a dvb tv device is a networking device in the first place. Or rather, why lspci -nnv shows it as a network device.

It is a card, but I would think it would be a graphics card. That might require some custom fixes to move from network to graphics, where it belongs from what I can see. Or maybe it should be in a different category.
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/07, 01:42:34
towo, yours is the first bug free output I've seen in beta! Of course, I've seen my own systems, which are all debugged, but so far, it's the first one on forum bug threads that had no obvious bugs.
Title: Re: New inxi ready for beta testing
Post by: GoinEasy9 on 2018/03/07, 03:20:53
Hey h2
Mine has a problem with lspci (Running openSUSE Leap 42.3)

pinxi -F
System:    Host: linux-gmor Kernel: 4.4.114-42-default x86_64 bits: 64 Desktop: KDE Plasma 5.8.7
           Distro: openSUSE Leap 42.3
Machine:   Type: Desktop Mobo: ASUSTeK model: SABERTOOTH 990FX v: Rev 1.xx serial: N/A
           UEFI: American Megatrends v: 0901 date: 11/24/2011
CPU:       Topology: 8 Core model: AMD FX-8150 Eight-Core type: MCP L2 cache: 2048 KB
           Speed: 4153 MHz min/max: N/A Core speeds: 1: 4153 2: 4153 3: 4153 4: 4153 5: 4153 6: 4153       
           7: 4153 8: 4153                                                                                 
Can't exec "lspci": No such file or directory at /usr/local/bin/pinxi line 13132.                         
Use of uninitialized value in split at /usr/local/bin/pinxi line 13132.                                   
Graphics:  Message: No PCI card data found.                                                               
           Display Server: x11 (X.Org 1.18.3) driver: nvidia                                               
           unloaded: vesa,nouveau,fbdev,nv,modesetting resolution: 1920x1080~60Hz, 1920x1080~60Hz         
           OpenGL: renderer: GeForce GTX 550 Ti/PCIe/SSE2 version: 4.5.0 NVIDIA 390.25                     
           direct render: Yes                                                                             
Audio:     Card-1: HDA ATI SB driver: HDA-Intel                                                           
           Card-2: HDA NVidia driver: HDA-Intel                                                           
           Sound Server: ALSA v: k4.4.114-42-default                                                       
Network:   Message: No PCI card data found.                                                               
Drives:    HDD Total Size: 1.47 TB used: 216.19 GB (14.3%)                                                 
           ID-1: /dev/sda model: ST1500DM003 size: 1.36 TB                                                 
           ID-2: /dev/sdb model: OCZ size: 111.79 GB                                                       
Partition: ID-1: / size: 29.40 GB used: 10.13 GB (34.4%) fs: ext4 dev: /dev/sda6                           
           ID-2: /home size: 344.38 GB used: 206.06 GB (59.8%) fs: ext4 dev: /dev/sda7                     
           ID-3: swap-1 size: 16.00 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda5
Sensors:   System Temperatures: cpu: 36.0 C mobo: 30.0 C gpu: nvidia temp: 39 C
           Fan Speeds (in RPM): cpu: 1721 fan-2: 0 fan-3: 1021
Info:      Processes: 227 Uptime: 12:51 Memory: 15.62 GB used: 3.68 GB (23.6%) Shell: bash 4.3.42
           pinxi: 2.9.00-353-p
Title: Re: New inxi ready for beta testing
Post by: GoinEasy9 on 2018/03/07, 03:31:07
Interesting, no lspci error running siduction

pinxi -F
Made: /home/goineasy9/.local/share/pinxi  <-- Only appears on first run
System:    Host: M2N-SLI Kernel: 4.15.7-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.12.2
           Distro: siduction 18.1.0 Patience - kde - (201712310029)
Machine:   Type: Desktop Mobo: ASUSTeK model: M2N-SLI v: 1.XX serial: N/A BIOS: Phoenix LTD
           v: ASUS M2N SLI Revision 0802 date: 04/16/2008
CPU:       Topology: Dual Core model: AMD Athlon 64 X2 5000+ type: MCP L2 cache: 1024 KB
           Speed: 1000 MHz min/max: 1000/2600 MHz Core speeds: 1: 1000 2: 1000
Graphics:  Card-1: NVIDIA G94 [GeForce 9600 GT] driver: nouveau v: kernel
           Display Server: x11 (X.Org 1.19.6) driver: nouveau unloaded: vesa,fbdev,nv,modesetting
           resolution: 1920x1080~60Hz
           OpenGL: renderer: NV94 version: 3.3 Mesa 17.3.6 direct render: Yes
Audio:     Card-1: C-Media CM6501 driver: USB Audio
           Sound Server: ALSA v: k4.15.7-towo.1-siduction-amd64
Network:   Message: No PCI card data found.
Drives:    HDD Total Size: 465.76 GB used: 8.45 GB (1.8%)
           ID-1: /dev/sda model: ST3500320AS size: 465.76 GB
Partition: ID-1: / size: 48.96 GB used: 8.11 GB (16.6%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 400.36 GB used: 352.6 MB (0.1%) fs: ext4 dev: /dev/sda3
           ID-3: swap-1 size: 8.00 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda2
Sensors:   System Temperatures: cpu: 37.0 C mobo:  Temperature C gpu: nouveau temp: 37 C
           Fan Speeds (in RPM): cpu: 1451 psu: 1293 sys-1: 3260 fan-1: 1610
Info:      Processes: 176 Uptime: 6 min Memory: 3.86 GB used: 1.72 GB (44.6%) Shell: bash 4.4.18
           pinxi: 2.9.00-353-p


I do get the same Memory error as towo though:
Memory:    RAM Report: permissions: Unable to run dmidecode. Are you root?
When running pinxi -v7
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/07, 03:48:15
Hi goingeasy. There's no ram error, you have to be root to get ram report.

I'll take a look at the lspci error, it might be a path thing. I'm assuming the Suse has lspci installed, right?
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/07, 04:04:59
Assuming this was a simple path issue, 0354-p should fix that suse thing, assuming it has lspci installed in the first place. It should, since pinxi checks all that initially, but it didn't store the paths, so if the path was like in /sbin, it would have failed. These are all corrected now.

Code: [Select]
Made: /home/goineasy9/.local/share/pinxi  <-- Only appears on first run
It's being polite and telling you it made the config etc directory, but good eye to catch that, I'd forgotten that feature.

Can you also check on suse: pinxi -r

those things change a lot over time so I want to make sure repos still is working on suse.
Title: Re: New inxi ready for beta testing
Post by: GoinEasy9 on 2018/03/07, 04:38:06
Hi h2

1) Yes, openSUSE has lspci installed.
2) If one needs to be root to get RAM support, is that memory report different from what's on the INFO line?


 pinxi -r
Repos:     Enabled zypp sources in: /etc/zypp/repos.d/download.nvidia.com-leap.repo
           1: download.nvidia.com-leap ~
           Enabled zypp sources in: /etc/zypp/repos.d/download.opensuse.org-non-oss.repo
           1: download.opensuse.org-non-oss ~
           Enabled zypp sources in: /etc/zypp/repos.d/download.opensuse.org-non-oss_1.repo
           1: download.opensuse.org-non-oss_1 ~
           Enabled zypp sources in: /etc/zypp/repos.d/download.opensuse.org-oss.repo
           1: download.opensuse.org-oss ~
           Enabled zypp sources in: /etc/zypp/repos.d/download.opensuse.org-oss_1.repo
           1: download.opensuse.org-oss_1 ~
           Enabled zypp sources in: /etc/zypp/repos.d/google-chrome-beta.repo
           1: google-chrome-beta ~
           Enabled zypp sources in: /etc/zypp/repos.d/google-talkplugin.repo
           1: google-talkplugin ~
           Enabled zypp sources in: /etc/zypp/repos.d/openSUSE-Leap-42.3-0.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/opensuse-guide.org-repo.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/packman.inode.at-suse.repo
           1: packman.inode.at-suse ~
           Enabled zypp sources in: /etc/zypp/repos.d/repo-debug-non-oss.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/repo-debug-update-non-oss.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/repo-debug-update.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/repo-debug.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/repo-source-non-oss.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/repo-source.repo
           1: No enabled zypp sources found in file
           Enabled zypp sources in: /etc/zypp/repos.d/slack.repo
           1: slack ~

Edit:  I just updated to 355-p and have no errors using -v7 or -F on openSUSE or siduction.
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/07, 05:32:44
that's a relief re pinxi -r on suse, great, thanks for confirming that. But it appears there's a small glitch with that empty slack line.  what is:

Code: [Select]
cat /etc/zypp/repos.d/slack.repo
You can see the various memory options like so:

pinxi -m
pinxi -tcm
pinxi -mtcm
pinxi -I
pinxi -bm

as you see, the memory line moves around depending. The default is the -I line, if -I line is not being used, it gets printed on whichever line printed it first.

the memory use line is memory, I should maybe rename the memory line to RAM, but it was originally called memory so I probably should not change it.

-m is memory ram report, which requires root. The regular memory total/used report does not require root.
Title: Re: New inxi ready for beta testing
Post by: GoinEasy9 on 2018/03/07, 07:23:47
~> cat /etc/zypp/repos.d/slack.repo
[slack]
name=slack
enabled=1
autorefresh=1
baseurl=https://packagecloud.io/slacktechnologies/slack/fedora/21/x86_64
type=rpm-md
keeppackages=0

~> cat /etc/zypp/repos.d/google-talkplugin.repo
[google-talkplugin]
name=google-talkplugin
enabled=1
autorefresh=1
baseurl=http://dl.google.com/linux/talkplugin/rpm/stable/x86_64
path=/
type=rpm-md
keeppackages=0

~> cat /etc/zypp/repos.d/google-chrome-beta.repo
[google-chrome-beta]
name=google-chrome-beta
enabled=1
autorefresh=1
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
path=/
type=rpm-md
keeppackages=0

~> cat /etc/zypp/repos.d/download.opensuse.org-oss.repo
[download.opensuse.org-oss]
name=Main Repository (OSS)
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/distribution/leap/42.3/repo/oss/                                     
path=/                                                                                                     
type=yast2                                                                                                 
keeppackages=0


I added the 2 google repos and the openSUSE OSS repo .  The 2 google repos because they resemble the slack repo, and, the OSS repo for comparison.  The difference I noticed was with their "type".  All repos were installed through Yast, except for the 2 google repos and the slack repo, which were downloaded manually and installed using zypper.
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/07, 07:38:03
thanks, I'll get it sorted out.
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/07, 09:09:57
290-0360-p should now work correctly with suse. they changed the order of the fields, so I had to make the looper build slightly differently to make sure the title and repo url were always included.

I think that will work, not positive.
Title: Re: New inxi ready for beta testing
Post by: unklarer on 2018/03/07, 10:22:48
Quote from: h2
..but I'm unclear why pinxi decided that a dvb tv device is a networking device in the first place. Or rather, why lspci -nnv shows it as a network device.

I don't think you need to worry about that. The manufacturer of the card already says in the description that this card is recognized under the network cards.   ;)
Title: Re: New inxi ready for beta testing
Post by: GoinEasy9 on 2018/03/07, 16:26:46
On openSUSE Tumblweed there is an error (uninitialized value) between RAID and USB running -v7 as root or user

Edit: Does not occur on openSUSE Leap 42.3

Code: [Select]
pinxi -v7
System:    Host: DellStudio17 Kernel: 4.15.7-1-default x86_64 bits: 64 compiler: gcc v: 7.3.0
           Desktop: KDE Plasma 5.12.2 dm: sddm Distro: openSUSE Tumbleweed 20180305
Machine:   Type: Portable System: Dell product: Studio 1737 v: A05 serial: B0BLMK1
           Mobo: Dell model: 0P792H v: A05 serial: .B0BLMK1.CN4864396R1047. BIOS: Dell v: A05 date: 02/11/2009
Battery:   BAT-0: charge: 7.6 Wh condition: 7.6/7.8 Wh (98%) volts: 12.0/11.1 model: SIMPLO Dell type: Li-ion
           serial: 512 status: Full
Memory:    Array-1: capacity: 4 GB slots: 2 EC: None max module size: N/A
           Device-1: DIMM_A size: 2 GB speed: 800 MT/s type: DDR2 detail: synchronous bus width: 64 bits
           total: 64 bits manufacturer: AD00000000000000 part-nu: HMP125S6EFR8C-S6 serial: 61607AEA
           Device-2: DIMM_B size: 2 GB speed: 800 MT/s type: DDR2 detail: synchronous bus width: 64 bits
           total: 64 bits manufacturer: AD00000000000000 part-nu: HMP125S6EFR8C-S6 serial: 60507B7F
CPU:       Topology: Dual Core model: Intel Core2 Duo T6500 type: MCP arch: Penryn rev: 10 L2 cache: 2048 KB
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 bogomips: 8380
           Speed: 1197 MHz min/max: 1200/2100 MHz Core speeds: 1: 1197 2: 1197
Graphics:  Card-1: Intel Mobile 4 Series Integrated Graphics Controller driver: i915 v: kernel bus ID: 00:02.0
           chip ID: 8086:2a42
           Display Server: x11 (X.Org 1.19.6) driver: modesetting unloaded: intel,fbdev,vesa
           resolution: 1440x900~61Hz
           OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express version: 2.1 Mesa 18.0.0-rc4 direct render: Yes
Audio:     Card-1: Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel v: kernel
           bus ID: 00:1b.0 chip ID: 8086:293e
           Sound Server: ALSA v: k4.15.7-1-default
Network:   Card-1: Intel WiFi Link 5100 driver: iwlwifi v: kernel bus ID: 04:00 chip ID: 8086:4232
           IF: wlp4s0 state: up mac: 00:22:fb:ad:79:00
           IP v4: 192.168.1.128/24 type: dynamic noprefixroute wlp4s0 scope: global broadcast: 192.168.1.255
           IP v6: fe80::111c:4579:b12c:ef3c/64 virtual: noprefixroute scope: link
           Card-2: Broadcom Limited NetLink BCM5784M Gigabit Ethernet PCIe driver: tg3 v: 3.137 port: N/A
           bus ID: 08:00 chip ID: 14e4:1698
           IF: enp8s0 state: down mac: 00:22:19:f6:cf:01
           WAN IP: 69.125.100.126
Drives:    HDD Total Size: 465.76 GB used: 44.29 GB (9.5%)
           ID-1: /dev/sda model: WDC_WD5000L31X size: 465.76 GB serial: WD-WX51A1442704 rev: 1AX1 temp: 35 C
           Optical-1: /dev/sr0 vendor: Optiarc model: DVD+-RW AD-7640S rev: HD16
           dev-links: cdrom,cdrw,dvd,dvdrw
           Features: speed: 24 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
           state: running
Partition: ID-1: / size: 122.53 GB used: 6.95 GB (5.7%) fs: ext4 dev: /dev/sda1 label: N/A
           uuid: 6d49e5e8-5c27-4f0e-a49a-aea6cc46dbaf
           ID-2: /home size: 326.54 GB used: 37.34 GB (11.4%) fs: ext4 dev: /dev/sda3 label: N/A
           uuid: 8b99d5a5-e814-4eeb-bc7b-bec572def0df
           ID-3: swap-1 size: 8.00 GB used: 0 KB (0.0%) fs: swap dev: /dev/sda2 label: N/A
           uuid: 6c9b90f7-1cdf-44c3-b7c1-8b674a39ab8b
RAID:      Message: No RAID data was found.
Unmounted: Message: No unmounted partitions found.
Use of uninitialized value $row[1] in numeric eq (==) at /usr/local/bin/pinxi line 11134.
USB:       Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Device-1: Microdia bus ID: 1:2 usb: 2.00 type: Video chip ID: 0c45:63fa
           Hub: 2:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 3:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 4:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
           Hub: 5:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 6:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Hub: 7:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
           Device-2: Logitech TrackMan Wheel bus ID: 7:2 usb: 1.10 type: Mouse chip ID: 046d:c404
           Hub: 8:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
Sensors:   System Temperatures: cpu: 49.0 C mobo: 34.0 C
           Fan Speeds (in RPM): fan-2: 2533 fan-3: 2533
Info:      Processes: 167 Uptime: 0:46 Memory: 3.81 GB used: 1.82 GB (47.7%) Init: systemd v: 234 runlevel: 5
           target: graphical.target Compilers: gcc: N/A Shell: bash 4.4.19 running in: konsole
           pinxi: 2.9.00-362-p
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/07, 21:43:38
goingeasy, if you can run: pinxi --debug 22

I can get a non hacked fix for that usb issue. There's clearly something I haven't seen yet in the opensuse lsusb output and in how pinxi handles it.

Is the opensuse repo issue resolved?
Title: Re: New inxi ready for beta testing
Post by: GoinEasy9 on 2018/03/07, 22:48:57
Debug says it was uploaded.

pinxi -r looks fine.
Title: Re: New inxi ready for beta testing
Post by: h2 on 2018/03/08, 08:16:07
suse pinxi -r does indeed look fine, thanks for that one, I've realized that with the subtle variants and small changes that happen, I have to see the raw distro repo files, or repo list command output, at least to debug issues, when it's really hard, I have to fake pinxi and use those files to tweak the test for that distro, but it's never as good or reliable as running it on a real version of the distro.