209 commits

Author	SHA1	Message	Date
Harald Hope	991a35d665	Enhanced features!! Huge BSD upgrades! Bug Fixes!! Elbrus Fixes!! More bluetooth ... fixes!! What are you waiting for?!!? A special thanks for significant help, ongoing, leading to a huge boost to BSD support, Stan Vandiver, who did a lot of BSD testing, and setup many remote access systems for testing and development of the latest BSD upgrades. If you're a BSD user, you can thank him for helping to expand BSD support! Take special note of the code folding fixes in Fix 1, those open up possible free software code editors that can be used to work with inxi to more than just Kwrite/Kate, to include scite and geany, nice lightweight code editors. You can't do real work in inxi without code folding, so getting this finally resolved was I think worth it. Also, for the first time ever!! inxi is now using Pledge, well, if OpenBSD::Pledge module is available, which is currently only in OpenBSD, since that's the only system that supports Pledge security, except for Serenity, but inxi doesn't support Serenity. Note that OpenBSD was smart and added OpenBSD::Pledge and OpenBSD::Unveil to Perl Core modules, thus removing any hoop that might stop a Perl program from implementing it. Nice going OpenBSD guys! The addition of OpenBSD softraid support for RAID and CRYPTO types highlights the problem with --raid and --logical, where --raid is really just a subset of Logical volume management. Note that while the hardware RAID feature only lists the actual PCI RAID device, OpenBSD bioctl supports hardware RAID out of the box, something I'd thought of doing in inxi for a few years, but it's too much work, but bioctl has done the work, which is impressive. Can't do much without a lot of debugger data there though, but it's worth being aware of. In this case, since softraid is the primary device, I opted to call Crypto and RAID types all RAID, same as with linear zfs. -------------------------------------------------------------------------------- KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED: 1. FreeBSD: USB drivers. I really gave this a try, but could not get any logic to be stable across systems and varying syntaxes used. Will wait for FreeBSD to add drivers to usbconfig -vl. Note that this makes it not possible to correctly match USB networking devices to their respective IF data, so USB networking IF will fall back to the undetected IF-ID, which means it was found but not connected to a specific hardware device. 2. FreeBSD Battery Report: there are non-objective values for Battery state data in sysctl output, as in minutes remaining, which has no meaning, and percent charge (percent of what? original design capacity? current actual capacity?). If data with voltages, design/current capacity in Ah or Wh, is made available, support will be added. Note that there are 3rd party tools that do supply this data in a usable format, but they are not in core so no point. 3. BSDs All: have found no way to get physical CPU counts. this will lead to odd outputs in some cases, like a 2 cpu system reporting itself as a 2x the actual core counts single CPU, but the data just isn't there as far as I know. Dragonfly in some cases appears to have that data. 4. BSDs All: so far no way to get live per core cpu speeds using a file or fast command query. Thought I'd found a way in FreeBSD but that was not the correct clockrate values, or inconsistently right/wrong, so not using it. Also saw the same issue with max/min frequencies in FreeBSD so removed that item, it's better to show nothing than data that is not reliable or actually not even referring to what it seems to be. 5. BSD SOC Support: An issue poster asked why FreeBSD (but really BSD in general) SOC ARM device, like RaPi, support, was so weak in inxi. The reason is simple: to do SOC ARM device data in a meaningful way requires a complete path based data structure, which the BSDs do not appear to have, at least from what I've seen so far. See Linux's /sys data structures for examples of what is required to add or expand inxi SOC device support in inxi. It's hard even with that type of rich path based data, and without it I won't try. The bright side is inxi runs perfectly on such devices, no errors, which was amazing to see, and spoke volumes of the recent work done to extend support for the BSDs. 6. Perl / inxi, when run as root, shows read error when trying to open a 200 / --w------- permission /sys uevent file for reading. The test works as expected as user, but not as root. Perl will try to read it when run as root even though it has no read permissions, only write. This in reality only manifests on very old /sys, from Debian Etch kernel 2.26 days. -------------------------------------------------------------------------------- BUGS: 1. tput + urxvt / FreeBSD: There appears to be a bug in Arch Linux urxvt that leads to failed terminal/console size from tput. Also while trying to resolve this bug, discovered that if you use "tput cols 2>/dev/null" in FreeBSD, for some inexplicable reason tput puts out defaults 80 cols x 24 rows. Why? Who knows. Added in non numeric tests of output to handle errors from tput instead. The bug appears to be what rxvt reports itself as vs what it is actually running as. This issue isn't present in any other distro I tried, but could just be a new bug in urxvt, don't know. 2. Elbrus CPU: Ongoing issue #197 Elbrus poster gave sample of new 2C3 cpuinfo, that exposed some bugs internally in inxi Elbrus handling, I was using integer values instead of hex for model IDs in the Elbrus logic, which would fail after model 9. 3. BSD dmesg.boot: The logic used for dmesg.boot data processing had errors, and had to be fully redone because of the need to detect in a reliable way the current state of USB drives. This logic now is much more robust and reliable, and no longer relies on using 'uniq' values per line, which would fail in all kinds of situations. 4. OpenBSD USB Speeds: bugs fixed for OpenBSD speeds, these were found during the USB data refactor testing process. 5. BSDs: in some cases, wrong memory used values were being generated, this should be largely corrected now. Also pulled the weird NetBSD use of /proc/meminfo which had wrong data in it, and now use vmstat for all BSDs, which after the used bug fixes, is more reliable for BSDs. 6. All systems: CPU stepping would report as N/A if stepping 0, luckily I came across some systems with an actual stepping: 0, which are not common. 7. FreeBSD: dmidecode sourced L2 cache data failed to show correct totals in some cases. Due to no MT detection possible for FreeBSD currently, these totals will still be wrong, but now it says note; check to let users know. 8. dmidecode: some cases were getting the wrong failure error message, this bug became exposed due to OpenBSD locking /dev/mem even to root, which then failed to show the expected message. This was a bug, and is now corrected. 9. FreeBSD: partition swap size didn't show in at least some cases, that's corrected. 10. Linux Partitions: partitions would let doubled swap items through in several cases, and also failed to create in rare cases matches for hidden partition mapped id's. Finally tracked down the actual cause, when moving the partition filters I'd forgotten to add swap into the filter list, oops. But now it will catch duplicates in several different ways, so that's fine. 11. Unmounted: Failed to properly handle detecting RAID components in the case of lvm, mdraid, it was only working for zfs. This was an accident, and should now be corrected. -------------------------------------------------------------------------------- FIXES: 1. Code Folding: Note that this was NOT a bug or failure in inxi, it was a bug in scintilla/scite geany code editors with folding, basically if you commented out logic, without using a space or other marker after the comment #, folding would break in weird ways. Obviously the core scintilla engine should IGNORE the darned # commented out lines, but it doesn't, which is a real bug. But not in inxi. This was however worth working around, because without folding, you can't work on or learn how inxi works, and the only editor I know of in the free software eco-system that can handle folding reasonably accurately was until now Kwrite/Kate code editors, and those have some real, long standing, weaknesses, and bugs around folding that have never been resolved, and yes, did notify them about them, and no, they remain unfixed after years, or they were fixed briefly, then broke again. So it was important to expand the base of possible code editors to more than just the KDE stuff. Fixing this was tedious, but I think worth it. On the bright side, geany/scite folding / unfolding is FAST, and once the code issues that triggered folding failures were resolved, very accurate, much better than Kate's to be honest, though Kate isn't as picky, but Kate's unfold top nodes has been broken more often than it's worked. To avoid this issue, it's also important to configure geany/scite to use a space after the comment when using keyboard shortcuts to comment out lines/blocks. Same goes for Kate/Kwrite, by the way. 2. Battery: Forgot to add battery-force to -v7, which means you would never see the battery line in full output if there was no battery present, this is similar to how raid-forced worked, it was just an oversight which I hadn't noticed until testing the new BSD battery logic. 3. Indentation: small indentation fixes on Sound Server data. Those are visible with -y1, that is. 4. OpenBSD PCI: enabled Device matching to PCI networking device, this required an odd little hack, but seems to be pretty reliable, and allowed me to add driver to PCI device reports as well. Not sure why driver isn't in pcidump -v but it probably will be in the future. Note to self: add in support for that so if they include it in a future release, it will suddenly 'just work', assume they use the same basic syntax as usbdevs -vv output. 5. BSDs: Added in some null data protections for BSDs, which do not always have all the data types found in Linux, those would trigger Perl undefined value errors, which are warnings that inxi failed internally to test for null data in that, but it's hard to know when to do that when the data is basically always there in Linux. 6. Debugger: Added test for required Net::FTP module in debugger, had forgotten to make that test explicit, which led to odd failures. 7. BSDs: nvme detections should be better now. But I have seen no live test system to confirm the fixes work as expected, plus, at least, OpenBSD swaps nvme0 to sd0 internally, so I'm not actually sure how that data will even work, we'll see how that goes. 8. BSDs: oddly, despite using 0x hex numbers almost everywhere, for CPU stepping, the stepping is in decimal, which is even odder because CPU makers list their steppings as hex in many if not most cases. In case this is corrected in the future, if 0x appears before stepping number, will not then try to convert to hex since it already is. 9a. CPU L3: Subtle, probably won't change behaviors, but L3 cache is per physical CPU in every case I've found, so never multiply value by cores for L3. Like everything, this may lead to corner cases being wrong, but that's life, it will also lead to the data being right for most users. 9b. CPU L1: Different L1 syntaxes found so inxi now uses more loose detections, should cover most OpenBSD L1 variants at least. 10. BSDs: inxi was using internal 'sleep' right before reading /proc/cpuinfo, but that was silly for BSDs since cpu speeds there come from sysctl, so the BSD sleeps are now running before sysctl if CPU data feature is required. 11. Too many to remember, but lots of subtle message output changes to make more clear, more accurate, shorter, whatever. 12. USB: a very subtle fix, some devices can be both audio and video, like cameras, but inxi would default to the first detected. Now it checks for both before going to the list of checks, and correctly assigns a type that is both audio and video to the audio and video hashes so both features will show the USB device, not just Audio. 13: BSD: fixes for BSD ifconfig IF status, it was slicing off the full status string, like 'no network' to 'no', which is silly. Now shows full string. 14. OpenBSD: restored USB Hub ports: xx item, I hadn't realized that the data was still there with usbdevs but it required an extra -v, like: usbdevs -vv to trigger, so now the OpenBSD USB ports works fine again. 15. Fedora Xorg: updated --recommends to use the newer split apart xorg utils package names, only xrandr I think needed updating. Thanks Mr. Mazda for keeping up with that stuff! 16. OpenBSD SMART: the actual device being queried turns out to the 'c' partition, the one that represents the entire disk, NOT the main device ID, like sd0, so now inxi tacks on 'c', sd0c, when smartctl runs, and it works fine. So previously SMART report would never have worked in OpenBSD. 17. Partion labels/uuids: in Partitions and Unmounted, does not show label/uuid if fs type is ffs or if fs is a logical type one, like zfs, hammer, and remote fs mounts etc. This cleans up output, since these file system types will never have labels or uuids. 18. Mr Mazda inxi was missing data and showing errors if run in Debian Etch with Perl 5.008, and I realized I'd slipped up and had used the -k option without testing lspci version, but -k was only available in 3.0 in Lenny. But -v turns on -k automatically, so the easy solution was just to remove the -k and leave the -nnv, which is the same thing, but does not cause errors in early lspci. There are also errors with reading as root some /sys uevent files, but upon examination, those had only root write permission, so the perl -r test isn't right. Don't think that can be fixed. See Can't/Won't fix for more. Another issue I noticed was that in some cases Perl seemed to lose track of some hash values in local %trigger in OptionsHandler, and just lose them, thus leading to things like --help --version --recommends not working. Moving %trigger to globals %show and %use fixed that one, but that's weird, no idea what happened, but it works now. Tested in Sarge 3.1, where core modules have to be explicitly installed, they were not included in base Perl install. Kernel 2.4 had some key differences, different lspci syntax, different /proc/partitions, so the block device output and device output is flawed, but otherwise inxi worked fine in Sarge, from 2005! But these issues will not be corrected, kernel 2.24 is just too old, lol. inxi should always run ok in very old systems, like Etch, back to when Perl 5.8 was standard, so bugs like this are always welcome, it's easy to slip up and use something that didn't work in those old systems, then forget to test. 19. Corner case SMART errors, sometimes occur much later in output than inxi expects, this is now corrected and errors should show in smart data no matter where the main error type occured. -------------------------------------------------------------------------------- ENHANCEMENTS: 1. Elbrus: Going along with Bug 2, Updated Elbrus microarch to use family 6, assuming models 10, 11, are the same, which they should be since 12 is the same as in family 4. 2. IPMI Sensors: More sensor syntax detections, sensors will never be stable... 3. OpenBSD: Rolled out live battery state feature, they have very good data, simple, but solid, that allows for a quality battery state report. Handles both Wh/Ah, though I am slightly suspicious of the reality of the arithmetic for Ah > Wh conversion, it seems to be too high. That's Ah * Design Voltage. But Linux battery data has the same issue, though I think in most cases, the data is in Wh, so this issue isn't BSD specific. My suspicion is that the voltages used to determine Ah may actually be slightly lower than the listed design voltage, which inxi calls min: but it's actually the design voltage. Unknown if NetBSD data is the same as OpenBSD for battery, was unable to locate any samples, so can't say, if you have a NetBSD laptop that correctly reports battery state in sysctl -a, please file an issue with some sample battery charge/voltage syntax and values, ideally from > 1 system. If the data is complete, it's easy to add support. 4a. BSD USB rev: inxi now emulates USB rev versions for BSD USB speed/rev version data. Note that this is not guaranteed to be right, because USB devices can be different rev versions than the speed they run at, but as far as I could find, the USB revision data is not available in any practical sense, unless I create a complicated recursive tool to build up a snapshot of the usb system and devices from dmesg data, but I already blew a day on that attempt, so will wait for more complete data in the usb tools in future. The rev version is based on the device/hub speed, using a standard USB rev speed mapping. But a 12 Mbps device can be rev 2, not rev 1.1, for example, that is, it's actually a USB 2.0 device, but a slow speed one. 4b. USB Type: Expanded fallback USB device type tests, these are useful for cases where it's either a vendor defined type, or for Open/NetBSD, which do not yet show USB class/subclass data. But it's a good fallback tool, added Mass Storage, expanded detections. 5. BSD Sensors: Going along with Enhancement 3, rolled out live sensors data. Confirmed working in OpenBSD and FreeBSD, not sure about NetBSD, no data, problem with vm testing is no sensors, but don't have any NetBSD hardware installs to verify. Stan gave it a good try, but could not get NetBSD running so far, maybe later. This basically means the -B and -s features are largely feature complete for the BSDs as far as practical, though due to difficulties in getting the data in a consistent clear way, some more advanced features, like gpu temps, which are now available in Linux kernel values and lm-sensors, do not yet appear to be present in the BSDs, though if this changes, the structures are in place to make updates to these logics very easy to implement now. Note that the --sensors-include and --sensors-exclude items, or config items, work fine with this BSD logic, though you have to figure out what exact syntax to use, but that's the same in Linux. 6. OpenBSD Pledge: Yes, that's right, inxi is now Pledged!!! In OpenBSD, anyway, they did a really good job, and the OpenBSD Perl packager made a very nice Perl modules, OpenBSD::Pledge, which was very easy to implement. Now I know what inxi needs to run its features!! So far OpenBSD only, but Pledge seems like a really good idea, so I figured, let's give it a spin, even if it will only currently work on OpenBSD, but that's fine, inxi is pledged as tightly as I could make it, including unpledging features not required post options processing, once inxi knows what it's actually going to be doing. Note that I'm aware of OpenBSD::Unveil, but that's a lot harder to implement due to never really being sure about what files inxi will need to be looking at until well into the logic. I may look at that in the future. 7. Bluetooth Rfkill: Due to ongoing failures in current inxi to show consistent Bluetooth hci report on Linux, added in one last fallback, rfkill state, which allows inxi to always fallback to at least that basic data. Also added in which tool is providing the report mostly, like: Report: bt-adapter ID: hci0 and so on. Also integrated into -xxx data, or for down state, the full rfkill report, since that can be quite useful. Note that bluetooth is a real pain for users to debug because you can have: * Bluetooth Service: enabled/disabled * Bluetooth Service: started/stopped * bluetoothctl: start/stop * bt-adapter: start/stop * hciconfig: start/stop * rfkill: software: block/unblock; hardware: block/unblock - however, for hardware, that means a physical button has been pressed to disable it, on the laptop that is. To make matters worse, one tool does not always even know when another tool has changed something, for example, if I rfkill blocked hci0, then unblocked it, hciconfig would keep seeing it as down until it was switched to on with hciconfig explicitly. This is I suspect one reason hciconfig is being dropped, it doesn't know how to listen to the newer tools like bluetoothctl, bt-adapter, or rfkill. 8. OpenBSD: Going along with Code Change 1, now has disk serial (doas/root), more consistent physical block size data, more reliable disk data, and for -Dxxx, duid, if available. Also added disk partition table scheme, aka MBR / GPT. Some of these new items may also work with NetBSD. See also Fix 17, SMART fix for OpenBSD. 9. OpenBSD/NetBSD/FreeBSD: the DiskDataBSD refactor now allows Unmounted partitions report. 10. OpenBSD: added in CPU MT detections using siblings data, I think only OpenBSD and Dragonfly support proper MT cpu core counts. Still no way to get physical cpu counts in OpenBSD or FreeBSD or NetBSD that I am aware of. 11. OpenBSD: added in cpu speed min/max data, that was available in most cases, didn't realize that. 12. BSDs: expanded and made more robust cpu L1/L2/L3 cache detections, now for example, OpenBSD will report its L1/L2/L3 cache without root. FreeBSD requires root since that data is coming from dmidecode. This logic update made BSD L-cache data much more reliable and consistent, and, important, easy to work with. This was directly connected to Code Changes 2 and 3, which made dealing with those data sources a lot easier. Note that L1/L2 cache data if not from OpenBSD will show note: check because it's not possible to determine if it's a multithreaded MT cpu or not, and thus if L1/L2 * core count would so often be totally wrong that inxi won't try to guess, it will just list the single value found, and tell the user to check it themselves. 13. OpenBSD: Added rcctl tool to init tools, I hadn't known about that one, that replaces the fallback default used before, /etc/rc.d. 14. RAM Vendor: Issue #245 raised the point that it would be good to try to show RAM vendor data when the manufactorer field is empty, and since that logic is already present in disk_vendor, it was just matter of researching the product IDs to find the matching patterns for the RAM vendors, the initial list is pretty good, but will need updates now and then to correct errors. Also will override only vendor ID 4 character hex value and see if it can find a better value. 15. OpenBSD RAM: data quality is decent (no vendor/product no, unfortunately). The data is often, but sadly not always, available. I'm not clear why sometimes it isn't, but since OpenBSD also defaults to blocking /dev/mem to even root user, which then blocks dmidecode, this is the only practical way to give basic RAM data for OpenBSD, so that's running fine now, when the data is available, with the added bonus of not needing doas/root. Note that due to the way that this data is present, I can have inxi deduce some things like how many arrays there are, and then guess at overall capacity, max stick size, and so on, but all Array-x: values are followed by note: est because they are never based on hard data, just extrapolations. I debated if inxi should even show the guesses, but I think by saying note: est after each Array-x: item, it's pretty clear that it's not hard data, and it does give an idea roughly. I made an initial guess at > 1 ram array but found no data samples to let me see if my guess was right or not, so > 1 array remains roughly theoretical until shown to work or not work empirically. While NetBSD sometimes has the system ram data in a similar way that OpenBSD does in dmesg.boot, it varies too much, and is too inconsistent. There are not enough data samples with good consistent data, and the samples I did see suggested that it would take too much code and convoluted logic to handle the variations, so I'm leaving this one alone. Also, NetBSD probably doesn't block /dev/mem so dmidecode should work fine. 16. Using system clang version info for OpenBSD kernel compiler, the assumption being that a BSD is an OS, so the Clang version it shipped with would be the clang version that compiled the kernel. Please correct if this is wrong. 17. OpenBSD RAID: support added for softraid, including for drive storage totals, unmounted raid component detections. Plugged in pretty smoothly, able to generate a partial report for non root, and shows message if not root. 18. VM detections upgraded, particularly for BSDs, now includes vmm, hvm, hyper-v, kvm. Not all of these would have been detected before. Also cleaned up vm logic, moved all vm detections into $dboot{'machine-vm'}, and only use the first found item. 19. Disk Vendors!!: Yes, last, but not least!! More disk vendors, vendor ID matches!! Yep. What else can I say? Eternity? Man's quest for something that cannot be found, yet these strivings never cease, here manifested by always new vendors and ID matches! -------------------------------------------------------------------------------- DOCUMENTATION: 1. Very significant ongoing upgrades to the docs in inxi-perl/docs/, particularly in inxi-values.txt, inxi-resources.txt, and inxi-data.txt. These are now increasingly useful, and I am trying to keep in particular inxi-values.txt up to date as a primary reference for various features, though it will always lag, because that's how it is, lol. 2. Cleaned up changelog, made 80 cols wide for text, bars, etc, made numbered lists and headers consistent, but otherwise did not change any of the actual content. -------------------------------------------------------------------------------- CODE CHANGES: 1. Complete rewrite of BSD disk/partition data tools, now there is one core tool that generates a mega-disk/partition hash, which is then used for all features that need partition/disk data. This worked out super well, and allowed new features like BSD Unmounted disk data to be generated for the first time ever, along with filling in various block device fields that were missing before. 2. Change 1 also went along with a refactor of dmesg data tool for BSDs, which allowed for much more granular data generation, along with a complex %dboot hash which stores all sub types as well as the main full dataset. This allowed inxi to stop looping through all of dmesg data each time a feature needed it. Now all the data types are assigned if required by a feature, and only then. This, along with change 1, worked really well. See also Bug 3, which mandated completely changing how dmesg.boot and dmesg live data were / are merged, the result is far more robust now, and far less prone to error. 3. Similar to dmesg changes, used same methods for sysctl data, now all the data is assigned to %sysctl data structure based on if needed or not, so it only does the assignments one time, in one location. Much cleaner code this way, and allows for testing set/unset substructures, like $sysctl{'cpu'}. 4. The %dboot and %sysctl refactors went so well that I switched the core USB and Devices to also use %usb and %devices structures. These updates let me dump a lot of global hashes and arrays, and leaned everything down a lot, and also removed basically all the testing loops for these data types, now the Item features just test to see if a reference to the specific type exists, if it does, it has data, if not, it doesn't, this is a lot easier to manage. 5. Ongoing: moving related subroutines to Packages, the goal is to have pretty much all related subroutines (functions) contained in parent classes/packages, makes it easier to maintain. 6. Ongoing: making all internal package tools have similar sub names, getting rid of the specific names for output and data generator functions. This makes each Item Generator increasingly like all the others, as much as practical. 7. A big one, renamed all the feature generators to be XxxxxItem, instead of XxxxData, which was colliding as a package name with actual data generator tools, now all the Feature generators are [Feature]Item, and all the Data generators have Data type names where relevant. This avoided in particular the silly case where I was relying on case to differentiate UsbData and USBData, feature vs data generator. 8. As part of the move to data hash global structures, also moved as many of the top global scalars and hashes and arrays to these now much more heavily utilized global hashes, like %alerts, %use, %fake, %force, and so on. There are now far fewer globals running than before, and where it makes sense, I keep moving them into global hashes, and giving the global hashes more work to do. 9. Significantly expanded list of debuggers for specific data types always available, see docs/inxi-values.txt for list of options there. Decided for rapid development, it was too much of a pain to always be uncommenting the debuggers, so now am uncommenting, adding to @dbg supported items, then documenting. I guess this means the @dbg items are more or less stable and consistent now, give or take. 10. Refactored UsbData and DeviceData, for in particular the BSDs, to be much more robust and to rely less on very fragile regex parsing patterns, takes more lines of code, but better than having the detections break every other BSD release. This was part of the %device and %usb refactors as well. 11. Fixed system_files() too, which was really silly logic, it used a global packed hash of system files, then would do a function call for the paths when required, which was redundant since the values were already in a hash which could be used directly. This was a throwback to inxi gawk/bash, where hashes were not really used in this way, and the logic had been translated to Perl without thinking about it, but once I thought about it, I realized how silly that was. This must have knocked off a good 50 or more unnecessary, and always expensive, function calls.	2021-04-16 20:41:58 -07:00
Harald Hope	3d4d1f533c	Bugs!! Fixes! Spring cleaning! ... Because these are either newly created, or newly discovered, bugs, this release was pushed as early as possible to get them fixed asap. BUGS: 1. Desktop: Lumina detection had a syntax error which made it not work. This has been broken for a while. 2. Logical: if not root, and if LUKS / bcache detected, failed to load proc_partitions, which generates error on --logical --admin since the required components data was not loaded. This was an oversight. 3. The 3.3.02 ShellData refactor created a bug for console IRC, showed shell, not irc client, name, and set default shell data which also showed. 4. Console IRC tty: there was also an older bug that made -S, -G not work consistently, and there were errors that had been missed for many years in that logic. These should all be corrected, console irc out of display, or in display as root, should now show tty info, tty size in -G. FIXES: 1. Memory: restored $bsd_type block on /proc/meminfo and force NetBSD to use a corrected vmstat. This leaves that block of logic to correct the NetBSD oddities in meminfo, but it may fix future isses that popup. 2. -Sxxx man page item incorrectly said XDG_VTNR was systemd/linux, it's not, it's various things, GhostBSD has it, for example. See what you get for believing what people say! 3. Logical: added in N/A for null maj-min in --logical report. While bug 2 triggered those errors, there could be future cases where maj-min are null, like BSD lvm data etc. ENHANCEMENTS: 1. Going along with Fix 1, added '--force meminfo' in case you really want that. 2. Distro: System Base: Added TrueNAS detection. 3. Package Data: Added mport [MidnightBSD] type. That requires root to run for some odd reason, so won't see the best output if not root. CHANGES: 1. Moved logical to -v7 from -v8, it's stable enough now. CODE CHANGES: 1. Moved get_tty_number and get_tty_console_irc to ShellData:tty_number and ShellData::tty_console_irc. ShellData::tty_number was being loaded several times, added $loaded{'tty-number'} test, and made client{'tty-number'} to store value. tty_console_irc changed to console_irc_tty, which is what it gets, removed hacks and made it load once and store result in client hash. 2. Optimization: retested sub vs package::method and they run at exactly the same time, give or take, so moving more stuff into packages to make it easier to maintain.	2021-03-17 19:39:02 -07:00
Harald Hope	75433a383a	Huge upgrade!! Bug Fixes!! Refactors!!! BSDs!!! More BSDs!!! ... raspberry pi!! New Features!!! Enhanced old features!!! Did I mention bluetooth?! USB? Audio? No? well, all hugely upgraded! ------------------------------------------------------------------------ BUGS: 1. Sadly, 3.3.01 went out with a bug, forgot to remove a debugger, resulted in hardcoded kernel compiler version always showing. Note that there is a new inxi-perl/docs/inxi-bugs.txt file to track such bugs, and matched to specific tagged releases so you know the line number and items to update to fix it. 2. Typo in manjaro system base match resulted in failing to report system base as expected. ------------------------------------------------------------------------ KNOWN ISSUES BUT CAN'T OR WON'T BE FIXED: 1. OpenBSD made fvwm -version output an error along with the version, and not in the normal format for standard fvwm, this is just too complicated to work around for now, though it could be in theory by creating a dedicated fvwm-oBSD item in program_values. But that kind of granularity gets too hard to track, and they are likely to change or fix this in the future anyway. Best is they just restore default -version output to what it is elsewhere, not nested in error outputs. 2. Discovered an oddity, don't know how widespread this is, but Intel SSDs take about 200 milliseconds to get the sys hwmon based drive temps, when it should take under a millisecond, this may be a similar cause as those drives having a noticeable SMART report delay, not sure. This is quite noticeable since 200 ms is about 15% of the total execution time on my test system. ------------------------------------------------------------------------ FIXES: 1. For --recommends, added different rpm SUSE xdpyinfo package name. 2. Distro Data: added double term filter for lsb-release due to sometimes generating repeated names in distro. 3. Packages: fix for appimage package counts. 4. Desktop: fixed ID for some wm when no xprop installed, fallback to using @ps_cmd detections, which usually work fine. 5a. When swap used was 0, showed N/A, fixed to correctly show 0 KiB. 5b. If no swap devices found, BSDs were not correctly showing no swap data found message. Corrected. 6a. Bluetooth: Removed hcidump from debugger, in some cases, that will just hang endlessly. Also wrapped bluetoothctl and bt-adapter debugger data collection with @ps_cmd bluetooth running test. Only run if bluetooth service is running. 6b. Bluetooth: running detections have to be very strict, only bluetoothd, not bluetooth, the latter can show true when bluetoothd is not running, and did in my tests. 7. USB: with Code Change 1, found a few places where fallback usb type detections were creating false matches, which resulted in say, bluetooth devices showing up as network devices due to the presence of the word 'wireless' in the device description. These matches are all updated and revised to be more accurate and less error prone. 8. Battery: an oversight, had forgotten to have percent used of available capacity, which made Battery data hard to decipher, now it shows the percent of available total, as well as the condition percent, so it's easier to understand the data now, and hopefully more clear. 9a. OpenBSD changed usbdevs output format sometime in the latest releases, which made the delicate matching patterns fail. Updated to handle both variants. They also changed pcidump -v formatting at some point, now inxi will try to handle either. Note that usbdevs updates also work fine on NetBSD. 9b. FreeBSD also changed their pciconf output in beta 13.0, which also broke the detections completely, now checks for old and new formats. Sigh. It should not take this much work to parse tools whose output should be consistent and reliable. Luckily I ran the beta prior to this release, or all pci device detections would simply have failed, without fallback. 9c. Dragonfly BSD also changed an output format, in vmstat, that made the RAM used report fail. Since it's clearly not predictable which BSD will change support for which vmstat options, now just running vmstat without options, and then using processing logic to determine what to do with the results. 10. It turns out NetBSD is using /proc/meminfo, who would have thought? for memory data, but they use it in a weird way that could result in either negative or near 0 ram used. Added in some filters to not allow such values to print, now it tries to make an educated guess about how much ram the system is really using based on some tests. 11. Something you'd only notice if testing a lot, uptime failed when the uptime was < 1 minute, it had failed to handle the seconds only option, now it does, seconds, minutes, hours:minutes, days hours:minutes, all work. 12. Missed linsysfs type to exclude in partitons, that was a partner to linprocfs type, both are BSD types. 13. Added -ww to ps arguments, that stops the cutting width to terminal size default behavior in BSDs, an easy fix, wish I'd known about that a long time ago. 15. gpart seems to show sizes in bytes, not the expected KiB, so that's now handled internally. Hopefully that odd behavior won't randomly change in the future, sigh. 16. Fixed slim dm detection, saw instance where it's got slim.pid like normal dms, not the slim.lock which inxi was looking for, so now inxi looks for both, and we're all happy! ------------------------------------------------------------------------ ENHANCEMENTS: 1. Added in something that should have been there all along, now inxi validates the man page download as well as the self, this avoids corrupted downloads breaking the man. 2. Init: added support for shepherd init system. 3. Distro Data: added support for guix distro ID; added support for NomadBSD, GhostBSD, HardenedBSD system base. GhostBSD also shows the main package version for the distro version ID, which isn't quite the same as the version you download, but it's close. Also added os-release support for BSDs, using similar tests as for linux distros, that results in nicer outputs for example for Dragonfly BSD. 4. Package Data: added guix/scratch [venom]/kiss/nix package managers. Update for slackware 15 package manager data directory relocation, now handles either legacy current or future one. 5. Repos: added scratch/kiss/nix-channels; Added GhostBSD, HardenedBSD pkg repos. 6. USB Data: added usbconfig. That's FreeBSD's, and related systems. 7. Device Data: Added pcictl support, that's NetBSD's, I thought inxi had supported that, but then I remembered last time I tried to run netBSD in a vm, I couldn't get it figured out. Now debugged and working reasonably well. 8. Raspberry Pi 3, 4: ethernet nic now detected; wifi device, which is on a special mmcnr type, now works, that stopped working in pi 3, due to the change, now it's handled cleanly. Also added support for pi bluetooth, which lives on a special serial bus, not usb. For Raspberry Pi OS, added system base detections, which are tricky. Also matched mmcnr devices to IF data, which was trickyy as well. Note that as far as I could discover, only pi puts wifi on mmcnr. 9. Bluetooth: due to deprecated nature of the fine hciconfig utility, added in support for bt-adapter, which also allows matching of bluetooth data to device data, but is very sparse in info supplied compared to hciconfig. bluetoothctl does not have enough data to show the hci device, so it's not used, since inxi can't match the bluetooth data to the device (no hci[x]). This should help the distros that are moving away from hciconfig, in particular, AUR is only way arch users can get hciconfig, which isn't ideal. 10. New tool and feature, ServiceData, this does two things, as cross platform as practical, show status of bluetooth service, this should help a lot in support people debugging bluetooth problems, since you have bluetooth enabled but down, or up, disabled, and you can also have the device itself down or up, so now it shows all that data together for when it's down, but when the device is up, it just shows the device status since the other stuff is redundant then. In -Sa, it now shows the OS service manager that inxi detected using a bunch of fallback tests, that's useful to admins who are on a machine they don't know, then you can see the service manager to use, like rc-service, systemctl, service, sv, etc. 11. Big update for -A: Sound Servers: had always been really just only ALSA, now it shows all detected sound servers, and whether they are running or not. Includes: ALSA, OSS, PipeWire, PulseAudio, sndio, JACK. Note that OSS version is a guess, might be wrong source for the version info. 12. Added USB device 'power:' item, that's in mA, not a terrible thing to have listed, -xxx. This new feature was launched cross platform, which is nice. Whether the BSD detections will break in the future of course depends on whether they change the output formats again or not. Also added in USB more chip IDs, which can be useful. For BSDs, also added in a synthetic USB rev, taken from the device/hub speeds. Yes, I know, USB 2 can have low speed, full speed, or high speed, and 1.1 can have low and full speeds, so you actually can't tell the USB revision version from the speeds, but it's close enough. 13. Made all USB/Device data the same syntax and order, more predictable, bus, chip, class IDs all the same now. 14. Added in support for hammer and null/nullfs file system types, which trigger 'logical:' type device in partitions, that's also more correct than the source: Err-102 that used to show, which was really just a flag to alert me visibly that the partition type detection had simply failed internally. Now for detected types, like zfs tank/name or null/nullfs, it knows they are logical structures. 15. Expanded BSD CPU data, where available, now can show L1/L2/ L3 cache, cpu arch, stepping, family/model ids, etc, which is kind of nifty, although, again, delicate fragile rules that will probably break in the future, but easier to fix now. 16. By an old request, added full native BSD doas support. That's a nice little tool, and it plugged in fairly seamlessly to existing sudo support. Both the internal doas/sudo stuff should work the same, and the detection of sudo/doas start should work the same too. 17a. Shell/Parent Data: Big refactor of the shell start/parent logic, into ShellData which helped resolve some issues with running-in showing shell name, not vt terminal or program name. Cause of that is lots of levels of parents before inxi could reach the actual program that was running inxi. Solution was to change to a longer loop, and let it iterate 8 times, until it finds something that is not a shell or sudo/doas/su type parent, this seems to work quite well, you can only make it fail now if you actually try to do it on purpose, which is fine. This was very old logic, and carried some mistakes and redundancies that made it very hard to understand, that's cleaned up now. Also restored the old (login) value, which shows when you use your normal login account on console, some system will also now show (sudo,login) if the login user sudos inxi, but that varies system to system. 17b. BSD running-in: Some of the BSDs now support the -f flag for ps, which made the parent logic for running-in possible for BSDs, which was nice. Some still don't support it, like OpenBSD and NetBSD, but that's fine, inxi tests, and if no support detected, just shows tty number. Adding in more robust support here cleaned up some redundant logic internally as well. 17c. Updated terminal and shell ID detections, there's quite a few new terminals this year, and a new shell or two. Those are needed for more reliable detections of when the parent is NOT a shell, which is how we find what it is. 18. Added ctwm wm support, that's the new default for NetBSD, based on twm, has version numbers. 19. Upgraded BSD support for gpart and glabel data, now should catch more more often. 20. For things like zfs raid, added component size, that doesn't always work due to how zfs refers to its components, but it often does, which is better than never before. 21. To make BSD support smoother, got rid of some OpenBSD only rules, which in fact often apply to NetBSD as well. That may lead to some glitches, but overall it's better to totally stay away from OpenBSD only tests, and all BSD variant tests, and just do dynamic testing that will work when it applies, and not when it doesn't. In this case, added ftp downloader support for netBSD by removing the openBSD only flag for that item. There's a bit of a risk there in a sense since if different ftp programs with different options were to be the fallback for something else, it might get used, but that's fine, it's a corner case, better to have them all work now than to worry about weird future things. But limiting it to only BSDs should get rid of most of the problem. vmstat and optical drive still use net/openbsd specifics because it is too tricky to figure out it out in any more dynamic way. 22. For -Sxxx, added if systemd, display, virtual terminal number. Could be useful to debug subtle issues, if the user is for example not running their desktop in vt 7, the default for most systems. ------------------------------------------------------------------------ CHANGES: 1. Moved battery voltage to -Bx output, the voltage is quite important to know since that is the key indicator of battery state. If voltage is within .5 volts of specified minimum, shows voltage for -B since that's a prefail condition, it's getting close to death. 2. In partitions and raid, when the device was linear raid logical type layout, it said, no-raid, when it should be 'linear', that's now cleaner and more correct. 3. When running-in is a tty value, it will now show the entire tty ID, minus the '/dev/tty', this will be more precise, and also may resolve cases where tty was fully alpha, no numbers, previously inxi filtered out everything that was not a number, but that can in some tty types remove critical tty data, so now it will show: running-in: tty 2 [not changed]; tty pts/2 [adds pts/]; tty E2 [adds the E]; tty rx [would have not shown at ll before] ------------------------------------------------------------------------ CODE CHANGES: NOTE: unlike the previous refactors, a lot of these changes were done to make inxi more maintainable, which means, slightly less optimized, which has been my preference in the past, but if the stuff can't be maintained, it doesn't matter how fast it runs! These changes have really enhanced the quality of the code and made it a lot easier to work with. It's also now a lot easier to add debuggers, force/fake data switches, etc, so it gets done, unlike before, when it was a pain, so it got skipped, and then caused bugs because of stray debuggers left in place, and so on. The bright side is while reading up on this, I learned that using very large subs is much more efficient than many small ones, which I've always felt was the case, and it is, so the style used internally in inxi proves to be the best one for optimizations. These refactors, ongoing, have now touched at least 1/3, almost 1/2, of the entire inxi codebase, so the stuff is getting more and more consistent and up to date, but given how old the logic is in places, there will be more refactors in the future, and maybe once the code is easier to maintain, some renewed optimizations!, if we can find anything that makes sense, like passing array/hash references back to the caller, already the first half is done, passing references to the sub/method always. The second part is started, using the Benchmark Perl module, which really speeds up testing and helps avoid pointless tweaks that do little re speed improvements. I could see with some care some areas where working on data directly via references could really speed things up, but it's hard to write and read that type of code, but it's already being done in the recursive data and output logics, and a few other places. 1. Large refactor of USBData, that was done in part to help make it work for BSDs better, but also to get it better organized. This refactor also made all the device items, like -A,-G,-N,-E use the same methods for creating USB output, previously they had used a hodgepodge of methods, some super old, it was not possible to add USB support more extensively for BSDs without this change. Also added in some fallback usb type detection tools using several large online collections of that info to see what possible matching patterns could catch more devices and correctly match them to their type, which is the primary way now that usb output per type is created. This really helps with BSDs, though BSD usb utilities suffer from less data than lsusb so they don't always get device name strings in a form where they can be readily ID'ed, but it's way better than it was before, so that's fine! Moved all previous methods of detecting if a card/device was USB into USBData itself so it would all be in one place, and easier to maintain. All USB tools now use bus_id_alpha for sorting, and all now sort as well, that was an oversight, previously the BSD usb tools were not sorted, but those have been enhanced a lot, so sorting on alpha synthetic bus ids became possible. Removed lsusb as a BSD option, it's really unreliable, and the data is different, and also varies a lot, it didn't really work at all in Dragonfly, or had strange output, so lsusb is now a linux only item. 2. Moved various booleans that were global to %force, %loaded, and some to the already present, but lightly used, %use hashes. It was getting too hard to add tests etc, which was causing bugs to happen. Yes, using hashes is slower than hardcoding in the boolean scalars, but this change was done to improve maintainability, which is starting to matter more. 3. Moved several sets of subs to new packages, again, to help with debugging and maintainability. MemoryData, redone in part to handle the oddities with NetBSD reporting of free, cached, and buffers, but really just to make it easier to work with overall. Also moved kernel parameter logic to KernelParameters, gpart logic to GpartData, glabel logic to GlabelData, ip data IpData, check_tools to CheckTools, which was also enhanced largely, and simplified, making it much easier to work with. 4. Wrapped more debugger logic in $fake{data} logic, that makes it harder to leave a debugger uncommented, now to run it, you have to trigger it with $fake{item} so the test runs, that way even if I forget to comment it out, it won't run for regular user. 5. Big update to docs in branch inxi-perl/docs, those are now much more usable for development. Updated in particular inxi-values.txt to be primary reference doc for $fake, $dbg, %force, %use, etc types and values. Also updated inxi-optimization.txt and inxi-resources.txt to bring them closer to the present. Created inxi-bugs.txt as well, which will help to know which known bugs belonged to which frozen pools. These bugs will only refer to bugs known to exist in tagged releases in frozen pool distros. 6. For sizes, moved most of the sizing to use main::translate_size, this is more predictable, though as noted, these types of changes make inxi a bit slower since it moved stuff out of inline to using quick expensive sub calls, but it's a lot easier to maintain, and that's getting to be more important to me now. 7. In order to catch live events, added in dmesg to dmesg.boot data in BSDs, that's the only way I could find to readily detect usb flash drives that were plugged in after boot. Another hack, these will all come back to bite me, but that's fine, the base is easier to work on and debug now, so if I want to spend time revisiting the next major version BSD releases, it will be easier to resolve the next sets of failures. 8. A big change, I learned about the non greedy operator for regex patterns, ?, as in, .*?(next match rule), it will now go up only to the next match rule. Not knowing this simple little thing made inxi use some really convoluted regex to avoid such greedy patterns. Still some gotchas with ?, like it ignores following rules that are zero or 1, ? type, and just treats it as zero instances. But that's easy to work with. 9. Not totally done, but now moved more to having set data tools set their $loaded{item} value in get data, not externally, that makes it easier to track the stuff. Only where it makes sense, but there's a lot of those set/get items, they should probably all become package/classes, with set/get I think. 10. Optimized reader() and grabber() and set_ps_aux_data(), all switched from using grep/map to using for loops, that means inxi doesn't have to go through each array 2x anymore, actually 4x in the case of set_ps_aux_data(). This saved a visible amount of execution time, I noticed this lag when running pinxi through NYTProf optimizer, there was a quite visible time difference between grabber/reader and the subshell time, these optimizations almost removed that difference, meaning only the subshell now really takes any time to run. Optimized url_cleaner and data_cleaner in RepoData, those now just work directy on the array references, no returns. Ran some more optimization tests, but will probably hold off on some of them, for example, using cleaner() by reference is about 50% faster than by copy, but redoing that requires adding in many copies from read only things like $1, so the change would lead to slightly less clean code, but may revisit this in the future, we'll see. But in theory, basically all the core internal tools that take a value and modify it should do that by reference purely since it's way faster, up to 10x.	2021-03-15 18:44:00 -07:00
Harald Hope	d11f2a7a89	small man fix	2021-02-08 17:15:46 -08:00
Harald Hope	2b49b32223	Bug fixes!! Fixes!!! Refactors!!! Edits!!! ... Bugs: 1. Big bug, 3.2 appears to have introduced this bug, for disks, rotation and partition scheme would never show, oops. 2. Tiny bug kept one specific smart value from ever showing, typo. Fixes: 1. Accidentally followed Arch linux derived distro page, which claims KaOS as arch derived, when of course it's not, it's its own distro, own toolchain, etc. I kind of knew this but had forgotten, then I believed the Arch derived distro page, oh well. Resulted in KaOS being listed with arch linux as system base with -Sx. Arch should fix this, it's not like it's hard, just remove the distro from the page. 2. Cleared up explanations for drivetemp vs hddtemp use, updated --recommends, man, and help to hopefully make this clear. Debian will be dropping hddtemp, which is not maintained, sometime in the coming years, sooner than later. Note that users unfortunately have to manually enable drivetemp module unless their distros enable it by default, but the man/recommands/help explain that. 3. Fixed smart indentation issues, that went along with code change 1, was failing to indent one further level for failed/age values like it's supposed to. Enhancements: 1. Added /proc/device to debugger, that will help track block device main numbers 2. More disk vendors, more disk vendor IDs!!! As noted, the enternal flow flows eternally, thanks linux-lite hardware database users!! and other inxi users, whose outputs sometimes reveal a failure or two. 3. Added loaded kernel module tests to --recommends, this was mostly to let users know that drivetemp is needed if you want non superuser fast drive temps, and that this came along with kernels 5.6 or newer. Hopefully word will start drifting out. Note that if inxi is using drivetemp values, drive temps will appear as regular user with -Dx, and will be to 1 decimal place. hddtemp temps are integers, and requires sudo to display the temps. 4. To handle issue #239 which I'd thought of trying off and on, but never did, added option to -Dxxx to show SSD if a positive SSD ID was made to rotation: So rotation will show either nothing, if no rotation or ssd data is detected, the disk speed in rpm, or SSD if an SSD device. There may be corner cases where this is wrong, but I don't have data for that, for example, if a disk is parked and has zero rotation but is a HDD, not as SSD. I don't know what the data looksl ike in that case. Note that if sudo inxi -Da is used, and smartctl is installed, it should be right almost all the time, and with regular -Dxxx, it's going to be right almost always, with a few corner cases. That slight uncertainty is why I never implemented this before. Legacy drives also sometimes did not report rotation speeds even when HDD, so those may create issues, but inxi will only call it an SSD if it's an nvme, mmcblk device, both are easy to ID as SSD, or if it meets certain conditions. It will not call a drive an SSD if it was unable to meet those conditions. INTERNAL CODE CHANGES: 1. Refactored the output logic for DiskData, that was messy, split it into a few subs, and also refactored the way smartctl data was loaded and used, that's much cleaner and easier to use now. Split the previous 1 big sub into: totals_output(), drives_output(), and smart_output(). Also split out the smart field arrays into a separate sub, which loads references to avoid creating new arrays and copying them all over when outputting smart data. References are weird to work with directly but they are MUCH faster to use, so I'm moving as much of the internal logic to use array raferences instead of dereferenced arrays/hashes assigned to a new array, or hash. 2. Redid all the output modules and renamed them to be more consistent and predictable, and redid the logic here and there to make the get() items be fairly similar on all the data builder packages. Now as with the data subs, which generally end in _data, now most of the output subs end with _output. 3. Roughly finished the process started in 3.2, got rid of redundant array loads, changed: @something = something_data(); push (@rows,@something); to: push (@rows,something_data()); which avoids creating an extra array, this also let me remove many arrays overall. 4. Missed a few hashes in machine data that were being passed directly, not as references, to other subs, corrected that. I think I missed those because they were %, so the search I did for @ in sub arg lists didn't catch the % hashes.	2021-02-08 17:07:34 -08:00
Harald Hope	a68b1e8358	Bug fixes!! New Feature!! Edits, cleanups!! ... Bugs: 1. Small bug, wrong regex would make mdraid unused report never show. Was looking for ^used, not ^unused. No idea how that happened, but it's fixed. 2. Big RAID bug. Due to never having seen an 'inactive' state mdraid dataset, inxi had a bunch of bugs around that. I'd assumed active and inactive would have roughly the same syntax, but they don't. This is now corrected. Thanks Solus user for giving me the required data. This case when not corrected resulted in a spray of errors as RAID ran, and a fairly incomplete RAID report for mdraid. 3. A bug that probably never impacted anyone, but in SMART the matching rules failed to match field name Size[s]? in the logical/physical block sizes. However, those were already coming in from I believe pre-existing /sys data for the drives but now it's fixed anyway. I had not realized that smartctl made it plural when logical/physical were different, and singular when they were the same. Fixes: 1. Going along with bug 2, fixed some other admin/non admin report glitches. Made patterns more aggressively matching, whitelist based to avoid the types of syntax issues that caused bug 2. 2. Added 'faulty' type to mdraid matches, that had not been handled. 3. Found even more of those pesky 'card' references in help and man page, replaced all of them with 'device[s]'. 4. Subtle fix, for debugger data collectors, added -y1 support, which can be useful at times. Enhancements: 1. In USB data grabber, added fallback case for unspecified type cases, now uses a simple name/driver string test to determine if it's graphics, audio, or bluetooth. This was mainly to make sure bluetooth usb devices get caught. 2. New feature! -E/--bluetooth. Gives an -n like bluetooth Device-x/Report. Requires for the 'Report:' part hciconfig, which most all distros still have in their repos. With -a, shows an additional Info: line that has more obscure bluetooth hci data: acl-mtu sco-mtu, link-policy, link-mode, service-classes. This closes the ancient, venerable issue #79, filed by mikaela so many years ago. Better late than never!! However, features like this were really difficult in legacy bash/gawk inxi 2.x, and became fairly easy with inxi 3.x, so I guess we'll slowly whittle away at these things when the mood, and global pandemic lockdowns, make that seem like a good idea... Includes a small lookup table to match LMP number to Bluetooth version (bt-v:), hopefully that's a correct way to determine bluetooth version, there was some ambiguity about that. -x, -xx, and -xxx function pretty much the same way as with -A, -G, and -N devices, adding Chip IDs, Bus IDs, version info, and so on. Since this bluetooth report does not require root and is an upper case option, it's been added to default -F, similar to -R, and -v 5, where raid/bluetooth shows only if data is found. With -v7 or -R or -E, always shows, including no data found message. Includes a fallback report Report-ID: case where for some reason, inxi could not match the HCI ID with the device. That's similar to IF-ID in -n, which does the same when some of the IFs could not be matched to a specific device. 3. For -A, -G, -N, and -E, new item for -xxx, classID, I realized this is actually useful for many cases of trying to figure out what devices are, though most users would not know what to do with that information, but that's why it's an -xxx option! 4. Yes! You've been paying attention!! More disk vendors, and new vendor IDs!! The cornucopia flows its endless bounty over the grateful data collector, and, hopefully, inxi users!! Thanks as always, linux-lite hardware database, and linux-lite users who really seem set on the impossible project of obtaining all the disks/vendors known to man. Changes: 1. Small change in wording for mdraid report: 'System supported mdraid' becomes 'Supported mdraid levels' which is cleaner and much more precise.	2021-01-28 20:02:42 -08:00
Harald Hope	1e2d470c69	That damned Kate editor bug where it randomly sprays out characters ... that were in the desktop clipboard caused 3 random pastes of the characters 'failed' into the man page. Kate needs to get their damned crap in order!!! It's becoming unusable.	2021-01-13 17:32:13 -08:00
Harald Hope	6e4cd28791	New version, man page, bug fixes, changes, adjustments and cleanups!!! ... Special thanks to mr. mazda for his ongoing suggestions, ideas, and observations. Bugs: 1. In certain corner cases, it appears that lsusb has blank lines, which tripped errors in inxi output when the usb parser was trying to access split keys that did not exist. Added in check to make sure split actually resulted in expected data. 2. A red face bug, I'd left the output debugger switched on with json output, so it was printing out the json data structure with Dumper, that's now switched off. Hope this doesn't mess anyone up, but it would have mattered only if the person was using: --output json --output-type print It did not effect xml output. Fixes: 1. Got rid of extra level of -L data structure and output handler. Not visible to users, but still irksome, so nice to get that fixed. Recursive structures are confusing, lol, but this extra level was pointless, but to fix it required redoing the logic a bit for both data generator and output feature. 2. Added in support for --display :0.0, previously it did not support the .0 addition, but why not, if it works for people, good, if not, makes no difference. 3. There were some missing cases for LVM missing data messages, so the following fixes were added: * In cases where lsblk is installed and user is non root, or lvs is not installed, but no lvm data is present, inxi now shows the expected 'Message: No LVM data found.' instead of the permissions or missing program error that showed before. If lsblk is not installed, and lvm is installed (or missing), with lvs not root readable, the permissiosn message (or missing program) will show since at that point, inxi has no way to know if there is lvm data or not. * Not an inxi, but rather an Arch Linux packaging bug, the maintainer of lvm has made lvs and vgs fail to return error number on non root start, which is a bug (pvs does return expected error return). Rather than wait for this bug to be fixed, inxi will just test if lvs and lsblk lvm data, it will show permissions message, otherwse the no lvm data message as expected. I think these cover the last unhandled LVM cases I came across, so ideally, the lvm data messages will be reasonably correct. 4. Some man page lintian fixes. 5. Changed usb data parser to use 'unless' instead of 'if' in tests since it's easier to read unless positive tests are true than if negative or negative etc. Enhancements: 1. Since I see too often things like -F --no-host -z which is redundant, the help and man now make it more clear that -z implies --no-host. 2. Even though it's not that pointful, I added in derived Arch Linux system base like Ubuntu/Debian have. It's not that meaningful because unlike Ubuntu/Debian, where you want to know what version the derived distro is based on, Arch is rolling thus no versions, but I figured, why not, it's easy to do, so might as well make the system base feature a bit more complete. Note that the way I did this requires that the distro is ID'ed as its derived distro nanme, not Arch Linux, that will vary depending on how they did their os-release etc, or distro files, but that's not really an inxi issue, that's up to them. From what I've been seeing, it looks like more of the derived distros are being ID'ed in inxi as the derived name, so those should all work fine. Note that seeing 'base:' requires -Sx. 3. More disk vendors!! More disk vendor IDs!!! I really dug into the stuff, and refactored slightly the backend tools I use, so it's now a bit easier to handle the data. Thanks linux-lite hardware database, as always, for having users that really seemt to use every disk variant known to humanity. Changes: 1. In -G, made FAILED: lower case, and also moved it to be after unloaded: It was too easy to think that the loaded driver had failed. Also to make it more explicit, made output like this, in other words, driver: is a container for the possible children: loaded: unloaded: failed: alternate: which should be easier to parse and read without mixing up what belongs to what. driver: loaded: modesetting unloaded: nouvean,vesa alternate: nv driver: loaded: amdgpu unloaded: vesa failed: ati Note that if there is no unloaded: driver, failed: would still appear to come after loaded:, but hopefully it's more clear now. Basically what we found was that the presence of the uppercase FAILED: drew the eye so much that it was sometimes not noted that it was a key: following the driver: item, which itself because it did not list explicitly loaded: was not as clear as it could have been. By making failed: the same as the other key names visually, hopefully it will be less easy to think that the loaded: driver failed: In a sense, this is a legacy issue, because the original use of FAILED: was for non free video drivers, to see when xorg had failed to load them, but over more recent years, the most frequent thing I have been seeing is odd things like failed: ati, when xorg tries to load the legacy ati driver when amdgpu is being used. 2. Likewise, for RAID mdraid and zfs changed FAILED: to Failed:, again, to make it more consistent with the other types. 3. In help menu and man page, removed legacy 'card(s)' in -A, -G, -N, and replaced that with 'device(s)', which is the more accurate term, since the days when these things were only addon cards are long behind us. I had not noticed that, but it caught me eye and I realized it was a very deprecated and obsolete syntax, which did not match the way inxi describes devices today. 4. It was pointed out how incoherent the naming of the item for setting wrap width, --indent-min and config item INDENT_MIN were super confusing, since it was neither indent or minimum, it was in fact wrap maximum, so the new options and config items are --wrap-max and WRAP_MAX. Note that the legacy values will keep working, but it was almost impossible in words to explain this option because the option text was almost the exact opposite of what the option actually does. Redid the man and help explanations to make the function of this option/config item more clear. 5. Made -J/--usb Hub-xx: to fit with other repeating device types in inxi output, before Hub: was not numbered, but it struck me, it should be, like all the other auto-incremented counter line starters, like ID-xx:, Device-x:, and so on. 6. Reorganized the main help menu to hopefully be more logical, now it shows the primary output triggers, then after, the extra data items, -a, -x, -xx, -xxx, separated by white space per type to make it easier to read. This also moved the stuff that had been under the -x items back to where they should be, together with the main output control options. For readability and usability, I think this will help, the help menu is really long, so the more visual cues it has to make it clear what each section is, the better I think. Previously -a was the first items, then way further down was -x, -xx, and -xxx, then under those was -z, -Z, -y.	2021-01-10 19:20:21 -08:00
Harald Hope	df45e6d4ae	Bug Fixes!!! Continuing internal refactor!! ... This bug report came in right after 3.2.00 went out live, but I would never have found it myself in testing so better found than not found! Bugs: 1. A bug was introduced to dmidecode data handlers in 3.2.00 resulted in the dmidecode data array basically eating itself up until errors appear. Quite difficult to trigger, but babydr from Slackware forums figured it out, using -F --dmidecode to force dmidecode use for all features that support it triggered thee bug always. This was a result of the refactor, previously inxi had worked on copies of referenced arrays, but in this case, it was working on the original array of arrays, subtle, but obvious. This method was only used on dmidecode arrays. 2. A second bug was exposed almost by accident, for -M --dmidecode data, there was a missing field and also a missing is set test on that field that led to an error of using undefined value in string comparison. This was strictly speaking 2 bugs, both very old, from 2.9 first rewrite, one failing to set/get the value, and the other failing to test if the value was set before using it. Fixes: 1. There were a few glitches in help menu and man page related to -L option, those are corrected. INTERNAL CODE CHANGES: 1. removed bug inducing splice use in some cases, and added parens to splice to make it fit the new way of with perl builtins, when taking 2 or more arguments, use parens. 2. Found many more instances to add -> dereferencing operator. I have to say, not doing that consistently made the code much harder to read, and created situations where it's somewhat ambiguous what item belongs to what, with everything consistently -> operator run, the code is more clear and obvious, and some of the hacks I'd added because of the lack of clarity were also removed. 3. Removed explicit setting of hash references with null value, that was done out of failure to use -> operators which clearly indicate to Perl and coder what is happening, so those crutches were removed. Also got rid of unnecessary array priming like: my @array = (); Some of these habits came from other languages, but in Perl, declaring my @array means it's an array that is null, and you don't need to do a further (). @array = () is obviously fine for resetting arrays in loops or whatever, but not in the initial declaration.	2020-12-17 14:51:11 -08:00
Harald Hope	5234e3903d	Huge upgrade, major rewrite/refactor, new features, everything is polished!!! ... Note that due to large number of internal changes to code, a separate INTERNAL CODE CHANGES section is at the bottom. Those are changes which in general do not impact what users see that much, but which definitely impact working on and with inxi! They also make errors less likely, and removed many possible bad data error situations. BUGS: 1. Obscure, but very old Tyan Mobo used a form of dmidecode data for RAM that I'd never gotten a dataset for before, this tripped a series of errors in inxi, which were actually caused by small errors and failures to check certain things, as well as simply never assigning data in corner cases. This system used only dmi handles 6 and 7, which is a very rare setup, from the very early days of dmi data being settled, but it was valid data, and actually inxi was supposed to support it, because I'd never gotten a dataset containing such legacy hardware data, the support didn't work. There were actually several bugs discovered while tracking this down, all were corrected. 2. Going along with the cpu fixes below, there was a bug that if stepping was 0, stepping would not show. I had not realized stepping could be 0, so did a true/false test instead of a defined test, which makes 0 in perl always test as false. This is corrected. 3. While going through code, discovered that missing second argument to main::grabber would have made glabel tool (BSD I think mostly) always fail, without exception. That explains why bsd systems were never getting glabel data, heh. 4. Many null get_size tests would not have worked because they were testing for null array but ('','') was actually being returned, which is not a null array. The testing and results for get_size were quite random, now hey are all the same and consistent, and confirmed correct. 5. In unmounted devices, the match sent to @lsblk to get extended device data would never work with dm-xx type names, failed to translate them to their mapped name, which is what is used in lsblk matches, this is corrected. This could lead to failures to match fs of members of luks, raid, etc, particularly noticeable with complex logical device structures. This means the fallback filters against internal logic volume names, various file system type matches, would always fail. 6. A small host of further bugs found and fixed during the major refactor, but not all of them were noted, they were just fixed, sorry, those will be lost to history unless you compare with diffs the two versions, but that's thousands of lines, but there were more bugs fixed than listed above, just can't remember them all. FIXES: 1. There was some ambiguity about when inxi falls back to showing hardware graphics driver instead of xorg gfx driver when it can't find an xorg driver. That can happen for instance because of wayland, or because of obscure xorg drivers not yet supported. Now the message is very clear, it says the gfx software driver is n/a, and that it's showing the hardware gfx driver. 2. Big redo of cpu microarch, finally handled cases where same stepping/model ID has two micorarches listed, now that is shown clearly to users, like AMD Zen family 17, model 18, which can be either Zen or Zen+, so now it shows that ambiguity, and a comment: note: check, like it shows for ram report when it's not sure. Shows for instance: arch: Zen/Zen+ note: check in such cases, in other words, it tells users that the naming convention basically changed during the same hardware/die cycle. 3. There were some raid component errors in the unmounted tests which is supposed to test the raid components and remove them from the mounted list. Note that inxi now also tests better if something is a raid component, or an lvm component, or various other things, so unmounted will be right more often now, though it's still not perfect since there are still more unhandled logical storage components that will show as unmounted when tney are parts of logical volumes. Bit by bit!! 4. Part of a significant android fine tuning and fix series, for -P, android uses different default names for partitions, so none showed, now a subset of standard android partitions, like /System, /firmware, etc, shows. Android will never work well though because google keeps locking down key file read/search permissions in /sys and /proc. 5. More ARM device detections, that got tuned quite a bit and cleaned up, for instance, it was doing case sensitive checks, but found cases where the value is all upper case, so it was missing it. Now it does case sensitive device type searches. 6. One of the oldest glitches in inxi was the failure to take the size of the raid arrays versus the size totals of the raid array components led to Local Storage results that were uselessly wrong, being based on what is now called 'raw' disk totals, that's the raw physical total of all system disks. Now if raid is detected the old total: used:... is expanded to: total: raw:... usable:....used:, the usable being the actual disk space that can be used to store data. Also in the case of LVM systems, a further item is added, lvm-free: to report the unused but available volume group space, that is, space not currently taken by logical volumes. This can provide a useful overview of your system storage, and is much improved over the previous version, which was technically unable to solve that issue because the internal structures did not support it, now they do. LVM data requires sudo/ root unfortunately, so you will see different disk raw totals depending on if it's root or not if there is LVM RAID running. Sample: inxi -D Drives: Local Storage: total: raw: 340.19 GiB usable: 276.38 GiB lvm-free: 84.61 GiB used: 8.49 GiB (3.1%) lvm-free is non assigned volume group size, that is, size not assigned to a logical volume in the volume group, but available in the volume group. raw: is the total of all detected block devices, usable is how much of that can be used in file systems, that is, raid is > 1 devices, but those devices are not available for storage, only the total of the raid volume is. Note that if you are not using LVM, you will never see lvm-free:. 7. An anonymous user sent a dataset that contained a reasonable alternate syntax for sensors output, that made inxi fail to get the sensors data. That was prepending 'T' to temp items, and 'F' to fan items, which made enough sense though I'd never seen it before, so inxi now supports that alternate sensors temp/fan syntax, so that should expand the systems it supports by default out of the box. 8. Finally was able to resolve a long standing issue of loading File::Find, which is only used in --debug 20-22 debugger, from top of inxi to require load in the debugger. I'd tried to fix this before, but failed, the problem is that redhat /fedora have broken apart Perl core modules, and made some of them into external modules, which made inxi fail to start due to missing use of required module that was not really required. Thanks to mrmazda for pointing this out to me, I'd tried to get this working before but failed, but this time I figured out how to recode some of the uses of File::Find so it would work when loaded without the package debugger, hard to figure it, turned out a specific sub routine call in that specific case required the parentheses that had been left off, very subtle. 9. Subtle issue, unlike most of the other device data processors, the USB data parser did not use the remove duplicates tool, which led in some cases to duplicated company names in the output for USB, which looks silly. 10. Somehow devtmpfs was not being detected in all cases to remove that from partitions report, that was added to the file systen filters to make sure it gets caught. 11. Removed LVM image/meta/data data slices from unmounted report, those are LVM items, but they are internal LVM volumes, not available or usable. I believe there are other data/meta type variants for different LVM features but I have added as many types as I could find.. Also explictly now remove any _member type item, which is always part of some other logical structure, like RAID or LVM, those were not explicitly handled before. 12. Corrected the varous terms ZFS can use for spare drives, and due to how those describe slightly different situations than simply spare, changed the spare section header to Available, which is more accureate for ZFS. ENHANCEMENTS: 1. Going along with FIX 2 is updating and adding to intel, elbrus microarch family/ model/stepping IDs (E8C2), so that is fairly up to date now. 2. Added in a very crude and highly unreliable default fallback for intel: /sys/devices/cpu/caps/pmu_name which will show the basic internal name used which can be quite different from what the actual microarch name is, but the hope is that for new intel cpus that come out after these last inxi updates, something may show, instead of nothing. Note these names are often much more generic, like using skylake for many different microarches. 3. More android enhancements, for androids that allow reading of /system/build.prop, which is a very useful informative system info file, more android data will show, like the device name and variant, and a few other specialized items. You can see if your android device lets inxi read build.prop if you see under -S Distro: Android 7.1 (2016-07-23) or just Android. If it shows just android, that means it can't read that file. Showing Android however is also new, since while inxi can't always read build.prop if that file is there, it's android, so inxi finally can recognize it's in android, even though it can't give much info if it's locked down. Inxi in fact did not previously know it was running in android, which is quite different from ARM systems in some ways, but now it does. If the data is available, it will be used in Distro: and in Machine: data to add more information about the android version and device. 4. A big one, for -p/-P/-o/-j now shows with -x the mapped device name, not just the /dev/dm-xx ID, which makes connecting the various new bits easier, for RAID, Logical reports. Note that /dev/mapper/ is removed from the mapped name since that's redundant and verbose and makes the output harder to read. For mapped devices, the new --logical / -L report lets you drill into the devices to find out what dm-xx is actually based on, though that is a limited feature which only supports drilling to a depth of 2 components/devices, there can be more, particularly for bcache, luks setups, but it's just too hard to code that level of depth, so something is better than nothing in this case, which is the actual choice I was faced, the perfect in this case really is/was the enemy of the good, as they say. 5. More big ones, for -a -p/-P/-o/-j shows kernel device major:minor number, which again lets you trace each device around the system and report. 6. Added mdadm if root for mdraid report, that let me add a few other details for mdraid not previously available. This added item 'state;' to the mdraid report with right -x options. 7. Added vpu component type to ARM gfx device type detection, don't know how video processing vcu had escaped my notice. 8. Added fio[a-z] block device, I'd never heard of that before, but saw use of it in dataset, so learned it's real, but was never handled as a valid block device type before, like sda, hda, vda, nvme, mmcblk, etc. fio works the same, it's fio + [a-z] + [0-9]+ partition number. 9. Expanded to alternate syntax Elbrus cpu L1, L2, L3 reporting. Note that in their nomenclature, L0 and L1 are actually both L1, so add those together when detected. 10. RAM, thanks to a Mint user, antikythera, learned, and handled something new, module 'speed:' vs module 'configured clock speed:'. To quote from supermicro: <<< Question: Under dmidecode, my 'Configured Clock Speed' is lower than my 'Speed'. What does each term mean and why are they not the same? Answer: Under dmidecode, Speed is the expected speed of the memory (what is advertised on the memory spec sheet) and Configured Clock Speed is what the actual speed is now. The cause could be many things but the main possibilities are mismatching memory and using a CPU that doesn't support your expected memory clock speed. Please use only one type of memory and make sure that your CPU supports your memory. >>> 11. Since RAM was gettng a look, also changed cases where ddr ram speed is reported in MHz, now it will show the speeds as: [speed * 2] MT/S ([speed] MHz). This will let users make apples to apples speed comparisons between different systems. Since MT/S is largely standard now, there's no need to translate that to MHz. 12. And, even more!! When RAM speeds are logically absurd, adds in note: check This is from a real user's data by the way, as you can see, it triggers all the new RAM per Device report features. Sample: Memory: RAM: total: 31.38 GiB used: 20.65 GiB (65.8%) Array-1: capacity: N/A slots: 4 note: check EC: N/A Device-1: DIMM_A1 size: 8 GiB speed: 1600 MT/s (800 MHz) Device-2: DIMM_A2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz) actual: 61910 MT/s (30955 MHz) note: check Device-3: DIMM_B1 size: 8 GiB speed: 1600 MT/s (800 MHz) Device-4: DIMM_B2 size: 8 GiB speed: spec: 1600 MT/s (800 MHz) actual: 2 MT/s (1 MHz) note: check 13. More disks vendor!!! More disk vendor IDs!!! Yes, that's right, eternity exists, here, now, and manifests every day!! Thanks to linux-lite hardware database for this eternally generating list. Never underestimate the creativity of mankind to make more disk drive companies, and to release new model IDs for existing companies. Yes, I feel that this is a metaphore for something much larger, but what that is, I'm not entirely clear about. CHANGES: 1. Recent kernel changes have added a lot more sensor data in /sys, although this varies system to system, but now, if your system supports it, you can get at least partial hdd temp reports without needing hddtemp or root. Early results suggest that nvme may have better support than spinning disks, but it really varies. inxi will now look for the /sys based temp first, then fall back to the much slower and root / sudo only hddtemp. You can force hddtemp always with --hddtemp option, which has a corresponding configuration item. 2. The long requested and awaited yet arcane and obscure feature -L/--logical, which tries to give a reasonably good report on LVM, LUKS, VeraCrypt, as well as handling LVM raid, both regular and thin, is now working, more or less. This took a lot of testing and will probably not be reasonably complete for a while, mainly because the levels of abstraction possible between lvm, lvm raid, mdraid, LUKS, bcache, and other caching and other encryption options are just too deep to allow for easy handling, or easy outputs. But a very solid and good start in my view, going from nothing to something is always a big improvement!! LVM reports require root/sudo. This will, finally, close issue #135. 3. Going along with -L, and serving as a model for the logic of -L, was the complete refactor of -R, RAID, which was a real mess internally, definitely one of the messiest and hardest to work with features of inxi before the refactor. It's now completely cleaned up and modularized, and is easy to add raid types, which was not possible before, now it cleanly supports zfs, mdraid, and lvm raid, with in depth reports and added items like mdraid size, raid component device sizes and maj:min numbers if the -a option is used. Note that LVM RAID requires root/sudo. 4. Added some more sensors dimm, volts items, slight expansion. Note that the possible expansion of sensors made possible by the recently upgraded sensors output logic, as well as the new inxi internal sensors data structure, which is far more granular than the previous version, and allows for much more fine grained control and output, though only gpu data currently takes advantage of this new power under the covers, although as noted, the /sys based hdd temps use the same source, only straight from /sys, since it was actually easier using the data directly from sys than trying to map the drive locations to specific drives in sensors output. Well, to be accurate, since now only board type sensors are used for the temp/fan speed, voltage, etc, reports, the removal of entire sensor groups means less chance of wrong results. 5. To bring the ancient RAID logic to fit the rest of inxi style, made zfs, mdraid, and lvm raid components use incrementing numbers, like cpu cores does. This got rid of the kind of ugly hacks used previously which were not the same for zfs or mdraid, but now they are all the same, except that the numbers for mdraid are the actual device numbers that mdraid supplies, and the LVM and ZFS numbers are just autoincremented, starting at 1. 6. Changed message <root/superuser required> to <superuser required> because it's shorter and communicates the same thing. INTERNAL CODE CHANGES: 1. Small, transparent test, tested on Perl 5.032 for Perl 7 compatibility. All tests passed, no legacy code issues in inxi as of now. 2. Although most users won't notice, a big chunk of inxi was refactored internally, which is why the new -L, the revamped -R, and the fixed disk totals finally all can work now. This may hopefully result in more consistent output and fewer oddities and randomnesses, since more of the methods all use the same tools now under the covers. Ths refactor also significantly improved inxi's execution speed, by about 4-5%, but most of those gains are not visible due to the added new features, but the end result is new inxi runs roughly the same speed as pre 3.2.00 inxi, but does more, and does it better, internally at least. If you have a very good eye you may also note a few places where this manifests externally as well. Last I checked about 10-12% of the lines of inxi had been changed, but I think that number is higher now. Everything that could be optimized was, everything could be made more efficient was. 3. Several core tools in inxi were expanded to work much more cleanly, like reader(), which now supports returning just the index value you want, that always happened on the caller end before, which led to extra code. get_size likewise was expanded to do a string return, which let me remove a lot of internal redundant code in creating the size unit output, like 32 MiB. uniq() was also redone to work exclusively by reference. 4. Many bad reference and dereference practices that had slipped into inxi from the start are mostly corrected now, array assignments use push now, rather than assign to array, then add array to another array, and assign those to the master array. Several unnecessary and cpu/ram intensive copying steps, that is, were removed in many locations internally in inxi. Also now inxi uses more direct anonymous array and hash refernce assignments, which again removes redundant array/hash creation, copy, and assignment. 5. Also added explicit -> dereferencing arrows to make the code more clear and readable, and to make it easier for perl to know what is happening. The lack of consistency actually created confusion, I was not aware of what certain code was doing, and didn't realize it was doing the same thing as other code because of using different methods and syntaxes for referencing array/hash components. I probably missed some, but I got many of them, most probably. 6. Instituted a new perl builtin sub routine rule which is: if the sub takes 2 or more arguments, always put in parentheses, it makes the code much easier to follow because you see the closing ), like: push(@rows,@row); Most perl builtins that take only one arg do not use parentheses, except length, which just looks weird when used in math tests, that is: length($var) > 13 looks better than length $var > 13. This resolved inconsistent uses that had grown over time, so now all the main builtins follow these rules consistently internally. Due to certain style elements, and the time required to carefully go through all these rules, grep and map do not yet consistently use these rules, that's because the tendency has been to use the grep {..test..} @array and map {...actions...} @array 7. Mainly to deal with android failures to read standard system files due to google locking it down, moved most file queries to use -r, is readable, rather than -e, exists, or -f, is file, unless it only needs to know if it exists, of course. This fixed many null data errors in android even on locked androids. 8. Added in %mapper and %dmmapper hashes to allow for easy mapping and unmapping of mapped block devices. Got rid of other ways of doing that, and made it consistent throughout inxi. These are globals that load once. 9. Learned that perl builtin split() has a very strange and in my view originally terrible decision that involves treating as regex rules string characters in split string, like split('^^',$string), which should logically be a string value, not a ^ start search followed by a ^, but that's how it is, so that was carefully checked and made consistent as well. Also expanded split to take advantage of the number of splits to do, which I had only used occasionally before, but only updated field/value splits where I have a good idea of what the data is. This is very useful when the data is in the form of field: value, but value can contain : as well. You have to be very careful however, since some data we do want in fact the 2nd split, but not the subsequent ones, so I only updated the ones I was very sure about. 10. Going along with the cpu microarch fixes, updated and cleaned up all the lists of model/stepping matches, now they are all in order and much easier to scan and find, that had gotten sloppy over the years. 11. More ARM, moved dummy and codec device values into their own storage arrays, that let me remove the filters against those in the other detections. Makes logic easier to read and maintain as well.	2020-12-15 15:13:14 -08:00
Harald Hope	f30d907c4c	man page fix	2020-11-11 15:45:10 -08:00
Harald Hope	285c6f715f	Bug fixes, new features!! Update now!! Or don't, it's up to you. ... Bugs: 1. Let's call some of the android fixes and debugger failures bugs, why not? Those are fixed. Note that many of these fixes will impact any system that is ARM based, not just android. Fixes: 1. Related to issue #226 which was a fine issue, fine tuned the debugger debuggers to allow for smoother handling of /sys parse failures. Also added debugger filters for common items that would make the /sys parser hang, oddly, most seem to be in /sys/power for android devices. 2. Added some finetunings for possible mmcblk storage paths, in some cases, an extra /block is added, which made inxi think mounted drives were unmounted. I've never seen this extra /block except on mmcblk devices on android, but you never know, it could be more widespread. 3. Also mainly related to android, but maybe other ARM devices, in some cases, an errant 'timer' device was appearing as a cpu variant, which is wrong. That was a corner case for sure, and part of the variant logic in fact uses timer values to assign the actual cpu variants, but it was wrong in this case because it was ....-timer-mem, not ...-timer, which led to non-existent CPU variants showing. 4. Issue #236 by ChrisCheney pointed out that inxi had never updated its default /proc/meminfo value to use the newer MemAvailable as default if present, which led to incorrect memory used values showing up. That's because back in the old days, we had to construct a synthetic Memory used from MemFree, buffers, cache, etc, but that wasn't always right, since sometimes the cache actually isn't available, often is, but not always. 34e431b0ae This commit on the kernel explains it pretty clearly. Thanks Chris for bringing this to our attention. 5. Kind of more future-proofing, got rid of a bunchy of hard-coded strings internally and switched those to use the row_defaults values, which is where string messages are supposed to go. That was mostly in the initial program check messages on start-up, but also a few other stray ones. Also consolidated them a bit to get rid of redundant messages, and added more variable based messages, like for missing/permissions on programs etc. The idea in general is that all the strings are contained in subs so that in theory they could be swapped for other strings, eg, languages, but honestly, I no longer see this as very likely to ever happen. But it's still nice to be consistent internally and not get sloppy with english strings. This also got rid of some largely redundant items in row_defaults, and expanded the list of handled events, and of variable based events, so it shouldn't be as necessary to add new row_defaults items for similar events. Enhancements: 1. Debugger item to maybe try to find distro OEM, this was connected with issue #231 but the issue poster vanished, and didn't do the work required, so this one won't happen until someone who cares [not me, that is] does the required work. It's always funny to see how quickly people vanish when they have to do the actual boring research that they want me to do for them, lol. Or maybe, sigh is more appropriate than lol. But it is pretty much par for the course, sad to say. Or maybe this was an OEM hoping to have someone do their corporate work for them for free, who knows. Anyway, there's a certain category of items that I'm reasonably happy to implement, but NOT if I have to do all the boring research work, so such features being added will depend on the poster actually doing the boring work. I've gotten burned on this a few times, cpu arch: for example, some guy said he'd track that and provide updates, he never even made it to the first release, so I got stuck doing that one forever after. But that one at least has some general value, so that's ok more or less, but I definitely won't take on stuff that I really don't personally care at all about unless the person requesting the feature does all the work beforehand. The boring part, that is.... 2. Related to issue #226, much improved android ID and many small android fixes for machine data etc. Now uses /system/build.prop for some data, which is a nice source, sadly, most modern android devices seem to be locked down, with both build.prop and /sys locked down, which makes inxi unable to actually get any of that data, but if your device either does not have these root only readable, or if you have an android rooted phone, the android support will be more informative. Hint: if you run inxi in termux on your non rooted android device, and it shows you what android version you are using in System:... Distro: line, then your android is not locked down. I have one such phone, android 7.1, but I cannot say how usual or non usual this is. The poster of issue #226 for instance had to root his android 7 phone to get this data to display. So it seems to vary quite a bit. Note that due to these file system lockdowns, in general, trying to do android arm support remains largely a waste of time, but on some devices sometimes, you can now get quite nice system info. As I noted in the issue, if I can't get the features to work on a non rooted phone in my possession, I'm probably not going to try to do the work because it's too hard to try to work on android issues without having the device in front of you for testing and debugging. In this case, one of my phones did work, so I did the work just to see where android is at now. Android showed some slightly odd syntaxes for some devices, but those are now handled where I got a dataset for them that revealed the changes required. 3. Also related to issue #226 for termux in android, will show -r info. That's an apt based package manager, but termux puts the apt files somewhere else so needed to change paths if those alternate paths existed for apt. 4. Added PARTFLAGS to debugger to see what knd of data that will yield, that's a lsblk key/value pair. 5. Just because it's easy to do, added new -Ixxx item, wakeups: which is a subset of Uptime, this will show how many times the system has been woken from suspend since the last boot. If the system has never been suspended, shows 0. 6. Many more disk vendors and disk IDs. The list just never ends, possibly a metaphor for something, the endless spinning of maya, who knows? 7. Added newest known ubuntu release, hirsute, to buntu ID logic. Might as well catch them early, that will be 21.04.	2020-11-11 15:35:08 -08:00
Harald Hope	e45c696010	Bug fixes, updates!!! Yes!! Why wait!!! Can't stay frozen forever! ... Bugs: 1. Not an inxi bug, but a weird change in defaults for ubuntu GNOME ENV variable values when running at least the gnome desktop, result to end users appears to be a bug. This resolves issue #228 Note that so much weird non desktop data was put into those environmental variables that inxi simply could make no sense of it. The fix was to make the detections more robust, using regex instead of string compare, as well as to at least try to strip out such corrupted data values, though that can never be fully predictable. As far as I know, this issue only hits ubuntu gnome desktops, I've never seen these value corruptions on any other distro, or on any other ubuntu desktop, though they may be there, but I'm not going to test all the ubuntu spins to find out. I'm hoping the combination of logic fixes and junk data cleaning will handle most future instances of these types of corruptions automatically. Again, this only happens on relatively laste ubuntu gnomes as far as I know. Fixes: 1. An oversight, added sshd to list of whitelisted start clients. This permits expected output for: ssh <name@server> inxi -bay that is, running inxi as an ssh command string. Should have done that a while ago, but better late than never. This corrects issue #227, or at least, has a better default, it worked fine before, but required using --tty to reset to default terminal behavior. The problem is that if inxi can't determine what it's running in, it defaults to thinking it's in an IRC client, and switches to IRC color codes, among other changes. But it was nice to get sshd covered automatically so users don't have to know the --tty option. Changes: 1. More disk vendors and vendor IDs!!! Yes, that's right, the list never ends!!	2020-10-16 13:54:25 -07:00
Harald Hope	ef428e75e1	Bug fixes, feature updates, changes!! ... Bugs: 1. There was a glitch in the pattern that made -D samsung / seagate not ID right, fixed. 2. I do not like calling this a bug, because it's not an inxi bug, it's an upstream regression in the syntax used in /proc/version, they changed a fully predictable gcc version .... to a random series of embedded/nested parentheses and other random junk. inxi tries to deal with this regression, which will be perceived as a bug in systems running kernel 5.8 or newer and inxi 3.1.06 or older, since it will fail to show the kernel build compiler version since it can't find it in the string. I really dislike these types of regressions caused by bad ideas done badly and without any thought to the transmitted knowledge base, but that's how it goes, no discipline, I miss the graybeards, who cared about things like this. Fixes: 1. more -D nvme id changes, intel in this case. 2. FreeBSD lsusb changed syntax, which triggered a series of errors when run. Since I never really got the required data [hint bsd users, do NOT file issues that you want fixed and then not provide all the data required, otherwise, really, why did you file the issue? did you expect magic pixies to fly in with the required data?] See the README.txt for what to do to get issues really handed in BSDs. tldr; version: if you won't spend the time providing data and access required, I won't spend the time on the issue, period, since if you don't care enough to do those simple steps, why on earth do you expect me to? Changes: 1. -C 'boost' option changed from -xxx feature to -x feature. Consider it a promotion! 2. Added --dbg 19 switch to enable smart data debugging for -Da. 3. Some new tools to handle impossible data values for some -D situations for SMART where the smart report contains gibberish values, that was issue #225 -- tools were convert_hex and is_Hex. The utility for these is limited, but might be of use in some cases, like handling the above gibberish data value.	2020-09-29 16:22:15 -07:00
Harald Hope	ddbd8e8679	fixed seagate/samsung glitch	2020-08-17 15:23:55 -07:00
Harald Hope	b1650ea2a8	New features, new changes, new bug fixes!!! Excitement!!! Thrills!!! ... Bugs: 1. Forgot to set get Shell logic in inxi short form, oops, so Shell remained blank, only inxi short, which I rarely use so I didn't notice. 2. Failed to test pacman-g2 for packages, had wrong query argument, so it failed. Also failed to test for null data, so showed errors for packages as well. Both fixed. 3. A big bug, subtle, and also at the same time, an enhancement, it turns out NVME drives do NOT follow the age old /proc/partitions logic where if the minor number is divisible by 16 or has remainder 8 when divided by 16, it's a primary drive, not a partition. nvme drives use a random numbering when > 1 nvme drives are present, and the old tests would fail for all nvme drivers more than the first one, which led to wrong disk size totals. Thanks gardotd426 who took the time to help figure this out in issue #223 - fix is to not do that test for nvme drives, or rather, to add a last fail test for nvme primary nvme[0-9]n[0-9] drive detections, not the minor number. Fixes: 1. Corrected indentation for block sizes, children were not indented. 2. Updated some older inxi-perl/docs pages, why not, once in a while? 3. Kernel 5.8 introduces a changed syntax to gcc string location, this has been corrected, and the kernel gcc version now shows correctly for the previous syntax and the new one. Hopefully they do not change it again, sigh... 4. Removed string 'hwmon' sensors from gpu, those are not gpu sensors, and are also usually not board/cpu sensors, but things like ath10, iwl, etc, network, or disk sensors, etc. In some cases hwmon sensor data would appear Enhancements: 1. Big sensors refactor, now inxi supports two new sensors options: --sensors-exclude - which allows you to exclude any primary sensor type[s]. Note that in the refactored logic, and in the old logic, gpu sensors were already excluded. Now other hardware specific sensors like network are excluded as well. --sensors-use - use ONLY list of supplied sensor IDs, which have to match the syntax you see in lm-sensors sensors output. Both accept comma separated list of sensors, 1 or more, no spaces. The refactor however is more far reaching, now inxi stores and structures data not as a long line of sensors and data without differentiation, but by sensor array/chip ID, which is how the exclude and use features can work, and how granular default hardware sensor exclusions and uses can happen. This is now working in the gpu sensors, and will in the future be extended to the newer 5.7/5.8 kernel disk temperature sensors values, which will lead in some cases to being able to get sensors data for disks without root or hddtemp. This is a complicated bit of logic, and I don't have time to do it right now, but the data is now there and stored and possible to use in the future. To see sensors structures, use: inxi -s --dbg 18 and that will show the sensors data and its structures, which makes debugger a lot easier for new features. This issue was originally generated by what was in my view an invalid complaint about some inxi sensors defaults, which led me to look more closely at sensors logic, which is severely lacking. More work on sensors will happen in the future, time, health, and energy permitting. 2. Added Watts, mem temp, for amdgpu sensors, as -sxxx option. More gpu sensor data will be added as new data samples show what will be available for the free modules like amdgpu, nouvean, and the intel graphics modules. 3. More disk vendors and IDs, as noted, the list never ends, and it hasn't ended, so statement remains true. Thanks linux-lite hardware database. Changes: 1. This has always bugged me since it was introduced, the primary cpu line starter Topology: which was only technically accurate for its direct value, not its children, and also, in -b, cpu short form was using the value as the key, which is a no-no, I'd been meaning to fix that too, but finally realized if I just make the primary CPU line key be 'Info:', which is short, yet non-ambiguous, it would solve both problems. To keep the -b cpu line as short as before, I removed the 'type:' and integraged that value into the primary Info: string: CPU: Info: 6-Core AMD Ryzen 5 2600 [MT MCP] speed: 2750 MHz min/max: 1550/3400 MHz -b 3.1.05 and earlier: CPU: 6-Core: AMD Ryzen 5 2600 type: MT MCP speed: 1515 MHz min/max: 1550/3400 MHz These resolve something that has irked me for quite a while, 'Topology:' didn't fit, it was too geeky, and worst, it only applied to the value directly following it, NOT to the rest of the CPU information. It also could not be shortened or abbreviated since then it would have made no actual sense, like topo:, and the same issue with value being used for key in -b, and wrong word for line starter in -C would have existed. Besides, someone might think I was trying to make a subtle reference to the great Jodorowsky film 'El Topo', which would be silly, because that's art, and this is just some system specs that are reasonably readable... 2. Was using opendns for WAN dig IP address, but apparently cysco bought that company, and now I've noticed the old opendns dig queries were failing more and more, so replaced that with akamai dig requests. Also made the WAN IP fallback to HTTP IP method if dig failed. New option: --no-http-wan and config item NO_HTTP_WAN with override --http-wan added to let you switch off http wan IP requests if you want. Note that if dig fails, you will get no wan ip address. Updated/improved error messages to handle this more complex set of wan ip options, so hopefully the error alert message will in most cases be right. 3. To future proof inxi, switched debugger upload location to ftp.smxi.org/incoming from the old techpatterns.com/incoming. Updated man/help to remove those urls too.	2020-08-16 15:27:11 -07:00
Harald Hope	3224a39f80	man page typo fix	2020-07-26 20:36:27 -07:00
Harald Hope	bbcaed9475	Bug fixes!!! New Features!! Why wait!!! ... Bugs: 1. Issue #220 on github: inxi misidentified XFCE as Gnome. This was a kind of core issue, and pointed to some logic that needed updating, and some inadequate assumptions made, and some too loose cascade of tests. Hopefully now xfce will almost never get misidentified, and the other primary desktops ID'ed either from $ENV or from xrop -root will be slightly more accurately identified as well. Note that this fix creates a possibility for obscure misconfigured desktops to be ID'ed wrong, but in this case, that will be technically a bug for them, but with the new fixes, that situation will be cleaner to handle internally in the desktop ID logic. Also tightened the final Gnome fallback detection to not trigger a possible false positive, it was testing for ^_GNOME but that is not adequate, because some gnome programs will trigger these values in xprop -root even if GNOME is not running. Should be safer now, hopefully no new bugs will be triggered by these changes. Fixes: 1. Missed an indentation level for -y1, gcc alt should have been indented in one more level, now it is. 2. In disk vendors/family, didn't clean items starting with '/', this is now corrected. Yes, some do, don't ask me why. Might be cases like: Crucial/Micron maybe, where the first ID is grabbed, not sure. Enhancements: 1. New Disk vendors, vendor IDs!!! The list never ends!!! We've finally found infinity, and it is the unceasing wave of tiny and not so tiny disks and their Ids. 2. New feature: for -Aa, -Na/-na/-ia, -Ga, now will add the modules the kernel could support if they were available on the Device-x lines of those items. This was made an -a option because it really makes no sense, if it's a regular option, users might think that for example an nvidia card had a nouveua driver when it didn't, when in fact, all the kernel is saying is that it knows those listed modules 'couid' be used or present. This corresponds to the Display: item in -Ga, that lists 'alternate:' drivers that Xorg knows about that could likewise be used, if they were on the system. In other words these are --admin options because otherwise users might get confused, so this is one where you want to know the man explanation before you ask for it. It is useful however if you're not sure what your choices are for kernel modules. When the alternate driver is the same as the active driver, or if none is found, it does not show the alternate: item to avoid spamming.	2020-07-26 19:22:59 -07:00
Harald Hope	0645c3a7a6	New version, new man, huge update, bug fixes, cleanups, updates!! ... What started as a relatively minor issue report ended up with a refactor of big chunks of some of the oldest code and logic in inxi. So many bugs and fixes, updates, and enhancements, that I will probably miss some when I try to list them. Bugs: 1. In the process of fixing an issue about sudo use triggering server admin emails on failure, when --sudo/--no-sudo and their respective configuration items were added, sudo was inadvertently disabled because the test ran before the options were processed, which meant the condition to set sudo data was always false, so sudo for internal use was never set. The solution was to set a flag in the option handler and set sudo after options or configs run. 2. Issue #219 reported gentoo and one other repo type would fail to show enabled repos, and would show an error as well, this was due to forgetting to make the match test case insensitive. If only all bugs were this easy to fix!! 3. I'd seen this bug before, and couldn't figure out why it existed. It turned out that the partition blacklist filters were running fine in the main partition data tool, but I had forgotten to add in corresponding lsblk partition data filters, lol, so when the logic went back and double checked for missing partitions [this feature had been if i remember right to be able to show hidden partitions, which the standard method didn't see, but lsblk did, anyway, when the double check and add missing partitions logic ran, inxi was putting back in the blacklisted partitions every time, despite the original blacklists working well and as intended. This was fixed by adding in all the required fs type blacklists, then adding in comments above each black list reminding coders that if they add or remove from one blacklist, they have to do the same on the other. 4. Found while testing something unrelated on older vm, the fallback case for cpu bugs, which was supposed to show the basic /proc/cpuinfo cpu bugs, was failing inexplicably because the data was simply being put into the wrong variable name, sigh. Fixes: 1. While not technically an inxi bug, it would certainly appear that way to anyone who triggered it. We'd gotten issue reports before on this, but they were never complete, so couldn't figure it out. Basically, if someone puts inxi into a simple script that is $PATH [this was the missing fact needed to actually trigger this bug in order to fix it], the script [not inxi], will then enter into an endless loop as inxi queries it for its version number using <script name> --version. This issue didn't happen if the script calling inxi was not in PATH, which is why I'd never been able to figure it out before. Only simple scripts with no argument handlers could trigger this scenario, and only if they were in PATH. Fixing this required refactoring the entire start get_shell_data logic, which ended up with a full refactor of the program_version logic as well. The fix was to expand the list of shells known by inxi so it would be able to recognize when it was in a shell running a script running inxi. This resulted in several real improvements, for instance, inxi will now almost always be able to determine the actual shell running inxi, even when started by something else. It will also never use --version attempts on programs it does not know about in a whitelist. So we lose slightly the abilty to get version data on unknown shells, but we gain inxi never being able to trigger such an infinite loop situation. 2. As part of the program_version refactor, a long standing failure to get ksh, lksh, loksh, pdksh, and the related posh shells, all of which ID their version numbers only if they are running the command in themselves. The mistake had been having the default shell run that command. These all now correctly identify themselves. 3. As part of the wm upgrades, many small failures to ID version numbers, or even wm's, in some cases, were discovered when testing, and corrected. Some I had not tested, like qtile, and the lisp variants, were not being detected correctly by the tests due to the way python or lisp items are listed in ps aux. 4. As part of the wm update and program_version refactor, updated and simplified many desktop and wm detections and logic blocks. Ideally this makes them more preditable and easy to work on for the future. 5. As some last tunings for the new -y1 key: value pair per line output option, fixed some small glitches in -b indentation. Also improved RAID indenting, and Weather, and made it all very clean and predictable in terms of indentations. 6. Something I'd slightly noticed but never done anything about, while testing desktop fixes, I realized that for Desktop: item, dm: is a secondary data type, but if it's Console:, then DM: is a primary data type, not a secondary one. So now if Console: it becomes DM: whic makes sense, previously it implied a dm: was used to start the console, which was silly. Also, since often the reason it's Console: with no dm in the first place is that it's a server with no dm. So now if console, and no dm detected, rather than showing DM: N/A it just doesn't show dm at all. 7. As part of the overall core refactor, the print_data logic was also refactored and simplified, by making -y1 a first class citizen, it led to significantly different way of being able to present inxi data on your screen, and now print_data logic is cleaner and reflects these changes more natively, all the initial hacks to get this working were removed, and the logic was made to be core, not tacked on. 8. A small thing also revealed in issue #219, battery data was not being trimmed, not sure how I missed that, but in some cases, space padding was in the values and was not removed, which leads to silly looking inxi output. 9. Several massive internal optimizations, which were tested heavily, led to in one case, 8-900x faster execution the second time a data structure is used, previously in program_values the entire list was loaded each time program_values was called, now it's loaded into a variable on first load and the variable is used for the tests after that. This was also done for the vendor_version for disk vendors, which also features a very long data structure which can be loaded > 1 times for instances where a system has > 1 disk. I also tested while I was at it, to see if loading these tyeps of data structures, arrays of arrays, or hashes of arrays, by reference, or by dereferencing their arrays, was faster, and it proved that it's about 20% faster to not dereference them, but to use them directly. So I've switched a number of the fixed data structures internally do use that method. Another tiny optimization was hard resetting the print_data iterator hash, while this would never matter in the real world, it showed that resetting the iterator hash manually was slightly more efficient than resetting it with a for loop. 10. While not seen inside inxi, I updated and improved a number of the vm's used to test inxi and various software detections, so now I have a good selection, going back to 2008 or so, up to current. This is helpful because things like shells and window managers and desktops come and go, so it is hard to test old detections on new stuff when you can't install those anymore. You'll see these fixes in many of the less well known window managers, and in a few of the better known ones, where in some cases the detections were damaged. 11. As part of the program_version refactor, updated and fixed file based version detections, those, ideally, will almost never be used. Hopefully programmers of things like window managers, shells, and desktops, can learn how to handle --version requests, even though I realize that's a lot harder than copying someone's code and then rebranding as your own project, or whatever excuse people have for not including a --version item in their softaware. Enhancements: 1. As a result of the shell, start shell, shell parent refactors, inxi was able to correctly in most cases deetermine also the user default shell and its verison, so that was added as an -Ixxx option: Shell: ksh v: A_2020.0.0 default: Bash v: 5.0.16 2. As part of the program_version refactor, a more robust version number cleaner was made, which now allows for much more manipulation of the version number string, which sometimes contains, without spaces, non version number ' info right before the actual version. 3. Many more wm IDs were created and tested, and some old virtual machines that were used years ago were used again to test old window managers and their IDs, as well as new vms created to test newer ones. Many version IDs and WM ids were fixed in this process as well. All kinds of new ones added, though the list is basiclaly endless so ideally inxi would only use its internal data tables for window managers that have actual users, or did. 4. First wayland datatype, now it may show Display ID: with -Ga, so far that's the only wayland screen/display data I can get reliably. 5. As part of the shell parent/started in: updates and fixes, added every shell I could find, and installed and tested as many of them as possible to verify that either they have no version method, or that their version method works. This shell logic also is used to determine start parent. Obviously using whitelists of things that can change over time isn't ideal, but there was no way to actually do it otherwise. The best part of the fixes is that it's now remarkably difficult to trick inxi into reporting the wrong shell, and it generally will also get the default shell right, though I found cases in testing where a shell when started replaces the value in $SHELL with itself. 6. I found a much faster and reasonably reliable way to determine toolkits used by gtk desktops, like cinnamon, gnome, and a few others. Test is to get version from gtk-launcher, which is MUCH faster than doing a package version query on the random libgtk toolkit that might be tested, and actually was tested for pacman, apt, and rpm in the old days, but that was removed because it was a silly hack. It's possible that now and then gtk desktops will be 0.0.1 versions off, but in most cases, the version matched, so I decided to restore the tk: item for a selection of gtk or gnome based desktops. So now gtk desktops, except mate, which of course will be using gtk 2 for a while longer, toolkit version should be working again, and the new method works on everything, unlike the old nasty hack that was used, which required package queries and guessing at which gtk lib was actually running the desktop, it was such a slow nasty hack that it was dumped a while ago, but this new method works reliably in most cases and solves most of the issues. 7. As part of the overall program_versions refactor, the package version tester tool was extended to support pacman, dpkg, and rpm, which in practical terms covers most gnu/linux users and systems. Since this feature is literally only used for ASH and DASH shell version detections, it was really just added as a proof of concept, and because it fit in well with the new Package counts feature of -I/-r. 8. Updated for version info a few other programs, added compositors as well. 9. Last but not least!! More disk vendor IDs, more disk vendors!! And found another source to double check vendor IDs, that's good. New Features: 1. For -Ix/-rx, -Ixx/-rxx, -Ia/-ra, now inxi shows package counts for most package managers plus snap, flatpak, and appimage. I didn't test appimage so I'm not 100% sure that works, but the others are all tested and work. If -r, Packages shows in the Repos item as first row, which makes sense, packages, repos, fits. Note that in some systems getting full package counts takes some time so it's an -x option not default. If -rx, -rxx, -ra, package info moved to -r section, and if -Ix, -Ixx, or -Ia, the following data shows: * -Ix or -rx: show total package counts: Packages: 2429 * -Ixx or -rxx: shows Packages then counts by package manager located. If there was only one package manager with packages, the total moves from right after Packages: to the package manager, like: Packages: apt: 3241 but if there were for example 2 or more found, it would show the total then: Packages 3245 apt:3241 snap: 4 * -Ia or -ra: adds package managers with 0 packages managed, those are not show with -xx, and also shows how many of those packages per package manager is a library type lib file. Sample: inxi -Iay1 Info: Processes: 470 Uptime: 8d 10h 42m Memory: 31.38 GiB used: 14.43 GiB (46.0%) Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 5/6/7/8/9 Packages: apt: 3685 lib: 2098 rpm: 0 Shell: Elvish v: 0.13.1+ds1-1 default: Bash v: 5.0.16 running in: kate pinxi: 3.1.04-1	2020-06-28 22:22:12 -07:00
Harald Hope	46ae081ec6	Big change, cleanup, small bug fixes. Hot, grab it now!! ... The new -y 1 feature exposed several small and larger glitches with how sets of data were constructed in inxi output. See Changes: for list of changes made to improve or fix these glitches. These errors and minor output inconsistencies became very obvious when I was doing heavy testing of -y 1, so I decided to just fix all of them at the same time, plus it was very hard to make the -y 1 indenter work as expected when the key values were not being treated consistently. Note that this completes the set of all possible -y results: Full -y Options: 1. -y [no integer given] :: set width to a default of 80. this is what you usually want for forum posts, or for online issue reports, because it won't wrap and be hard to read. Help us help your users and others!! Teach them to use for example -Fxzy or -bay for their bug reports. Just add y to whatever collection of arguments you generally ask for in support forums or issue reports. Highly recommended, easy to type, and joins cleanly with other letters. 2. -y -1 :: removes line width limits, this can lead to very long lines in some cases, and removes all auto-wrapping of line widths. 3. -y 1 :: Switch to stacked key: value pairs, with primary data blocks separated by a blank line. Think dmidecode type output, or other command line sys info tools. By request, a forum support guy noted it was hard for newbies to understand the -G values, particularly -Ga when in lines, so this is another way to request data. WARNING: for lots of data, this gets really long!!! But if you are curious how inxi actually constructs its data internally, this sort of shows it. 4. -y 80-xx :: set width to 80 or greater. Note you can also set these in your configurations if you want using the various options supported. ----------------------------------- Bugs: 1. Once again, no real bugs found beyond a few trivial things I can't remember. Fixes: 1. When out of X, dm: showed after Console: and often said dm: N/A particularly on headless servers, which was silly. Now DM: only shows after Console: if a DM: was actually found. If regular Desktop output, either in X, or via --display out of X, no changes. 2. There was a pointless sudo test when sudo values are set initially, they were still running even if --no-sudo was used. Now they don't run in that case. Enhancements: 1. The biggie, now inxi can output in a similar indented way as something like dmidecode if you use the -y 1 option. This feature was originally by request, though the initial request actually just wanted to see it stacked simply, but that was almost impossible to read for any output reasonably long, so I made the indentations very dynamic and deep, they go up to 4 levels in, which is roughly how deep in the inxi sub Categories go. This output format makes it very easy to see how inxi 'thinks' about its data, how it views sets, subsets, subsubsets, and subsubsubsets of data. Note that each data block, as with dmidecode data, is separated by a blank line. You know what this means!!! Yes, that's right!!! You can parse inxi output with awk!!, same way legacy bash+gawk inxi used to parse its data!! Or if your brain just does not like lines of data, you can make it appear in indented single key: value pairs. Here you can see for example that 1 Xorg Display has 1 or more Screens, and each Screen has one or more Monitors. Note that this -Ga data first appeared in inxi 3.1.00. Sample [with bug in OpenGL output!, and showing -Ga newer values as well for dual monitor setup, with one Xorg Screen]: inxi -aGy1 Graphics: Device-1: NVIDIA GT218 [GeForce 210] vendor: Gigabyte driver: nouveau v: kernel bus ID: 09:00.0 chip ID: 10de:0a65 Display: x11 server: X.Org 1.20.8 driver: nouveau unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1 Screen-1: 0 s-res: 2560x1024 s-dpi: 96 s-size: 677x271mm (26.7x10.7") s-diag: 729mm (28.7") Monitor-1: DVI-I-0 res: 1280x1024 hz: 60 dpi: 96 size: 338x270mm (13.3x10.6") diag: 433mm (17") Monitor-2: VGA-0 res: 1280x1024 hz: 60 dpi: 86 size: 376x301mm (14.8x11.9") diag: 482mm (19") OpenGL: renderer: N/A v: N/A direct render: N/A 2. Refactored and cleaned up print_data(), got rid of some early testing code, dumped some unnecessary tests, simplified old tests, and optimized the new indentation logic reasonably well. Hopefully the print_data() will not be quite as much of a black box now as it was. 3. Even more drive vendors and ID matches!!! The list never ends!! An endless series of new vendors and IDs of existing vendors sprout up, then float away. And inxi follows them to the best of its ability. Thanks again to Linux-Lite hardware database, which help make this ever expanding list possible, since their users appear to use every disk known to humankind. Changes: 1. When out of Display, and Console: shows, -S will not show dm: if no display manager is detected, and if it is detected, it shows DM: since it's not part of the Console: set of data. If out of X and --display is used to get Xorg data out of X, it will show Desktop: set of data as normal, at least it will show the stuff it can find. This resolves the issue where dm: appeared to be a member of the set of Console: data, instead of either its own thing, DM:, or a member of the set of Desktop: data. 2. For RAID Devices with sub Array-x: values, Array-x: is capitalized, it used to be array-x: That was silly. 3. In USB, now Device-x: resets inside each Hub: so that the Device-x: are numbered starting at 1 within each Hub:. This makes the counter behavior act the same as it does in for example RAM Array-x: / Device-y:, where each Array-x: resets Device-y: count to 1. This changes the old default of having Device-x: not reset, to let you see the total number of devices plugged in or attached no matter which hub they were plugged into, but the output actually gets sort of confusing in single key: value pair mode per line. 4. The key: value syntax for weather was changed completely, now it works like the rest of the features, with Report:... [Forecast:...] Locale:... and Source:. Locale makes the source of the times and other date related features, and the location if shown or available, much more obvious. Before it was never clear if Current Time referred to your local or the remote time, now it's clearly from the Locale: you specified with -W, or the default -w local info. Also made Report 1 line if unwrapped, Forecast 1 line if not wrapped, and Locale: 1 line if not wrapped, which makes the output easier to read. NOTE: automated weather queries are NOT allowed, if you do it, you will be banned!! inxi is NOT a desktop weather app!! Don't confuse it with one!! Weather is just a small service to users who might for example want to check the weather on a remote system, or something like that, and is not intended to be used on a routine basis. 5. Cleaned up and re-ordered the --version output. It had some pretty old contexts in the language, which were removed or cleaned up and brought up to date. If you're wondering, I roughly use rsync and nano --version as guides for what to show or not show there.	2020-06-12 00:47:10 -07:00
Harald Hope	7ca58b94d2	New inxi, man. New information types, fixes, man updates. ... Bugs: No bugs of any importance fixed or found!! Fixes: 1. Tiny fix, didn't use partition/slice assignment in help menu. BSD interest only since default partition is standard for Linux. Enhancements: 1. Disc Vendors: added a large number of possible disk vendors, without having actual detection data available for all of them, using a different source. Also added, as usual, more disc vendor IDs from linux-lite hardware database, always ready with more vendors! 2. Added groovy gorilla ID for ubuntu 3. Very nice usability change, mostly for support people, now if -y without an integer is supplied, it will assign default column width of 80, which is what you usually want for forums or issue reports, otherwise the output can wrap outside the post or issue report, which is hard to read. Hopefully support people will catch onto this one. 4. This closes issue #217 - Adds dmidecode based extra data: -xxx - shows CPU voltage and external clock speeds -a - shows CPU socket type and base/boost: speed items. These are --admin options because neither is particularly reliable, sometimes they are right, sometimes they aren't, as usual with dmi data. As far as tests show, base speed, what dmidecode misleadingly calls 'Current Speed', which it isn't, is the actual normal non throttled speed of the CPU / motherboard setup. boost is what dmidecode calls 'Max Speed', which it also isn't, though sometimes it is, as with AMD cpus with boost, and no overclocking. With overclocking, sometimes base will be higher, sometimes the actual real current cpu speeds will be higher than all the max/boost values. Motherboard CPU socket type is likewise randomly correct, incorrect, empty, misleading, depending on the age and type of the system, and the CPU vendor. It appears that in general, AMD CPUs will be more or less right if they have this data, and Intel CPUs will sometimes be right, sometimes not, or empty. For > 1 CPU systems, the data is much less reliable.	2020-05-31 14:41:20 -07:00
Harald Hope	2329d54318	small man fix, had wrong copyright date	2020-04-22 21:00:43 -07:00
Harald Hope	c06a034c98	man page fixes, lintian stuff.	2020-04-22 20:04:46 -07:00
Harald Hope	70d13aca4e	New inxi, new man. Huge update, new line types, huge graphics upgrade, new ... switches, bug fixes, glitch fixes, enhancements, you name it, this has got it!! Note that since this features a new primary line item (-j / --swap Swap:), the version number has been bumped to 3.1.0, making this a major version upgrade, the first since the new Perl inxi rewrite was launched, though of course 3.0.0 contained many new line items as well, but this is the first actually new line item since then. Bugs: 1. Big bug fix: if -z used, and -p, and user had partitions mounted in $HOME directory, the partitions would buggily duplicate in the output. 2. See Fix 1, inxi was reporting the wrong (or no in some cases) Xorg driver because it was using the wrong Xorg log, it was only searcing in the original /var/log/Xorg.0.log file, not the newer alternative path locations. Fixes: 1. Both an enhancement and a fix, users reported Xorg log file location changes. Fix is that now inxi uses wildcard searches of all readable locations that can contain the log files, then collects a list of them, and uses the last modified one. This ensures that the best possible guess is made about which actual log file is current, which should lead to significantly more reliable Xorg driver reports overall. Note that this fix works for user level and root level, it will always use the most recent readable file no matter what. For root, that should translate to the most recent on an absolute level Xorg log file. This issue was caused by gdm moving from Xorg.0.log to Xorg.1.log on some systems, but not all, and also, the location is often but not always now: ~/.local/share/xorg/Xorg.[01234..].log [except for root, which is why root has to search for all user Xorg log files to find the most recent one. There were many red-herrings in this issue report, so it took some research to dig through those to the real data sources. 2. Now that the compositor detection is out of early testing mode, enabled always on compositor detection for Wayland systems. Since the compositor is the Wayland display server, it makes sense to always show it if Wayland. Note that there is still no known way to actually reliably get Wayland data beyond simple environmental variables that let inxi detect Wayland is running the desktop. Lack of reliable logs or debugging tools across Wayland compositors makes this entire process about 10-50x more difficult than it should have been. 3. In keeping with 2., also moved compositor: item to be right after server: item. 4. Debian bug: https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=inxi requested that HTTP::Tiny be set to default always check SSL certificates. Now inxi does that, and --no-ssl flag disables this, which makes the Perl http downloader now work roughly the same as wget, curl, etc. 5. Man page fixes, added pointer placeholders for out of alphabetical order options, so you can find anything by looking down the alpha sorted lists, like: --swap - See -j. Since inxi is running out of single letters that match new features, it's easier to point man readers to the right item without them having to already know it to find it. Also added --dbg [2-xx] pointer to github inxi-perl/docs/inxi-values.txt so people interested can learn how to trip the various per feature screen debuggers. Enhancements: 1. updated ubuntu ids, added 'focal LTS'. 2. USB Graphic devices added. This will add support for USB graphics adapters, an uncommon but existing category, often used in SOC boards, for example, but also on desktops, and things like USB webcams. Leaving these off was really just an oversight, the programming internally had the data, it just wasn't using it. 3. Support added for TV card type multimedia devices in Graphics. That was actually a long term oversight, I'd simply missed that in the device ID documentation, one of the multimedia device subtypes is Video device. 4. Huge, massive, internal upgrade to allow for -Ga output, which gives a technically accurate Xorg > Display > Screen > Monitor breakdown. Note that Display and Screen data come from xdpyinfo, and Monitor info comes from xrandr, but if xrandr is missing, the Screen information shows. Technically for -G, -Gxx, end users see very little difference except the per Screen / per Monitor resolutions are listed with a 1: type counter per item. Note that Xorg Screens are NOT Monitors, they are a virtual space Xorg constructs out of the pieces of hardware that make up the Screen space. In many cases, 1 Xorg Screen contains only 1 Monitor, but the dimensions or dpi are frequenty different. New output items: Display: ... display ID: [Xorg Screen identifier, like :0.0]; screens: [Total Xorg Screens in current Display]; [s-default: [if > 1 Screens, default Screen number]] Screen-x: [Screen number]; s-res: [Xorg Screen resolution]; s-dpi: [Xorg Screen dpi]; s-size: [Xorg Screen mm (inch) size; s-diag: [diagonal of Xorg Screen size] Monitor-x: [Monitor Xorg ID]; res: [Actual monitor pixel dimensions]; hz: [actual monitor reported frequency]; dpi: [actual monitor dpi as calculated from actual monitor resolution/size; size: [actual monitor size in mm (inch); diag: [actual diagonal size in mm (inch). 4a. -Gxx now shows Xorg s-dpi: for the Screen as well, after the main resolution section for -G. 5. Big improvement in error messages and logging for Xorg driver detections, this logic is much more robust now, but after the main driver fix, also much less likely to ever be seen. 6. Almost not visible to users, but major internal graphics refactor allows now for more modular treatment, and eventual Wayland data sourcing. Currently most Wayland data sourcing is in stub form, or only logically possible, but as it grows possible (if ever, since Wayland protocal appears to have totally neglected enforcing single location logging, and single tool debugging for the entire Wayland protocol of compositors, a massive oversight in my view). The -Ga refactors internally made this much more possible, and I integrated switches and tests, and fallbacks, and stubs in some locations, so it was clear where current Xorg specific logic is, and where future Wayland logic will fit in, sort of anyway. 7. Debugger tools added for new features, or most of them. 8. New primary line item: --swap / -j. This moves all swap data to a dedicated Swap: line, which looks roughly the same as Partition: lines, but when -j/--swap is used, all swap types, not only physical partition swaps, show. This should make some users happy. 9. Added more cpu family IDs for Zen 2 series of cpu, tweaked some later Intel cpu family ids in terms of cpu arch name tool. 10. By request, added ability filter out all UUID or Partition Label strings in -j, -o, -Sa, -p, -P. Those are tripped by --filter-label and --filter-uuid. Mostly useful in fringe cases, for example, replacing label or UUID from -Sa kernel boot parameters with root=LABEL=<filter>, or in cases you want to show full -v8 output without showing UUID or Labels, whatever. 11. Added --no-dig/--dig plus configuration option NO_DIG=true. This disables dig in cases where dig is installed but failed due to maybe network firewall rules or something, and WAN IP detection fails. Normally you always want to use dig, it's faster, more reliable, and safer, than all the other regular downloader based methods, but we have seen server setups where for some reason those types of dig requests were blocked, thus disabling WAN IP detection. 12. Added in WAN IP failure case, if dig was used, suggestion to try again with --no-dig, since most users are unlikely to learn about this issue, or the solution to it. 13. Added single letter shortcut -J for --usb, maybe this will help people discover usb component of inxi, now you can request for instance: inxi -FJaz 14. Added xonsh to supported shells, that had tripped a perl undefined value for start client bug since xonsh uses single word for version, xonsh/234 so the default value, 2nd word, was undefined. 15. More SSD and USB drive vendors from the endless fountain over at Linux Hardware Database (linuxliteos.com). Changes: 1. Small change in how screen resolutions are output in -G non -a mode, now each Screen / Monitor will increment by 1 the 1: [resolution~hz] key. This helps make it more readable. Note that in non -a mode, the increments are just based on Screen, then Monitor, Monitor, Screen, and so on, counts. Most users will only have one Screen systems, but more advanced setups may use the Xorg > 1 Screen, each screen able to run > 1 monitors. The counts in say, a 2 Screen system, with 3 monitors, would be: 1: res1 [from screen 0, monitor 1] 2: res2 [from screen 0, monitor 2] 3: res3 [from screen 1, monitor 1. If xrandr is not installed, it would show: 1: res1 [from screen 0] 2: res2 [from screen 1]	2020-04-22 19:35:53 -07:00
Harald Hope	d65b40e60a	Bugs: ... 1. Fixed undefined error that could happen, in rare cases, in hdd_temp logic. Fixes: 1. Fixed Elbrus cpu nazming, model 9 is 8CV, not 8CB (Cyrillic error) 2. Preventitive, was not using '-' quite correctly in all regex ranges. 3. Had wrong desktop string listed in Unity 4. Reordered Family/Drive model in usb drive reports, it's to make it more obvious what is what. 5. Adjusted indexing of splits to get better results in corner cases. 6. Fixed some numbering issues. 7. Added trimming n1 from nvme0 type names for nvme, this corrects some issues users were having. 8. Fixed a division by 0 error in smartctl data grabber. 9. Fixed a Perl issue, didn't realize perl treats 000 as a string, not 0. 10. Another Perl fix, int() only wants to get numeric values sent to it, I'd assumed a different behavior, non numerics get converted to 0, but that's not how Perl sees things. Things like this, by the way, are why Perl is so absurdly fast. Enhancements: 1. More disk vendors. The list will never be complete!! We have found eternal churn!! Thanks to linux lite hardware database as always. 2. Big one!!! Now inxi uses smartctl data, if installed, for getting advanced drive information (with -a). See man and help for details. Will show failing drives, etc. Lots of info can be available, but sometimes data is not in smartctl db, so inxi can't find it, that's not an inxi bug, it's just how it is. 3. Made hours on more human readable, into days/hours, for -a smartctl disk report. 4. Added $test[12] for smartctl data printout, and $test[13] for disk array print out. Note that advanced debugger outputs can change or vary depending on what is being worked on so don't in general rely on these always being around. But they do tend to say stuck in place once I add them. 5. Added some nvme stuff, spare reserve, if you need it, you'll appreciate it, if not, you'll never know it's there. 6. By request from some forum issue thread: made --host only be shown onif not --filter or not --host. This makes -z remove hostname, but retains ability to do absolute overrides. Hostname should have always been filtered out like that, it was an oversight. I think that was Manjaro who asked that, but I forget. Note that this change, as usual, will not alter expected behaviors if users have config item for hostname set. 7. Added support for picom compositor, thanks user codebling for that, I think that's compiz fork, the real branch that is that is being developed.	2020-03-14 23:15:16 -07:00
Harald Hope	f2cfb7edfb	New version, man page, exciting changes!! ... Bugs: 1. issue #200 - forgot to add all variants for -p, now works with --partition-full and --partitions-full 2. issue #199 - another one, forgot to add --disk to -D for long version. Thanks adrian15 for both of these, he was testing something and discovered these were missing. 3. Issue #187 an issue with RAID syntax not being handled in a certain case, thanks EnochTheWise for following through on this one. This turned out to be a bad copy paste, a test pattern did not match the match pattern. Fixes: 1. Fixed some docs typos. 2. Issue #188 fixed protections and filters for some glxinfo output handlers. 3. Issue #195, for Elbrus bit detection. 4. Added filter to cpu data, was not skipping if arm, so Model string was treated numerically. Enhancements: 1. Added rescatux to Debian system base detections. This closes issue #202, again from adrian15, thanks. 2. For cpu architecture, updated for latest AMD ryzen and other families, like Zen 3, which is just coming out re available data. Also latest Intel, which are trickier to ID right now, but I think I got the latest ones right, That's things like coffee lake, amber lake, comet lake, etc. 3. Huge one, full (hopefully out of the box) Russian Elbrus CPU support. Thanks to the alt-linux and the others who helped provide data and feedback to get support. Note that this was also part of correcting 64 bit detection for e2k type, which is how Elbrus IDs internally. See issue #197 which I've left open for the time being for more information on this CPU and how it's now handled by inxi. Note all available data should now work for Elbrus, including physical cpu/core counts etc. Elbrus do not show flag information, nor do they use min/max speed, so that data isn't available, but everything else seems to work well. 4. Eternal disk vendors. Thanks linux lite hardware database, you continue to help make the disk vendor feature work by supplying every known vendor ever seen. 5. To close debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942194 Note that the fix is simply to give the user the option to disable this behavior with the new --no-sudo and NO_SUDO configuration file options. This issue should never have been filed as a bug since even the poster admitted it was a wishlist item, but because of how debian bug tracker works, it's hard to get rid of invalid bugs. Note that this is the internal use of sudo for hddtemp and file, not starting inxi with sudo, so using this option or configuration item just removes sudo from the command. Note that because the user did not do as requested, and never actually filed a github wishlist issue, and since his request was vague and basically pointless, the fix is just to let you switch off sudo, that's all.	2019-11-19 20:42:21 -08:00
Harald Hope	92df6e1ae0	New version, many small fixes. And a hall of shame, LOL. ... Bugs: 1. Issue #188 exposed a situation in glxinfo where the required opengl fields are present but contain null data. This happens when a system does not have the required opengl drivers, which was the case here. inxi failed to handle that. Thanks LinuxMonger for posting the required data to figure this corner case out. 2. Fixed a long time bug in Disk vendor ID, there was an eq (string equals) where it was supposed to use regex pattern match. Oops. Would have led to disk vendor id failures in several cases. Fixes: 1. help, man updates for RAM/Memory data, more clarifications. 2. Refactored RepoData class/package, to make it easier to handle repo string data, and make it all overall cleaner internally, and enable future extensions to certain features in inxi that may or may not one day become active. 3. Added to some regex compares \Q$VAR\E to disable regex characters in strings. I should have used that a long time ago, oh well, better late than never! 4. Found a horrible case were xdpyinfo uses 'preferred' instead of the actual pixel dimensions, shame on whoever allowed that output!!! shame! Had to add a workaround to make sure numeric values are present, if not, then use the fallback, which means, 2x more data parsing to get data that should not require that, but in this example, it did (an Arch derivative, but it could be xdpyinfo itself, don't know)> Enhancements: 1. More fixes on issue #185. Thanks tubecleaner for finding and provding required data to really solve a set of RAM issues that apply particularly in production systems. This issue report led to 2 new options: --memory-short, which only shows a basic RAM report. Memory: RAM: total: 31.43 GiB used: 14.98 GiB (47.7%) Report: arrays: 1 slots: 4 modules: 2 type: DDR4 And a 2nd, --memory-modules, only shows the occupied slots. This can be useful in situations where it's a server or vm with a lot of slots, most empty: Memory: RAM: total: 31.43 GiB used: 15.44 GiB (49.1%) Array-1: capacity: 256 GiB slots: 4 EC: None Device-1: DIMM 1 size: 16 GiB speed: 2400 MT/s Device-2: DIMM 1 size: 16 GiB speed: 2400 MT/s Note that both of these options trigger -m, so -m itself is not required. 2. More disk vendors!! The list never ends! Thanks linux-lite hardware database and users for supplying, and buying/obtaining, apparently every disk known to mankind. 3. Added fallback XFCE detection, in cases were the system does not have xprop installed, it's still possible to do a full detection of xfce, including toolkit, so now inxi does that, one less dependency to detect one more desktop. 4. Added vmwgfx driver to xorg drivers list. Note, I've never actually seen this in the wild, but I did see it as the kernel reported driver from lspci, so it may exist. Unfixed: 1. Issue #187 EnochTheWise (?) did not supply the required debugger data so there is a RAID ZFS issue that will not get fixed until the required debugger data is supplied. Please do not waste all our time filing an issue if you have no intention of actually following through so we can get it fixed. Note that a key way we get issues here is from Perl errors on the screen, which are a frequent cause of someone realizing something is wrong. This is why I'm not going to do a hack fix for the RAID ZFS issue, then the error messages will go away, and it will likely never get handled. For examples of good, useful, productive issue reports, and how to do them right: #188 and #185, both of which led to good improvements in how inxi handles corner cases in those areas.	2019-08-14 11:14:13 -07:00
Harald Hope	0757b3a816	New version. Bug fixes, updates. ... Bugs: 1. Issue #185 exposed a small long standing bug in ram max module size logic. Was not retaining the value each loop iteration, which could lead to way off max module size guesses. Note that this could lead to a VERY wrong max module size report. 2. Issue #185 also exposed a rarely seen undefined value for ram reports, was not tested for undefined, now is. Fixes: 1. cleanup of comments in start client debugger that made it unclear. 2. Got rid of all the legacy development modules that were in inxi-perl/modules. These were totally out of date and pointless to retain. Enhancements: 1. Added eoan ubuntu 19-10 release name 2. Added zen cpu model ID. 3. Disk vendors and new vendor IDs added. Thanks linuxlite hardware database. 4. Made a backend tool to check for new unhandled disks, this makes updating disk/vendor IDs a lot easier. 5. Updated inxi-perl/docs with new links etc.	2019-07-15 19:56:44 -07:00
Harald Hope	9a3c442c9f	man edits	2019-04-30 19:06:19 -07:00
Harald Hope	f5ea688e8d	more man edits	2019-04-30 18:29:35 -07:00
Harald Hope	63d13ff858	small man edit	2019-04-30 18:26:25 -07:00
Harald Hope	b3c72ae289	New version, new man, new feature!! Bug fixes! ... Bugs: 1. issue #182 - in freebsd, there was an oversight in the pciconf parser, it was using unfiltered strings as regex pattern, and of course, a string flipped an error. Fix was to add the regex cleaner to the string before it's used in test. 2. NOTE: issue #182 had a second bug, but the issue poster didn't follow up with data or output so it couldn't be fixed. This was related to a syntax change in usbdevs -v output in FreeBSD. Such changes are too common, but it might also simply be a variant I have not seen or handled, but so far no data, so can't fix. Don't blame me if you get this bug, but do post requested debugger data if you want it fixed! Fixes: 1. Updated man for weather, explained more clearly how to use country codes for weather output. More clarifying in general about weather location, and weather restrictions. Enhancements: 1. Added avx/avx2 to default flag list in -C short form. Thanks damentz from liquorix for clarifying why that was a good idea. Note the initial issue came up in a Debian issue report, not here. People!! please post issues here, and don't bug maintainers with feature requests! Maintainers aren't in a position to add a feature, so you should go straight to the source. 1.a. Created in inxi-perl/docs new doc file: cpu-flags.txt, which explains all the flags, and also covers the short form flags and explains why they are used. 2. To resolve another issue, I made a new documentation file: inxi-perl/docs/inxi-custom-recommends.txt This is instructions for maintainers of distros who do not use rpm/apt/pacman but still want the --recommends feature to output their package pool package names for missing packages. I decided to not allow more than the default 3 package managers because no matter what people say, if I allow in more, the maintainer will vanish or lose interest, and I'll be stuck having to maintain their package lists forever. Also, it's silly to even include that package list for any distro that does not use rpm/apt/pacman, since the list is just wasted lines. Instructions in doc file show what to change, and how, and has an example to make it clear. Odds of this actually being used? Not high, lol, but that's fine, if people want it done, they can do it, if not, nothing bad happens, it just won't show any suggested install package, no big deal. 3. Using the new disk vendor method, added even more disk vendors. Thanks linux litet hardware database!! 4. EXCITING!! A new --admin/-a option, suggested by a user on techpatterns.com/forums/ Now -S or -b or -F with -a option for GNU/Linux shows the kernel boot parameters, from /proc/cmdline. Didn't find anything comparable for BSDs, if you can tell me where to look, I'll add it for those too, but wasn't anywhere I looked. Do the BSDs even use that method? Don't know, but the logic is there, waiting to be used if someone shows me how to get it cleanly. The 'parameters:' item shows in the main 'System:' -S output, and will just show the entire kernel parameters used to boot. This could be very helpful to distros who often have to determine if for example graphics blacklists are correctly applied for non free drivers, like nomodeset etc, or if the opposite is present. For forum/distro support, they just have to ask for: inxi -ba and they will see t the relevant graphics info, for instance, or -SGaxxx, or -Faxxx, whatever is used to trigger in this case the graphics and system lines. 5. Updated man/help for 4 as well, now explains what they will see with --admin/ -a options and -S. Good user suggestion, I wish all new features were this easy, heh.	2019-04-30 17:56:10 -07:00
Harald Hope	2650a51d3b	New version, new man. Weather explanations, disks, bugs!! ... Bugs: 1. For sensors, in some cases, gpu failed to show correctly. This should be corrected. Fixes: 1. Made help/man explanations of weather changes more clear. Particularly in regards to no automated query info. But also for supported location syntaxes. 2. Some corner cases of null weather data return null and tripped a null data error. This is corrected. 3. Added city duplicate filter to weather output, this hopefully will in some cases avoid printing city name twice, depends on weather source. 4. Removed --weather-source option 0, that no longer works so all code was removed. 5. More deb822 fixes, loosened up even more syntax. That's a poorly designed config syntax, hard to work with. Enhancements: 1. Lots of new disk vendors. So many!! Thanks linux-lite hardware database! switched to a new method of getting disk name/vendor data, now it's a lot easier to check for new ones. 2. Added fancybar to desktop info.	2019-03-29 14:11:22 -07:00
Harald Hope	1f037020e3	New version, new man. A few more modifications to weather. ... Fixes: 1. In case with zero wind speed, it now shows zero, not N/A, as expected. Enhancements: 1. Depending on weather source used: * Shows precipitation, not rain/snow. * Adds Sunrise/sunset (most sources do not have this)	2019-02-07 20:52:41 -08:00
Harald Hope	a9fbd19a9b	New version, new man page. Big update! Get it in before your freeze!! ... Bugs: 1. Maybe the vendor/product regex, which when + was used, would put out errors. 2. Maybe Fix 4, since that could lead to incorrect behavior when sudo is involved depending on sudo configuration. 3. BIG: current inxi weather will probably fail if not updated to this or newer versions!! Not an inxi bug per se, but your users will see it as one. Fixes: 1. Fixed Patriot disk ID. 2. Fixes for PPC board handling. 3. Regex cleaner fixes, this could lead to error in special cases of product vendor names. 4. crazy from frugalware pointed out that $b_root detection was flawed, and relied on a bad assumption, particularly for sudo. As usual, he's right, that is now corrected, and uses $< Perl native to determine UID. Enhancements: 1. Added septor to Debian system base. 2. Removed quiet filters for downloaders when using --dbg 1, now you see the entire download action for curl/wget downloads. This went along with issue # 174 3. New feature: --wan-ip-url. This closed issue #174. Also has user config option: WAN_IP_URL as well to make changes permanent. 4. Added --dbg 1 to man and help. The other --dbg options are random and can change, but --dbg 1 is always for downloading, so might as well tell people about it. 5. To anticipate the loss of a major weather API, inxi is redone to use smxi.org based robust API. This also allows for a new switch, --weather-source (or --ws for shorter version), options 0-9, which will trigger different APIs on smxi.org. Added WEATHER_SOURCE configuration option as well. Note that 4-9 are not currently active. Also added in better error handling for weather. The main benefit here is that inxi is now largely agnostic to the weather APIs used, and those can be changed with no impact to inxi users who are running frozen pool inxi's, or who have not updated their inxi versions. NOTE: all inxi versions older than 3.0.31 will probably fail for weather quite soon. So update your inxi version in your repos!! 6. More disk vendors IDs and matches. Thanks linuxlite hardware database. 7. Going along with weather changes, added, if present, cloud cover, rain, and snow reports. Those are for previously observed hour. 8. Small change to Intel CPU architecture, taking a guess on stepping for skylake/Cascade lake ID. Guessing if stepping is > 4, it's cascade lake. But could not find this documented, so it's a guess. At worst, it means that Cascade lake, which must be a later steppingi than 4, will not be ID'ed as skylake. 9. Documentation updates for data sources. Changes: 1. inxi now uses a new system to get weather data. There is no longer a risk of weather failing if the API used locally in inxi fails or goes away. This change should be largely invisible to casual users. 2. In weather, moved dewpoint to be after humidity, which makes a little more sense.	2019-02-06 18:31:55 -08:00
Harald Hope	1976702562	New version, new man page. ... Bugs: 1. Both a fix and a bug, in that inxi had an out of date list of Xorg drivers. This led to all the newer Intel devices failing to show their drivers in the Xorg driver lines, like i915, i965, and so on. Updated to full current list of Xorg drivers. This is not technically a bug since it's simply things that came into existence after that logic was last updated. But it looks like a bug. Fixes: 1. Issues #170 and #168 showed a problem with inxi believing it was running in IRC when Ansible or MOTD started inxi. This is because they are not tty so trip the non tty flag, which assumes it's in IRC in that case. The fix was to add a whitelist of known clients based on the parent name inxi discovers while running inside that parent. MOTD confirmed fixed, Ansible not confirmed. Why do people file issue reports then not follow them? Who knows. Note that this issue is easy to trip by simply doing this: echo 'fred' | inxi which disables the tty test as well. To handle that scenario, that is, when inxi is not first in the pipe, I added many known terminal client names to the whitelists. This works in my tests, though the possible terminals, or programs with embedded terminals, is quite large, but inxi handles most of them automatically. When it doesn't, file an issue and I'll add your client ID to the whitelist, and use --tty in the meantime. 2. Issue #171 by Vascom finally pinned down the wide character issue which manifests in some character sets, like greek or russian utf8. The fix was more of a work-around than a true fix, but inxi now simply checks the weather local time output for wide characters, and if detected, switches the local date/time format to iso standard, which is does not contain non ascii characters as far as I can tell. This seemed to fix the issue. 3. Added iso9660 from excluded file systems for partitions, not sure how inxi missed that one for so long. 4. See bug 1, expanded and made current supported intel drivers, and a few other drivers, so now inxi has all the supported xorg drivers again. Updated docs as well to indicate where to get that data. Enhancements: 1. As usual, more disk vendor/product ID matches, thanks to linuxlite hardware database, which never stops providing new or previously unseen disk ids. Latest favorite? Swissarmy knife maker victorinox Swissflash usb device. 2. Added Elive system base ID. 3. Added Nutyx CARDS repo type.	2018-12-31 21:11:01 -08:00
Harald Hope	b119455049	New version, fixes, updates, missing specs. ... Bugs: 1. See fix 4, incorrect positioning of Trinity desktop detection logic. Fixes: 1. Vascom reports in issue #169 that some systems are making the /sys cpu vulnerability data root read only. Added <root required> test and output. 2. A while back, they added several chassis types in the smbios specifications. I used an older specification pdf file, this is now corrected. Note that realworld use of the new types exists, like tablet, mini pc, and so on. This missing data caused Machine report to list N/A as machine type when it was actually known. I'd been using an older specification PDF, and had failed to look at the actual spec download page, where you could clearly see the newer spec file. Corrected this in the inxi docs as well. 3. Made gentoo repo reader check for case insensitive values for enabled. Also extended that to other repo readers that use similar syntax, they are all now case insensitive (Yes/yes/YES, that is) 4. Fixed incorrect handling of Trinity desktop ID, that needed to happen in the kde ID block, as first test, not after it. Caused failure in Q4OS trinity, and maybe others. I'm not sure why inxi had the detection where it was, it made no real sense, so that's now nicely integrated, so these types of failures should not happen again. Thanks Q4OS for exposing that issue. Enhancements: 1. Added TDM and CDM display managers. Never seen either (Q4OS uses TDM), TDM corrected. CDM not confirmed, don't know if it's still around, but if it is similar to TDM re cdm.pid in /run, it should be detected fine. 2. Added more disk vendors/ids, the list never stops!! Thanks LinuxLite Hardware database, your users seem to use every disk known to humanity. 3. Added Debian derived Q4OS distro ID and system base handler.	2018-12-10 11:23:16 -08:00
Harald Hope	6bef996c55	man page fix	2018-11-29 21:30:30 -08:00
Harald Hope	121e07682e	New version, new man. Fixes, enhancements. ... Bugs: 1. ARM fix, odroid > 1 cpu speeds not showing correctly. 2. Ansible start fixes. 3. Fringe Battery failures, see Pinebook. Fixes: 1. Removed null data message 'old system' since that's not always the case. 2. Added support for > 1 CPU speeds in systems with > 1 CPU. 3. Added is_numeric test for sudo version tests, that was tripping errors in rare cases. 4. Fine tuned terminal size setting to check that is int to correct the Ansible problem. 5. ARM Pinebook fixes, battery, cpu. This also fixes corner cases where the battery charge state is missing but it is a systme battery. Enhancments: 1. Added more disk ID matches/vendors. Thanks LinuxLite Hardware database!! 2. UKUI, ukwm, ukui-panel added to desktop data. 3. Added PopOS to system base. 4. Ansible/Chef user noted that inxi believes that it is running in IRC when started by Ansible / Chef (not sure about Chef but assuming it's the same). Added flag --tty flag to force inxi to believe it's running in shell no matter what starts it. Note that this fix is not confirmed because the person didn't confirm the fix. Annoying. 5. Added Ubuntu disco to ubuntu_id.	2018-11-29 21:23:15 -08:00
Harald Hope	281e57bb6f	New version, new man. Fixes, stitches, and returns!! ... Bugs: 1. As a fix (3), failure to handle spaces in mount source names. More of a fix than a bug, since it was an old issue #63. 2. OSX errors, BSD errors, but not really inxi errors or bugs, more weird data tripping null data or unreadable file errors, but I'll call those bugs since they look like bugs to end users. See Fixes for more. 3. See Fix 4, this is sort of a bug, inxi failed to return expected values on success/failure. Fixes: 1. One of the documented config items, COLS_MAX_NO_DISPLAY had not been implemented internally. This is now corrected. 2. Apple OSX was returning errors, those were fixed. 3. Finally handled ancient issue #63, support now there for spaces in remote source name. This means that both spaces in source block name, and mount point name, are in theory both handled now. This was also to fix an osx issue #164 despite the fact that technically I do not support osx beyond fixing errors, but since in this case the issue was a long standing one, I fixed it for everything. 4. Big fix, I'd completely left undone proper unix type error number returns in inxi, oops. Thanks Unit193 for noticing that and prompting me to fix it. Now inxi returns integer success/error numbers as expected. 5. OSX xml based version info broke, of course, naturally it would, so I added in an osx fallback where if no distro version detected, use fallback unix method, which is what all the other unices use. 6. Along with space in source name, fixed mapped handling a bit more too for partitions. 6. Added cifs remote file system to disk size used blacklist, and iso9660. Not sure how I'd missed those for so long. 7. OpenBSD vmstat in 6.3 changed the column order for avm/fre, and changed to a, sigh, human readable default format, in M, so to handle this for all bsds, I had to make a dynamic column detection for avm and fre, and use those after, and also i had to add in a M detection, if found, *1024 and strip out M, sigh. 8. OpenBSD, another alternate ordering/syntax issue, the dmesg.boot data for disks does not always use the same order in comma separated list, saw user case where the first item after : was the MB size, not the second. Made detection dynamic. 9. Due to Android case, found types where no cpu speed data was found, no max speed at least, which tripped an error due to null data for ARM, this is now handled, now cpu speed min/max read permissions in /sys are checked first before trying to read, and default failures are better handled. 10. On man page, added in clarification of the moving of Memory: item from Info: line to ram Memory: line, explaining when it appears where. I do not removing the item from -I, I may revert that change, I find it non-intuitive to move that around. Enhancements: 1. Added display manager Ly, plus Ly version number. Thanks NamedKitten, this closes issues #166 #165 #162 2. Improved documentation a bit to avoid ambiguity re how to get colors in output. That handles issue #161, thanks fugo for the nudge to improve the documentation. 3. First inxi on Android tests, using termux, which has a debian based apt type installer, got inxi running on at least two devices, including pixel2, but discovered that apparently as of android 5, /sys is now locked up in terms of wildcard reads, but further analysis is required, but as of now, inxi works in termux, but fails to get any Device data for A, G, or N. Thus it also fails to match IF to Device, so none of the IP data shows up. The latter will probably be fixed since Android has ip and ifconfig already, or termux does, but so far I found no way to get device data for ARM in Android 5.x and greater (checked on android 7 and 9 in real phones). 4. More disk vendors!! thanks linuxlite / linux hardware database for offering an apparently never ending list of obscure and not so obscure disk vendors and products. 5. While I was unable to get confirmation or documentation on file names for tce repo files, I guessed that localmirrors would be used, but this may be any random text file in /opt at all, no extensions, I'd have to test to confirm or deny possible values. 6. To handle more complex debugger failures, added --debug-no-proc, --debug-no-exit, to skip or enable completion where proc or sys debugger is hanging. Changes: 1. Changed vendor in A, G, and N to -x, not -xxx, this data seems much more useful and reliable than I'd first expected when I made the feature, the -xxx was more an indication of my lack of trust in the method and source, but so far it seems pretty good, so I bumped it up to an -x option. Note that also, it's quite useful to know the vendor of, say, your network or graphics card, not just the actual device internal data, which is all inxi has ever shown previously. 2. Small change, if no partition type data is found, dev, remote, mapped, default now says 'source:' instead of 'dev:' which makes more sense. Note that df calls that column 'source', so I decided to go with their language for the default not found case. Also changed mapped to say mapped. This was part of a bit of a refactor of the partition type logic, enhanced by adding mapped to existing types, and moved the entire type detection block into the main data generator, and out of the data line constructor. Optimizations: 1. Tested, and dumped, List::Util first() as a possible way to speed up grep searches of arrays, where the goal is just to see if something is in an array. My expectation was that first(), returning the first found instance of the search term, would of course be faster since it will always exit the search loop was met with the sad fact that first() is about 2 to 4 times SLOWER than grep() native builtin. I tested this fairly carefully, and used NYTProf optimizer tool and the results were totally consistent, first() was always much slower than grep(), no matter what size the array is. I assume this means the core C programming that makes grep is simply much better than the File::Util module programming that makes first(). Removed first() and now know that nothing will be faster than grep so no need to look there for speed improvements. The moral of the story: just because something should in theory be faster, does sadly not mean it will be faster, for there are bigger things at work, skill of the programmers who made the logic, how perl handles external vs internal tools, and so on. As an aside, this forms a fairly consistent pattern where I've found Perl by itself to be faster than modules in many cases, that is, it's faster to write the code out than to use a module in many cases that I have tested, so I will always test such ideas and dump every one that is in fact slower than native Perl builtins.	2018-10-14 16:16:06 -07:00
Harald Hope	4e7a20a4b4	man edit	2018-09-28 14:54:00 -07:00
Harald Hope	95cf1aaed9	New version, new man. ... Bugs: 1. If you consider failure to identify a mounted yet hidden partition a bug, then that bug is fixed, but I consider that as more of a fix than a bug. Fixes: 1. Added more device pattern ID for odroid C1 and C2, these are now pretty well supported. 2. inxi failed to handle a certain type of hidden partition, so far only seen with udiskctl mounted TimeShift partitions, but this may be a more general udisk issue, but so far not enough information. The fix is to use the lsblk data to build up missing partitions, so this fix is for non legacy Linux systems only. The fix works pretty well, but it's hard to know until we get a lot more real world data, but given so far I've received only one issue report on it, I suspect this is not a common situation, but you never know, it would never have shown up in datasets unless I had looked specifically for it, so it may be more common than I think. 3. Cleaned up and simplified new --admin -p and -d logic. Enhancements: 1. For debugging, renamed all user debugger switches to have prefix --debug. These options are to help debug debugger failures, and so far have been tested and solved the failures, so I'm adding them all to the main man and help menu, thus raising them to the level of supported tools. These were enormously helpful in solving proc or sys debugger hangs. * --debug-proc * --debug-proc-print * --debug-no-sys * --debug-sys * --debug-sys-print 2. Added findmnt output to debugger, that may be useful in the future. Also added df -kTPa to also catch hidden partitions in debugger. 3. Added in another user level debugger, triggered with --debug-test-1 flag. This will do whatever operation is needed at the time for that user. Some issues can only be resolved by the user on their machine. 4. More disk vendors and matches!!! Thanks linuxlite/linux hardware database!	2018-09-28 14:25:17 -07:00
Harald Hope	894c5fe925	New version, new man. Huge set of changes. Excitement!! Thrills! Spills? ... Bugs: 1. There was a missing main::is_int test that in some instances triggered error. This is corrected. 2. More of a fix, but legacy devices were not matching NIC to IF because the /sys path was not a link as it is now. I made a separate function to handle that match test so it could be more readily be worked with. Fixes: 1. Arch/Manjaro presented yet another Xorg.wrapper path, this time /usr/lib. Why? who knows. That to me is a bug, but since if it's not handled in inxi, it makes it look like inxi has a server: -G bug, I worked around it. Again. This creates the bug when you do not use the actual true path of Xorg where Xorg.wrapper complains and will not show -version data. Why move this? why use that wrapper thing? I don't know, makes no sense to me. 2. More MIPS data, thanks manjaro ARM people. This made MIPS much better, though it will certainly need more work. 3. Better ARM support, added in devicetree strings, which helps pad out the Devices IDs, albeit with very little data, but at least the devices are detected. Thanks Manjaro ARM people there again. 4. Removed Upstart init test for arm/mips/sparc devices. This test made MIPS device totally puke and die, killed networking, so since very few upstart running systems will be arm/mips devices, I decided there better safe than sorry. 5. Found another uptime syntax case, MIPS as root does not have the users item. 6. Many tweaks to SOC data generators, will catch more categories, but the lists will never be done since each device can be, and often is, random re the syntax. 7. USB networking failed to test usb type for 'network', which led to failed ids on some device strings. SOC types are now filtered through a function to create consistent device type strings for the per device tool to use to assign each to its proper @device_<type> array. 8. For pciconf/FreeBSD, cleaned up device class strings to get rid of 0x and trailing subsubclass values, this converts it into the same hex 4 item string that is used by GNU/Linux/lspci so I can apply consistent rules to all pci types, no matter what the generator source is, lspci, pcidump, pciconf, and eventually pcictl if I can get netbsd running. 9. Fixed internal --dbg counts for various features, and updated docs for that. 10. Fixed ARM / MIPS missing data messages, they were redundant. 11. Ongoing, moving excessive source comments to inxi-values.txt and inxi-data.txt. 12. Added unity-system-compositor as mir detection, who knew? I guess that was its production application name all along? Oh well. Enhancements: 1. Added basic support for OpenIndiana/Solaris/SunOS as a bsd type. Just enough to make errors not happen.-repos 2. future proofed unix/bsd detections just to avoid the unset $bsd_type of non BSD unix. 3. Added S6 init system to init tool. 4. Added OpenBSD pcidump to new DeviceData feature. Includes now <root required> message on Device-x: lines if not root. All working. 5. Fully refactored the old pci stuff to DeviceData package/class, due to adding so many types to that, it made sense to make it a single class. 6. Did the same to USBData, because of lsusb, usbdevs, and /sys usb, made sense to integrate the data grabber into one package/class 7. Added speed: item to USB:, it shows in Mb/s or Gb/s 8. Added Odroid C1/C2 handling, which is one big reason I opted to refactor the devices data logic into DeviceData. 9. Added ash shell, not sure if that detection will work, but if it does, it will show. 10. As part of the overall DeviceData refactor, I moved all per type data into dedicated arrays, like @device_graphics, @device_audio, @device_network, etc, which lets me totally dump all the per device item tests, and just check the arrays, which have already been tested for on the construction of the primary DeviceData set. Moved all per type detections into DeviceData so that is now one complete logic block, and the per type data generators don't need to know about any of that logic at all anymore. 11. Added sway, swaybar, way-cooler as window managers, info items. Not 100% positive about the --version, their docs weren't very consistent, but I think the guess should be right if their docs weren't incorrect. 12. Added vendor: item to network, not sure why I kept that off when I added vendor: to audio and graphics. It made sense at the time, but not now, so now -GNA all have vendor: if detected. 13. More device vendors!! The list never ends. Thanks linuxlite/linux hardware database, somehow you have users that manage to use every obscure usb/ssd/hdd known to humanity. 14. Big update to --admin, now has the following: A: partitions: shows 'raw size: ' of partition, this lets users see the amount of file system overhead, along with the available size as usual. B: partitions: show percent of raw in size: C: partitions: show if root, block size of partition file system. Uses blockdev --getbsz <part> D: partition: swap: show swappiness and vfs cache pressure, with (default) or (default <default value) added. This apparently can help debugging some kernel issues etc. Whatever, I'll take someone's word for that. E: Disks: show block size: logical: physical: 15. New option and configuration item: --partition-sort / PARTITION_SORT This lets users change default mount point sort order to any available ordering in the partition item. Man page and help menu show options. 16. Going along with the MIPS fixes, added basic support for OpenWRT, which uses an immensely stripped down busybox (no ps aux, for example), maybe because it only runs as root user/ not sure, anyway, took many fixes. Changes: 1. Changed usb: 1.1 to rev: 1.1 because for linux, we have the USB revision number, like 3.1. Note that this is going to be wrong for BSDs, but that's fine. 2. Changed slightly the output of Memory item, now it follows the following rules: A: if -m/--memory is triggered (> -v4, or -m) Memory line always shows in Memory: item, which makes sense. Note that -m overrides all other options of where Memory minireport could be located. B: if -tm is triggered, and -I is not triggered, Memory shows in in -tm C: if -I is triggered, and -m is not triggered, Memory: shows in -I line. D: no change in short form inxi no arg output, Memory is there.	2018-09-24 16:50:33 -07:00
Harald Hope	9046b7873d	New version, new man page. Bug fix, enhancements, fixes. ... Bugs: 1. Big bug found on certain systems, they use non system memory memory arrays, inxi failed to anticipate that situation, and would exit with error when run as root for -m when it hit those array types. These arrays did not have modules listed, so the module array was undefined, which caused the failure. Thanks Manjaro anonymous debugger dataset 'loki' for finding this failure. This is literally the first dataset I've seen that had this issue, but who knows how many other system boards will show something like that as well. Fixes: 1. Related to bug 1, do not show the max module size item if not system memory and size is less than 10 MiB. Assuming there that it's one of these odd boards. Enhancements: 1. For bug 1, extended Memory: report to include array type if not system memory. That instance had Video Memory, Flash Memory, and Cache Memory arrays along with the regular System Memory array. Now shows: use: Video Memory for example if not System Memory to make it clear what is going on. 2. Added basic Parrot system base, but for some inexplicable reason, Parrot changed the /etc/debian_version file to show 'stable' instead of the release number. Why? Who knows, it would be so much easier if people making these derived distros would be consistent and not change things for no good reason. 3. Added a few more pattern matches to existing vendors for disks. As usual, thanks linuxlite/linux hardware database for the endless lists of disk data. 4. Added internal dmidecode debugger switches, that makes it much easier to inject test dmidecode data from text files using debugger switches internally. 5. Added -Cxx item, which will run if root and -C are used, now grabs L1 and L3 cache data from dmidecode and shows it. I didn't realize that data was there, not sure how I'd missed it all these years, I guess pinxi really is much easier to work on! This only runs if user has dmidecode permissions from root or sudo.	2018-09-10 15:13:52 -07:00
Harald Hope	e08d828056	pre tag last fix, added -a to trigger --admin, that makes it easier ... for forum output, like: inxi -Fxxxaz	2018-09-07 17:03:27 -07:00
Harald Hope	e78e37a1e1	New version, man page. Fixes, enhancements, changes. ... Thanks: 1. AntiX forums, for testing -C --admin, suggestions, always helpful. Bugs: 1. Added switch to set @ps_gui, I forgot case where info block was only thing that used ps_gui (Nitrux kde nomad latte case). This led to no info: data if other ps_gui switches not activated. Now each block that can use it activates it. Fixes: 1. To clarify issue #161 added help/man explanation on how to get colors in cases where you want to preserve colors for piped or redirected output. Thanks fugo. 2. LMDE 3.0 released, slightly different system base handling, so refactored to add Debian version, see enhancement 2. Tested on some old vm instances, improved old system Debian system base id, but it's empirical, distro by distro, there is no rule I can use to automatically do it, sadly. 3. 'Motherboard' sensors field name added, a few small tweaks to sensors. This was in response to issue #159, which also raised a problem I was not really aware of, user generated sensor config files, that can have totally random field names. Longer term solution, start getting data from sys to pad out lm-sensors data, or to handle cases where no lm-sensors installed. 4. Fixed kwin_11 and kwin_wayland compositor print names, I'd left out the _, which made it look strange, like there were two compositors or something. 5. Fixed latte-dock ID, I thought the program name when running was latte, not latte-dock. inxi checks for both now. Thanks Nitrux for exposing that in vm test. 6. Sensors: added in a small filter to motherboard temp, avoid values that are too high, like SYSTIN: 118 C, filters out to only use < 90 C. Very unlikely a mobo would be more than 90C unless it's a mistake or about to melt. This may correct anoymous debugger dataset report from rakasunka. Enhancements: 1. Added --admin to -v 8 and to --debugger 2x 2. Expanded system base to use Debian version tool, like the ubuntu one, that lets me match version number to codename. The ubuntu one matches code names to release dates. Added Neptune, PureOS, Sparky, Tails, to new Debian system base handler. 3. Big enhancement: --admin -C now shows a nice report on cpu vulnerabilities, and has a good error message if no data found. Report shows: Vulnerabilities: Type: [e.g. meltdown] status/mitigation: text explanation. Note: 'status' is for when no mitigation, either not applicable, or is vulnerable. 'mitigation' is when it's handled, and how. Thanks issue #160 Vascom from Fedora for that request. 4. The never-ending saga of disk vendor IDs continues. More obscure vendors, more matches to existing vendors. Thanks linuxlite/linux hardware database Changes: 1. Reordered usb output, I don't know why I had Hubs and Devices use different ordering and different -x switch priorities, that was silly, and made it hard to read. Now shows: Device/Hub: bus-id-port-id[.port-id]:device-id info: [product info] type/ports: [devices/hubs] usb: [type, speed] -x adds drivers for devices, and usb: speed is now default for devices, same as Hubs. Why I had those different is beyond me. The USB ordering is now more sensible, the various components of each matching whether hub or device. Unfixable or Won't Fix: 1. Unable to detect Nomad desktop. As far as I can tell, Nomad is only a theme applied to KDE Plasma, there is no program by that name detectable, only a reference in ps aux to a theme called nomad. 2. Nitrux system base ID will not work until they correct their /etc/os-release file. 3. Tails live cd for some inexplicable reason uses non standard /etc/os-release field names, which forces me to either do a custom detection just for them, or for them to fix this bug. I opted for ignoring it, if I let each distro break standard formats then try to work around it, the distro ID will grow to be a 1000 lines long easily. Will file distro bug reports when I find these from now on. Samples: This shows the corrected, cleaned up, consistent usb output: inxi -y80 --usb USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0 Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1 Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) type: Audio,HID usb: 1.1 Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse usb: 1.1 Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse usb: 1.1 Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific> usb: 2.0 Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network usb: 2.0 Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1 Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0 Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1 Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0 Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0 inxi -y80 --usb -xxxz USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 usb: 2.0 chip ID: 1d6b:0002 Hub: 1-3:2 info: Atmel 4-Port Hub ports: 4 usb: 1.1 chip ID: 03eb:0902 Device-1: 1-3.2:4 info: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) type: Audio,HID driver: cm109,snd-usb-audio interfaces: 4 usb: 1.1 chip ID: 0d8c:000e Device-2: 1-4:3 info: Wacom Graphire 2 4x5 type: Mouse driver: usbhid,wacom interfaces: 1 usb: 1.1 chip ID: 056a:0011 Device-3: 1-10:5 info: Tangtop HID Keyboard type: Keyboard,Mouse driver: hid-generic,usbhid interfaces: 2 usb: 1.1 chip ID: 0d3d:0001 Device-4: 1-13:7 info: Canon CanoScan LiDE 110 type: <vendor specific> driver: N/A interfaces: 1 usb: 2.0 chip ID: 04a9:1909 Device-5: 1-14:8 info: Apple Ethernet Adapter [A1277] type: Network driver: asix interfaces: 1 usb: 2.0 chip ID: 05ac:1402 serial: <filter> Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 usb: 3.1 chip ID: 1d6b:0003 Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 usb: 2.0 chip ID: 1d6b:0002 Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 usb: 3.1 chip ID: 1d6b:0003 Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 usb: 2.0 chip ID: 1d6b:0002 Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 usb: 3.0 chip ID: 1d6b:0003	2018-09-07 13:58:55 -07:00
Harald Hope	59e988c9e2	man edits	2018-08-28 16:26:41 -07:00
Harald Hope	ae238fb24b	small man page bug fix	2018-08-28 16:20:09 -07:00
Harald Hope	b0392e23ff	New version, man page. Bug fixes, enhancements. ... Bugs: 1. A long standing bug was finally identified and fixed. -n/-i would fail to match a Device to the right IF in cases where they had the same chip / vendor IDs. Added busID for non Soc type devices to fix that. I hope. This fix has been tested on a machine that had this bug, and it is now corrected. Thanks skynet for the dataset. 2. deepin-wm was failing to get listed correctly with new fixes, this is corrected. Fixes: 1. mate version was depending on two tools, mate-about and mate-session, which somewhat randomly vary in which has the actual highest version number. Fix was to run both in MATE for version, and run those through a new version compare tool. Thanks mint/gm10 for reporting that bug. 2. -Gxx compositors: added some missing ones that were being checked for in- correctly. 3. For distro id, fixed a glitch in the parser for files, now correctly removes empty () with or without spaces in it. 4. Got rid of ' SOC?' part of no data for ram or slots, that also triggers in non SOC cases, so best to not guess if I can't get it right. Enhancements: 1. More disk vendor ID matches, also, somehow missed QEMU as vendor, thanks to linux hardware database (linuxlite) for great samples of vendor/product strings. 2. Added a bunch of compositors, found a new source that listed a lot inxi did not have already. 3. Added version v: for some compositors in -Gxxx. 4. New program_data() tool provides an easier to use simple program version/print name generator, including extra level tests, to get rid of some code that repeats. 5. Found some useful QEMU virtual machines for ARM, MIPS, PPC, and SPARC, so made initial debugging for each type, so basic working error free support is well on its way for all 4 architectures, which was unexpected. More fine tunings to all of them to avoid bugs, and to catch more devices, as well. Note that QEMU images are hard to make, and they were not complete in terms of what you would see on physical hardware, so I don't know what features will work or not work, there may be further variants in audio/network/graphics IDs that remain unhandled, new datasets always welcome for such platforms! 6. Found yet another desktop! Added Manokwari support, which is at this point a reworking of gnome, but it was identifiable, minus a version number. 7. Added deepin and blankon to system base supported list, these hide their debian roots, so I had to use the manual method to provide system base.	2018-08-28 15:23:19 -07:00
Harald Hope	c69f9d701b	New version, man page. Big set of changes. Full USB refactor, plus added features. ... Bugs: 1. A result of the issue #156 USB refactor, I discovered that the --usb sort order, which was based on Bus+DeviceID, in fact is wrong, pure and simple. This was exposed by using a second USB hub on a bus, the Device IDs are not really related in any clearly logical way to the actual position on the bus. The solution was to fully refactor the entire USB logic and then use generated alpha sorters based on the full bus-port[.port] ID. Device ID is now printed last in the ID string, like so: 1-4:1. Note that Device IDs start at 1 for each bus, regardless of how many hubs you have attached to that port. 2. Certain situations triggered a bug in Optical devices, I'd forgotten to change $_ to $key in two places. Since that part didn't normally get triggered, I'd never noticed that bug before. Thanks TinyCore for exposing that glitch! Fixes: 1. On legacy systems, fluxbox --version does not work, -v does. Corrected. 2. for --usb, network devices should now show the correct 'type: Network'. For some weird reason, the people who made the usb types didn't seem to consider many key devices, scanners, wifi/ethernet adapters, and those are almost always "Vendor defined class". 3. A really big fix, for instances where system is using only Busybox, like TinyCore, or booting into any system running busybox for whatever reason, now avoids the various errors when using busybox ps, which only for example outputs 3, not 11, default columns for ps aux, and which does not support ps -j, which is used in the start/shell client information. This gets rid of a huge spray of errors, and actually allows for pretty complete output from systems that only have busybox tools installed. This should cover everything from TinyCore to MIPS to ARM systems that run minimalist Linux. Note that this fix goes along with the /sys based USB parser, since such systems may have USB, but are unlikely to have lsusb installed, but do have /sys USB data. 4. In some cases, strings /sbin/init would trigger a false version result, fixed that logic so now it rarely will do that. Enhancements: 1. Added Mosksha desktop, that's a Bodhi fork of Enlightenment E17; added qtile window manager (no version info). 2. Added Bodhi detection; Salix + base slackware; kde neon system base; 3. Added support for slaptget repos, basic, it may not be perfecct. 4. More disk vendors, and matches for existing vendors. 5. Full rewrite of USB data, in --usb, -A, and -N, along with core usb data engines. This makes lsusb optional, though recommended (because it has a better vendor/ product ID to string internal database) than /sys data. This was in response to a second set of issues in #156 by gm10, USB drivers. Depending on the system, using only /sys data, while slightly less informative, is between 20 and 2000 milliseconds faster, so if you want speed, either use the new --usb-sys option, or the configuration file USB_SYS=[true|false] option. 1. switched to cleaner more efficient data structures 2. added ports count to hub report, linux and bsd. 3. added [--usb|-A|-N] -xxx serial for Device items, if present. 4. added --usb -xx drivers, per interface, can be 1 or more drivers. 5. fully refactored -A and -N usb device logic, far cleaner and simple now, much easier to work with, no more hacks to find things and match them. 6. USB type: now comes from /sys, and is in general going to be more accurate than the lsusb -v based method, which was always an ugly and incomplete hack. As with drivers, it also now lists all the interface types found per device, not just the first one as with the previous method. Note that HID means the more verbose: Human Interface Device, but I shortened it. Now that the type: data is created by inxi reading the class/subclass/protocal IDs, and then figuring out what to do itself, I can have quite a bit more flexibility in terms of how type is generated. 7. added --usb -xxx interfaces: [count] for devices, which lists the device interface count. This can be useful to determine if say, a usb/keyboard adapter is a 2 interface device. Note that Audio devices generally have many interfaces, since they do more than 1 thing (audio output, microphone input, etc.). 8. Support for user configuration file item: USB_SYS=[true|false]. This is useful if you want to see only the /sys version of the data, or if you want the significant speed boost not using lsusb offers, particularly on older systems with a complex USB setup, many buses, many devices, etc. New option --usb-tool overrides USB_SYS value, and forces lsusb use. 9. New options: --usb-sys - forces all usb items to use /sys data, and skip lsusb. Note that you still have to use the feature options, like --usb, -A, or -N. This can lead to a significant improvement in execution time for inxi. 10. Rather than the previous bus:device ID string, to go along with the internal sorting strings used, inxi now shows the real Bus / port /port ids, like: 1-3.2.1:3 - Bus-Port[.port]:device id. 6. Added support for Xvesa display server. Thanks for exposing that one, TinyCore! 7. Added tce package manager to repos. That's the tinycore package manager. Changes: 1. big one, after 10 plus years, the venerable 'Card-x:' for -A,-N, and -G has been replaced by the more neutral 'Device-x:'. This was a suggestion by gm10 from Mint in issue #156 This makes sense because for a long time, most of these devices are not cards, they are SOC, motherboard builtin, USB devices, etc, so the one thing they all are are some form of a device, and the one thing that they are all not is a Card. Along with the recent change from HDD: to Local Storage in Disks: this brings inxi terminology out of the ancient times and into the present. Thanks for the nudge gm10. Removed: See inxi-perl/docs/inxi-fragments.txt for removed blocks. 1. Entire parser for lsusb -v, now it all runs either usbdevs or lsusb, and if Linux and not lsusb, it will use /sys exclusively, otherwise it uses /sys data to complete the lsusb vendor/product strings. 2. Two functions that were used by -A and -N to match usb devices and get their /sys data, that became redundant since it all now goes through the /sys parser already, so those features can get the data pre-parsed from the @usb arrays. Output Examples: Sort by DeviceID failures in 3.0.20 using Device ID: inxi --usb USB: Hub: 1:1 usb: 2.0 type: Full speed (or root) hub Device-1: Wacom Graphire 2 4x5 bus ID: 1:2 type: Mouse Device-2: Tangtop HID Keyboard bus ID: 1:3 type: Keyboard Device-3: Verbatim bus ID: 1:11 type: Mass Storage Device-4: Apple Ethernet Adapter [A1277] bus ID: 1:13 type: Vendor Specific Class Hub: 1:85 usb: 1.1 type: Atmel 4-Port Hub Device-5: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) bus ID: 1:86 type: Audio Device-6: Canon CanoScan LiDE 110 bus ID: 1:112 type: Vendor Specific Protocol Device-7: ALi M5621 High-Speed IDE Controller bus ID: 1:113 type: Mass Storage Hub: 2:1 usb: 3.1 type: Full speed (or root) hub Hub: 3:1 usb: 2.0 type: Full speed (or root) hub Hub: 4:1 usb: 3.1 type: Full speed (or root) hub Hub: 5:1 usb: 2.0 type: Full speed (or root) hub Hub: 6:1 usb: 3.0 type: Full speed (or root) hub Corrected: sort by BusID in 3.0.21: inxi --usb USB: Hub: 1-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 14 Hub: 1-3:85 usb: 1.1 type: Atmel 4-Port Hub ports: 4 Device-1: C-Media Audio Adapter (Planet UP-100 Genius G-Talk) type: Audio,HID bus ID: 1-3.2:86 Device-2: ALi M5621 High-Speed IDE Controller type: Mass Storage bus ID: 1-3.4:113 Device-3: Wacom Graphire 2 4x5 type: Mouse bus ID: 1-4:2 Device-4: Verbatim type: Mass Storage bus ID: 1-7:11 Device-5: Tangtop HID Keyboard type: Keyboard,Mouse bus ID: 1-10:3 Device-6: Canon CanoScan LiDE 110 type: <vendor specific> bus ID: 1-13:112 Device-7: Apple Ethernet Adapter [A1277] type: Network bus ID: 1-14:13 Hub: 2-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 8 Hub: 3-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 2 Hub: 4-0:1 usb: 3.1 type: Full speed (or root) Hub ports: 2 Hub: 5-0:1 usb: 2.0 type: Full speed (or root) Hub ports: 4 Hub: 6-0:1 usb: 3.0 type: Full speed (or root) Hub ports: 4	2018-08-17 15:58:44 -07:00