Yesnamida12 wrote: Do I need sudo?
inxi / pinxi 2.9.00 beta testers!
Re: inxi / pinxi 2.9.00 beta testers!
MX-18 on Asus T100CHI (z3775 Intel baytrail) mixed-mode 32 bit UEFI, 64 bit OS
Dell 3250 Inspiron desktop, i5-6400, 64 bit OS
Dell 3250 Inspiron desktop, i5-6400, 64 bit OS
Re: inxi / pinxi 2.9.00 beta testers!
yes, you'll need sudo to write to /usr/local/bin
Re: inxi / pinxi 2.9.00 beta testers!
jbMacAZ, I'm slightly puzzled with this one, pinxi to find cinnamon first checks for the the program muffin, which is at /usr/bin/muffin, and is a dependency of cinnamon, at least current cinnamon, I checked with apt-file. this detection has worked in the past, but it failed in your case. Has cinnamon changed and no longer depends on muffin? To work around this I added a second test, for cinnamon-session which I assume is a required part of cinnamon.
biker, I believe I caused that cpu bug, that should be fixed now.
biker, I believe I caused that cpu bug, that should be fixed now.
Re: inxi / pinxi 2.9.00 beta testers!
I'm trying to close off an entire category of network usb detection failures, so I've changed some stuff internally, and I may need to change more.
The problem comes from how the usb output is actually generated, I may have to alter that detection slightly I think and add a more aggressive test for networking. I've upped the network usb tests quite a bit now, the problem is that when using the short form of lsusb there is virtually no way to identify a network device unless the company puts the key words I can detect in their device name. I've now changed the detection to add together the values of 4 fields, in hopes of improving the odds of finding those key words, and i've also changed a bit how the output name is generated, similar to the changes I made to get audio usb name working.
0374 has these changes. But as noted, I may need to go in deeper to the full usb data to dig out the networking info, but that's going to be an empirical work, inxi never did this level, so that's actually a new feature, which is good.
This should detect your usb ethernet device since that data was available in another field, but that's really just a random thing, not an overall solution, since it depends on them naming the device with a detectable networking term in it. The full usb output however does have more data, but I'm trying to avoid using that because it's really, really, long, and cpu intensive to loop over and over again. But maybe I'll add in some fields that make the parsing easier, I'll see how hard these issues are to resolve.
The problem comes from how the usb output is actually generated, I may have to alter that detection slightly I think and add a more aggressive test for networking. I've upped the network usb tests quite a bit now, the problem is that when using the short form of lsusb there is virtually no way to identify a network device unless the company puts the key words I can detect in their device name. I've now changed the detection to add together the values of 4 fields, in hopes of improving the odds of finding those key words, and i've also changed a bit how the output name is generated, similar to the changes I made to get audio usb name working.
0374 has these changes. But as noted, I may need to go in deeper to the full usb data to dig out the networking info, but that's going to be an empirical work, inxi never did this level, so that's actually a new feature, which is good.
This should detect your usb ethernet device since that data was available in another field, but that's really just a random thing, not an overall solution, since it depends on them naming the device with a detectable networking term in it. The full usb output however does have more data, but I'm trying to avoid using that because it's really, really, long, and cpu intensive to loop over and over again. But maybe I'll add in some fields that make the parsing easier, I'll see how hard these issues are to resolve.
Re: inxi / pinxi 2.9.00 beta testers!
0380-p fixes the issue with ARM devices or no networking card detected not showing the IF networking data for -n or -i
I'm going to also try to list undetected devices as well, that is, say you have an ethernet card, that shows fine, but you have a wifi usb device that doesn't get detected, so you don't see it's -n or -i data, once I get that working, it will show it under the detected devices
I'm going to also try to list undetected devices as well, that is, say you have an ethernet card, that shows fine, but you have a wifi usb device that doesn't get detected, so you don't see it's -n or -i data, once I get that working, it will show it under the detected devices
- rokytnji.1
- Global Moderator
- Posts: 718
- Joined: Sun Apr 13, 2014 9:06 pm
Re: inxi / pinxi 2.9.00 beta testers!
Just installed and updated on my Acer C710 Chromebook. It is current
I'll boot up my Dell E4310 that I posted with yesterday and update it and check for the cpu fix for you.
Edit: Here is the Dell Laptop.
I should mention I guess. As a part of my routine install process. I always run sensors-detect
2nd edit. I guess to keep you from spinning your wheels. I would not overthink the lack of info on Chromebook readouts. With all the N/A and BattX stuff. It is at least reading something.
They are strange creatures to say the least.
Sigh. 3rd edit.
Figured I'd show acpi -b to show Battery 0 shows instead of BAT X.
I'll show my conky battery line also
Code: Select all
harry@biker:~
$ sudo pinxi -U --alt 40
Code: Select all
harry@biker:~
$ inxi -Fxxx
System: Host: biker Kernel: 4.15.5-antix.1-amd64-smp x86_64 bits: 64 gcc: 6.3.0
Desktop: IceWM 1.4.2 dm: slim
Distro: antiX-17_x64-full Heather Heyer 24 October 2017
Machine: Device: desktop System: Google product: Parrot v: 1.0 serial: N/A
Mobo: Google model: Parrot v: 1.0 serial: N/A
BIOS: coreboot v: 4.0-6588-g4acd8ea-dirty date: 09/04/2014
Chassis: type: 3 serial: N/A
Battery BATX: charge: 31.0 Wh 99.0% condition: 31.3/37.0 Wh (85%) volts: 17.4/14.8
model: SANYO AL12B32 Li-ion serial: 0000000000001D0F status: N/A cycles: 0
CPU: Dual core Intel Celeron 1007U (-MCP-) arch: Ivy Bridge rev.9 cache: 2048 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 5986
clock speeds: min/max: 800/1500 MHz 1: 1397 MHz 2: 1382 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
bus-ID: 00:02.0 chip-ID: 8086:0156
Display Server: X.Org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1366x768@60.02hz
OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile
version: 3.3 Mesa 13.0.6 (compat-v: 3.0) Direct Render: Yes
Audio: Card Intel 7 Series/C216 Family High Def. Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1e20
Sound: Advanced Linux Sound Architecture v: k4.15.5-antix.1-amd64-smp
Network: Card-1: Qualcomm Atheros AR9462 Wireless Network Adapter
driver: ath9k bus-ID: 01:00.0 chip-ID: 168c:0034
IF: wlan0 state: up mac: 3c:77:e6:26:f5:b5
Card-2: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe
driver: tg3 v: 3.137 bus-ID: 02:00.0 chip-ID: 14e4:16b5
IF: eth0 state: down mac: 20:1a:06:14:09:d9
Drives: HDD Total Size: 16.0GB (Used Error!)
ID-1: /dev/sda model: SanDisk_SSD_U100 size: 16.0GB serial: 132553400495
ID-2: /dev/mmcblk0 model: N/A size: 31.9GB serial: 0x61881eb6
Partition: ID-1: / size: 15G used: 4.3G (31%) fs: ext4 dev: /dev/sda1
Sensors: System Temperatures: cpu: 42.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 133 Uptime: 6 min Memory: 511.9/2875.9MB
Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 6.3.0
Client: Shell (bash 4.4.121 running in lxterminal) inxi: 2.3.54
Edit: Here is the Dell Laptop.
Code: Select all
harry@biker:~
$ sudo pinxi -U --alt 40
[sudo] password for harry:
Starting pinxi self updater.
Using curl as downloader.
Currently running pinxi version number: 2.9.00
Current version patch number: 369-p
Current version release date: 2018-03-07
Updating pinxi in /usr/local/bin using pinxi branch as download source...
Successfully updated to pinxi branch version: 2.9.00;
New pinxi branch version patch number: 380-p;
New pinxi branch version release date: 2018-03-08;
To run the new version, just start pinxi; again.
----------------------------------------
Starting download of man page file now.
Skipping man download because branch version is being used.
harry@biker:~
$ inxi -Fxxx
System: Host: biker Kernel: 4.15.5-antix.1-amd64-smp x86_64 bits: 64 gcc: 6.3.0 Desktop: IceWM 1.4.2 dm: slim
Distro: antiX-17_x64-full Heather Heyer 24 October 2017
Machine: Device: laptop System: Dell product: Latitude E4310 v: 0001 serial: N/A Chassis: type: 9 serial: N/A
Mobo: Dell model: 0T6M8G v: A01 serial: N/A BIOS: Dell v: A03 date: 07/08/2010
Battery BAT0: charge: 48.8 Wh 113.3% condition: 43.1/48.8 Wh (88%) volts: 12.5/11.1
model: Samsung SDI DELL RM6618A Li-ion serial: 0 status: Full cycles: 0
CPU: Dual core Intel Core i5 M 520 (-MT-MCP-) arch: Nehalem rev.5 cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9576
clock speeds: min/max: 1199/2400 MHz 1: 1242 MHz 2: 1298 MHz 3: 1324 MHz 4: 1566 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0046
Display Server: X.Org 1.19.2 driver: intel Resolution: 1366x768@60.00hz
OpenGL: renderer: Mesa DRI Intel Ironlake Mobile version: 2.1 Mesa 13.0.6 Direct Render: Yes
Audio: Card Intel 5 Series/3400 Series High Definition Audio
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:3b57
Sound: Advanced Linux Sound Architecture v: k4.15.5-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.0 chip-ID: 8086:10ea
IF: eth0 state: down mac: 5c:26:0a:06:32:15
Card-2: Intel Centrino Advanced-N 6200 driver: iwlwifi bus-ID: 02:00.0 chip-ID: 8086:422c
IF: wlan0 state: up mac: 00:27:10:6a:ae:60
Drives: HDD Total Size: 60.0GB (42.6% used)
ID-1: /dev/sda model: KINGSTON_SV300S3 size: 60.0GB serial: 50026B7743028DAC
Partition: ID-1: / size: 7.7G used: 3.8G (53%) fs: ext4 dev: /dev/sda2
ID-2: /home size: 48G used: 21G (45%) fs: ext4 dev: /dev/sda1
Sensors: System Temperatures: cpu: 52.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 154 Uptime: 1:02 Memory: 229.4/7904.3MB
Init: SysVinit v: 2.88 runlevel: 5 default: 5 Gcc sys: 6.3.0
Client: Shell (bash 4.4.121 running in lxterminal) inxi: 2.3.54
harry@biker:~
$
2nd edit. I guess to keep you from spinning your wheels. I would not overthink the lack of info on Chromebook readouts. With all the N/A and BattX stuff. It is at least reading something.
Code: Select all
Machine: Device: desktop System: Google product: Parrot v: 1.0 serial: N/A
Mobo: Google model: Parrot v: 1.0 serial: N/A
BIOS: coreboot v: 4.0-6588-g4acd8ea-dirty date: 09/04/2014
Chassis: type: 3 serial: N/A
Battery BATX: charge: 31.0 Wh 99.0% condition: 31.3/37.0 Wh (85%) volts: 17.4/14.8
model: SANYO AL12B32 Li-ion serial: 0000000000001D0F status: N/A cycles: 0
Sigh. 3rd edit.
Figured I'd show acpi -b to show Battery 0 shows instead of BAT X.
Code: Select all
$ acpi -b
Battery 0: Full, 100%
Code: Select all
{execi 1000 acpi 2>/dev/null | grep -q . && echo "Batt: "}${execi 10 acpi -b 2>/dev/null | cut -d" " -f3,4 | sed 's/,$//'}
Re: inxi / pinxi 2.9.00 beta testers!
Another Arm machine. This is a Samsung Chromebook running Ubuntu with Crouton. Crouton runs Linux on arm chromebooks in a chroot which may or may not account for the missing /run/run/utmp. debug 21 uploaded.
Code: Select all
(precise)tim@localhost:~$ pinxi -v7
System: Host: localhost Kernel: 3.8.11 armv7l bits: 32 compiler: gcc v: 4.9.x Desktop: LXDE info: lxpanel
dm: N/A Distro: Ubuntu precise (12.04.5 LTS)
Machine: Message: No machine data: try newer kernel. Is dmidecode installed? Try -M --alt 33.
Memory: RAM Report: missing: Required program dmidecode not available
CPU: Topology: Dual Core model: ARMv7 rev 4 (v7l) type: MCP arch: ARMv7 rev: 4
features: Use -f option to see features bogomips: N/A
Speed: 1700 MHz min/max: 200/1700 MHz Core speeds: 1: 1700 2: 1700
Graphics: ARM: PCI data type is not supported on ARM systems.
Display Server: X.org 1.13.0 driver: tty: 134x36
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: ARM: PCI data type is not supported on ARM systems.
Network: ARM: PCI data type is not supported on ARM systems.
IF: mlan0 state: up speed: N/A duplex: N/A mac: 1c:99:4c:15:b0:5c
IP v4: 192.168.1.142/24 scope: global broadcast: 192.168.1.255
IP v6: fe80::1e99:4cff:fe15:b05c/64 scope: link
WAN IP: 65.35.72.33
Drives: HDD Total Size: 0 KB used: 24.46 GB
ID-1: /dev/mmcblk0 model: N/A size: 14.68 GB serial: 0x0923a026
Message: No Optical or Floppy data was found.
Partition: ID-1: / size: 9.89 GB used: 8.15 GB (82.5%) fs: ext2 dev: /dev/root label: N/A uuid: N/A
ID-2: /tmp size: 1000.5 MB used: 3.9 MB (0.4%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-3: /run size: 200.1 MB used: 24 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-4: /dev/shm size: 1000.5 MB used: 5.9 MB (0.6%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-5: /home size: 9.89 GB used: 8.15 GB (82.5%) fs: ext4 dev: /dev/mmcblk0p1 label: N/A
uuid: 8acfa9e3-e507-4b46-ad86-fe6e44491d7c
ID-6: /var size: 9.89 GB used: 8.15 GB (82.5%) fs: ext4 dev: /dev/mapper/encstateful label: N/A
uuid: N/A
ID-7: /media size: 9.89 GB used: 8.15 GB (82.5%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-8: /usr/local size: 9.89 GB used: 8.15 GB (82.5%) fs: ext4 dev: /dev/mmcblk0p1 label: N/A
uuid: 8acfa9e3-e507-4b46-ad86-fe6e44491d7c
ID-9: /sys/fs/cgroup size: 1000.5 MB used: 0 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-10: /dev/pstore size: 1000.4 MB used: 0 KB (0.0%) fs: pstore dev: ERR-102 label: N/A uuid: N/A
ID-11: / size: 9.89 GB used: 8.15 GB (82.5%) fs: ext4 dev: /dev/mmcblk0p1 label: N/A
uuid: 8acfa9e3-e507-4b46-ad86-fe6e44491d7c
ID-12: /dev/shm size: 1000.5 MB used: 5.9 MB (0.6%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-13: /tmp size: 1000.5 MB used: 3.9 MB (0.4%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-14: /var/host/dbus size: 1000.5 MB used: 428 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A
uuid: N/A
ID-15: /var/host/shill size: 1000.5 MB used: 428 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A
uuid: N/A
ID-16: /var/host/timezone size: 2.92 GB used: 220.1 MB (7.4%) fs: ext4 dev: /dev/mapper/encstateful
label: N/A uuid: N/A
ID-17: /lib/modules/3.8.11 size: 1.19 GB used: 931.7 MB (76.3%) fs: ext2 dev: /dev/root label: N/A
uuid: N/A
ID-18: /var/host/udev size: 1000.5 MB used: 428 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A
uuid: N/A
ID-19: /var/host/cras size: 1000.5 MB used: 428 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A
uuid: N/A
ID-20: /var/host/media size: 1000.5 MB used: 0 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-21: /home/tim/Downloads size: 9.89 GB used: 8.15 GB (82.5%) fs: ecryptfs dev: ERR-102 label: N/A
uuid: N/A
ID-22: /sys/fs/cgroup size: 1000.5 MB used: 0 KB (0.0%) fs: tmpfs dev: ERR-102 label: N/A uuid: N/A
ID-23: /media/CB6A-7FFA size: 16.0 MB used: 6.9 MB (43.0%) fs: vfat dev: /dev/mmcblk0p12 label: N/A
uuid: CB6A-7FFA
ID-24: swap-1 size: 1.91 GB used: 0 KB (0.0%) fs: swap dev: /dev/zram0 label: N/A uuid: N/A
RAID: Message: No RAID data was found.
Unmounted: ID-1: /dev/dm-0 size: 1.21 GB fs: ext2 label: N/A uuid: N/A
ID-2: /dev/dm-1 size: 2.97 GB fs: ext4 label: N/A uuid: 46f716b5-2588-4174-8c7a-629625ab2d70
ID-3: /dev/dm-2 size: 12.1 MB fs: hfs label: N/A uuid: N/A
ID-4: /dev/mmcblk0 size: 14.68 GB fs: root required label: N/A uuid: N/A
ID-5: /dev/mmcblk0boot0 size: 2.0 MB fs: root required label: N/A uuid: N/A
ID-6: /dev/mmcblk0boot1 size: 2.0 MB fs: root required label: N/A uuid: N/A
ID-7: /dev/mmcblk0p2 size: 16.0 MB fs: root required label: N/A uuid: N/A
ID-8: /dev/mmcblk0p3 size: 2.00 GB fs: ext2 label: ROOT-A uuid: N/A
ID-9: /dev/mmcblk0p4 size: 16.0 MB fs: root required label: N/A uuid: N/A
ID-10: /dev/mmcblk0p5 size: 2.00 GB fs: ext2 label: N/A uuid: N/A
ID-11: /dev/mmcblk0p6 size: 0 KB fs: root required label: N/A uuid: N/A
ID-12: /dev/mmcblk0p7 size: 0 KB fs: root required label: N/A uuid: N/A
ID-13: /dev/mmcblk0p8 size: 16.0 MB fs: ext4 label: OEM uuid: e19e68c6-70ba-4590-848c-092fabe41fc8
ID-14: /dev/mmcblk0p9 size: 0 KB fs: root required label: N/A uuid: N/A
USB: Hub: 1:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
Hub: 2:1 usb: 3.00 type: Full speed (or root) hub chip ID: 1d6b:0003
Hub: 3:1 usb: 2.00 type: Full speed (or root) hub chip ID: 1d6b:0002
Hub: 3:2 usb: 2.00 type: Standard Microsystems Single TT chip ID: 0424:3503
Device-1: N/A bus ID: 3:3 usb: 2.00 type: Video chip ID: 2232:1037
Hub: 4:1 usb: 1.10 type: Full speed (or root) hub chip ID: 1d6b:0001
Sensors: System Temperatures: cpu: 23.0 C mobo: N/A
Fan Speeds (in RPM): N/A
runlevel:/var/run/utmp: No such file or directory
Use of uninitialized value $runlevel in substitution (s///) at /usr/local/bin/pinxi line 12939.
Info: Processes: 204 Uptime: 18 min Memory: 1.95 GB used: 712.2 MB (35.6%) Init: Upstart v: 1.5)
default: 2 Compilers: gcc: 4.6.3 alt: 4.6 Shell: bash 4.2.25 running in: xfce4-terminal
pinxi: 2.9.00-380-p
HP Pavillion TP01, AMD Ryzen 3 5300G (quad core), Crucial 500GB SSD, Toshiba 6TB 7200rpm
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Dell Inspiron 15, AMD Ryzen 7 2700u (quad core). Sabrent 500GB nvme, Seagate 1TB
Re: inxi / pinxi 2.9.00 beta testers!
Progress! Cinnamon is reported, the USB Dongle was found and there is some info about the network. Just some debug info between audio and network.
Code: Select all
john@LapLet ~ $ sudo pinxi -Fxzc0
System:
Host: LapLet Kernel: 4.15.7.1 x86_64 bits: 64 compiler: gcc v: 5.4.0
Desktop: ^Cinnamon 3.4.6 Distro: Linux Mint 18.2 Sonya
Machine:
Type: Laptop System: ASUSTeK product: T100CHI v: 1.0 serial: <filter>
. . <snip> . .
Audio:
Card-1: Intel HDMI/DP LPE Audio driver: HdmiLpeAudio
message: bus/chip ids unavailable
Card-2: bytcr-rt5640 driver: bytcr-rt5640
message: bus/chip ids unavailable
Sound Server: ALSA v: k4.15.7.1
Argument "usb" isn't numeric in numeric gt (>) at /usr/local/bin/pinxi line 8121.
Network:
Message: No PCI card data found.
IF: enx70886b825431 state: up speed: 100 Mbps duplex: full mac: <filter>
IF: wlan0 state: up speed: N/A duplex: N/A mac: <filter>
Card-1: Realtek USB 10/100/1000 LAN driver: USB Network bus ID: 1:6
. . <snip> . .
Info:
Processes: 187 Uptime: 9 min Memory: 1.83 GB used: 779.5 MB (41.7%)
Init: systemd runlevel: 5 Compilers: gcc: 5.4.0 Shell: bash 4.3.48
pinxi: 2.9.00-380-p
MX-18 on Asus T100CHI (z3775 Intel baytrail) mixed-mode 32 bit UEFI, 64 bit OS
Dell 3250 Inspiron desktop, i5-6400, 64 bit OS
Dell 3250 Inspiron desktop, i5-6400, 64 bit OS
Re: inxi / pinxi 2.9.00 beta testers!
rokytnji.1, those were inxi, not pinxi outputs. I was wondering, then I noticed it wasn't pinxi.
timkb4cq, on that arm chromebook, I see there is no battery data because of Crouton, so that's not a bug. /sys shows no such data.
I've fixed the runlevel thing, that is I suspect another crouton artifact, pinxi assumed if the program runlevel existed, it would have output, that is not the case in crouton, so I've added error suppression and null result handling. Note that if no runlevel is detected, none shows in the -I line, I'm not sure that's the best behavior but that's what it is now.
jbMacAZ, 0381 may or may not correct that 'usb' glitch, I had something out of order. The '^' in front of cinnamon was another small bug, that's also corrected now.
Note that now pinxi has smarter handling, and will show all IF devices not already detected in the per card readout.
It will use the row starter: IF-iD-[number] to differentiate it from the IF items inside a CARD-[number] set.
This solution seems to work pretty well, and covers arm, missing wifi, and anything else where an IF id did not get displayed under the corresponding CARD section.
I believe I have the ordering right now, I'd forgotten to get the usb data before running these last checks, let me know if it is fixed, if it's not, I'll probably need to see: --debug 22 for that system.
timkb4cq, on that arm chromebook, I see there is no battery data because of Crouton, so that's not a bug. /sys shows no such data.
I've fixed the runlevel thing, that is I suspect another crouton artifact, pinxi assumed if the program runlevel existed, it would have output, that is not the case in crouton, so I've added error suppression and null result handling. Note that if no runlevel is detected, none shows in the -I line, I'm not sure that's the best behavior but that's what it is now.
jbMacAZ, 0381 may or may not correct that 'usb' glitch, I had something out of order. The '^' in front of cinnamon was another small bug, that's also corrected now.
Note that now pinxi has smarter handling, and will show all IF devices not already detected in the per card readout.
It will use the row starter: IF-iD-[number] to differentiate it from the IF items inside a CARD-[number] set.
This solution seems to work pretty well, and covers arm, missing wifi, and anything else where an IF id did not get displayed under the corresponding CARD section.
I believe I have the ordering right now, I'd forgotten to get the usb data before running these last checks, let me know if it is fixed, if it's not, I'll probably need to see: --debug 22 for that system.
Re: inxi / pinxi 2.9.00 beta testers!
jbMacAZ, 382 will fix that 'usb' glitch, that was just a stupid mistake by me.