New #pinxi dev output option for --admin -P, show swap swappiness and vfs cache pressure.
Useful in fringe admin type cases, for example, #liquorix tells me that if users or distros have altered these two default values, that can trigger hard to figure out bugs in the kernel. At least kernels with some configuration focuses like #liquorix.
Turns out the method I was going to use for #inxi --admin -p to determine block size was wrong, but found a standard linux tool that will give the partition logical and physical block sizes, so this feature is now working.
Added the /sys based block size report for -d disks as well, since I already had the logic, figured might as well.
This makes the upcoming inxi, as seems to the norm, filled with features and new tricks and gadgets.
--admin now actually does more than just -C cpu data, which is nice.
Adding in raw partition size to #inxi to squeeze that long requested feature in before 3.0.25 is released. Raw size is the size of the partition including the partition table and extra data the file system uses, but which is not available as storage size to end user.
All the internal device handlers in #inxi started getting redundant, so I ended up refactoring all of it into a new package/class, DeviceData, this pulls together lspci, pciconf, pcidump, eventually pcictl, and SOC /sys data constructors.
To go along with this, I also refactored USB data generators into class USBData, which integrates lsusb, usbdevs, and /sys USB generators.
Testing an #openwrt system with #pinxi on #manjaro forums, didn't expect to get MIPS response, but that's why it never hurts to ask. openwrt is presenting problems, it appears to have an ultra stripped down busybox, and more packages have to be installed to even get inxi running, and there are some real problems, but it is generating relatively error free output, until a kernel thing crashes the networking. Early days.
OpenBSD's pcidump has very little pci data however, less than FreeBSD's pciconf, so I can't match the IF to the PCI NIC as with GNU/Linux and FreeBSD.
But it works. Requires root to run pcidump, which is too bad, will have to add error message for pcidump noting requires root if not root.
My goal with BSD/Unix is basically for all error handlers and null data handlers to work as expected, and to have at least OpenBSD and FreeBSD + FreeBSD variants roughly working. Given the lack of consistent tools / data sources, that's about as far as I'll go unless someone pays me for my time.
I may also look at NetBSD just because that would cover the 3 main BSDs.
I gave #openindiana a quick check for #inxi support, because of @distrotube review yesterday. After fixing a failed BSD ID, I quickly determined that SunOS/OpenSolaris/OpenIndiana aren't going to be getting much if any support beyond the null data handlers kicking in correctly, which they do.
These BSDs come from a different era, and actually expect people to learn tools and logic that applies only to that single OS. They should collaborate, create shared tools to make a more consistent BSD interface.
Re #inxi 3.0.24, for the first time, I had to use cpu steppings to differentiate between kaby lake and coffee lake cpus, they have the same model IDs, so the only way you can roughly tell them apart is through stepping number. So that brings inxi into the present re cpu architectures.
Before tagging new #inxi version, threw in an updated CPU architecture dataset, finally found a place that correctly lists the cpu family, model data and is reasonably upto date.
This brings in zen+, zen 2 amd architectures, and coffee lake, tremont, goldmont, ice lake, cannon lake intel architectures.
#inxi 3.0.24 released. Thanks anonymous Manjaro debug dataset user 'loki' for this report. This fixes the ram/memory report crash, and slightly enhances output for those corner case system boards that have memory arrays for non system memory, like video, cache, or flash.
When memory array is not system memory, now shows what its use is.
Added -Cxx cpu L1/L3 cache report as well. This requires dmidecode and sudo/root to use.
Extended system base to Parrot, but why did they change /etc/debian_version?
Bug fix for #inxi, encountered an unusual motherboard with memory arrays not related to system memory, an old laptop, this caused a break in memory output because it was expecting memory arrays where non existed.
This will be fixed in 3.0.24, which is coming soon.
Also realized I can pull in L1 and L3 cache from dmidecode if root, so added that to -Cxx output as well.
#inxi A few final changes, added -a as shortcut for --admin, which allows something like -Fxxxaz
Thanks to #antix guys for testing and checking for glitches, and making a few last minute suggestions, like adding --admin to -v8, which is now the case.
Thanks to vascom, the #fedora inxi maintainer for making the suggestion (github inxi issue 160) to expand --admin -C to have more useful output.
USB output is now also much nicer and consistent between Hub and Device-x lines.
#inxi just did 3.0.23, revised USB output, vastly enhanced --admin -C cpu vulnerabilty output, and some more system base ids, including a new Debian specific one.
#inxi testing cpu bugs now:
Topology: Quad Core model: AMD GX-412TC SOC bits: 64 type: MCP
family: 16 (22) model-id: 30 (48) stepping: 1 microcode: 7030105
L2 cache: 2048 KiB
Speed: 600 MHz ....
Vulnerabilities: Type: l1tf status: Not affected
Type: meltdown status: Not affected
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline
This is a good idea, and should not be too difficult to carry out.
Look for it in inxi 3.0.23. Will give type and status of each cpu issue, like meltdown, spectre_v1 and spectre_v2.
This feature only works with newer Linux kernels.
Some people give me playful grief because I have a pocket notebook that is never more than 10 feet away from me 24 hours a day and I frequently write down any random random thoughts that occur to me, lists, things I need to remember, interesting quotes, etc etc.
I must say, though, that despite being someone you could call “fully digital” for pretty much everything, starting to carry this notebook a few years ago has been one of the most life-changing oh great decisions I’ve ever made.
#lmde 3 just came out, so I decided to test the #inxi system base feature on it, and discovered that #mint has yet again changed the structure of their /etc/os-release file, adding in some more items.
Rather than play guessing games for proper LMDE system base detection, and other Debian based distro system bases, I decided to just add in a Debian base data generator. This is working in #pinxi, though it probably won't hit master branch for a few weeks.
Free software developer.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!