dmitriy.kazimirov/inxi
1
0
Fork 0
mirror of https://github.com/smxi/inxi.git synced 2025-04-25 19:19:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Compare commits

...

16 commits
3.3.28-1 ... master

Author SHA1 Message Date
Harald Hope
15a55d0b94 added gitattritubes 2023-12-05 12:39:25 -08:00
Harald Hope
308f2a97be readme, dumping opencollective in favor of liberapay 2023-11-28 22:37:13 -08:00
Harald Hope
4d6c596ed6 cleaned up code 2023-11-02 21:41:58 -07:00
Harald Hope
8c3b64c74d bug fix, undefined value possible 2023-11-02 20:00:09 -07:00
Harald Hope
bf13ee49a8 small bug, creates out put glitch, but not error 2023-11-02 18:46:12 -07:00
Harald Hope
4b5bdd7114 another nvidia id 2023-10-31 18:32:45 -07:00
Harald Hope
59f25a43f1 changelog, added ubuntu noble 2023-10-31 16:49:05 -07:00
Harald Hope
33a1d1ddbc A small point release, mainly for fixes and bugs, plus a few minor matching 
table updates. Also some core tools updates, which make supporting gpu devices
easier over time, particularly nvidia ones. Also some gpu data updates, new
nvidia 545, which was unexpected, came out, extending the time to next legacy by
some months.

--------------------------------------------------------------------------------
SPECIAL THANKS:

1. GRAPHICS: GPU DATA: codeberg user malcolmlewis who also posted both the first
pinxi issue, and the first codeberg issue. I had not thought nvidia would forget
to add their own device IDs to their lists, but they did. This prompted an
upgrade to the gpu_raw.pl/gpu_ids.pl to better handle manual add files for
Nvidia, as well as better overall consistency for gpu data files and processing.

2. SYSTEM: Wakeups: Mint user senjoz for alerting me to the well done but
unfortunately localized to mint forums report on the wrong wakeup count report,
because the data source was not what I thought it was.

--------------------------------------------------------------------------------
KNOWN ISSUES:

1. Any distro forum person who finds issues related to inxi maybe being wrong or
operating from false assumptions in terms of data sources should ideally find a
way to report these issues directly, either via a codeberg issue, an email, or
something else. It's not possible or practical to track every forum that uses
inxi to debug user issues, so if members of those forums can be more proactive
in terms of sending what appear to be valid issue reports to the inxi project,
that will help a lot.

2. GRAPHICS: GPU: no data for things like Biren and other non AMD/Intel/Nvidia
GPUs. If you are into GPUs, by all means, help us out here!

--------------------------------------------------------------------------------
BUGS:

1. INFO: main::get_wakeups(): I'd say that despite in the past largely being
correct, using /sys/power/wakeup_count is a bug, but a bug that is excusable
because the docs are just too opaque about what this thing actually refers to.
My assumption re its meaning was clearly wrong.

--------------------------------------------------------------------------------
FIXES:

1. INFO: main::get_wakeups(): Issue reported via a Mint forum posting which I
was alerted to.

https://forums.linuxmint.com/viewtopic.php?p=2378107#p2378107

This would have made it into inxi 3.3.30 easily since the patch is changing file
name, but I unfortunetly did not become aware of it until right after the
release, On my system, for example, with systemctl suspend instead of the not
working xfce suspend from gui, I get 7 wakeup_count type events counted for each
suspend event. On another system I have, almost same everything, except fully
functioning xfce suspend feature, the success and wakeup_counts are matched.

I found a value of 49000+ digging through my datasets, and I can find no
pattern, nor can I find this clearly documented, so the behavior is simply going
to be use the value, including 0, from /sys/power/suspend_stats/success and
using it if it is defined, and getting rid of /sys/power/wakeup_count completely
as a data source, which I am now no longer sure at all about the meaning of. 1
of my systems has 7 events per resume, one, almost the same setup, has 1.

2. GRAPHICS: GPU DATA: Many nvidia fixes, device ID lists updated and corrected.

--------------------------------------------------------------------------------
ENHANCEMENTS:

1a. PARTITIONS: added puzzlefs, atomfs to excludes. It's unclear, but both sound
like they are like isofs or something like that.

2a. GRAPHICS: GPU DATA: added Nvidia Pascal, Hopper, Lovelace device IDs. See
Code 1 for fixes to detections. Added AMD, Intel newer GPU IDs, going with Code
1 and GPU data fixes.

2b. GRAPHICS: GPU DATA: updated lists, added Nvidia current EOL data, added
newer kernel/X.org last supported. Added two more memssage types for current,
legacy messages. Found a site that lists EOL for the drivers, that helps.

2c. GRAPHCIS: GPU_DATA: added new 545 driver IDs, updated nv current to 545

--------------------------------------------------------------------------------
CHANGES:

1. DATA: pinxi/tools/lists: made file names consistent for gpu data types.

--------------------------------------------------------------------------------
DOCUMENTATION:

1. DOCS: docs/inxi-graphics.txt, docs/inxi-partitions.txt - ongoing updates for
features. More GPU data added, new file system types.

--------------------------------------------------------------------------------
CODE:

1a. GRAPHICS: GPU DATA: pinxi/tools/gpu_raw.pl, pinxi/tools/gpu_ids.pl. Upgraded
to enable basic manual additions to nvidia drivers. Also fixed detections for
Hopper and Lovelace, those were too tight and I missed some device IDs there.

Redid tools/gpu_raw.pl and gpu_ids.pl to have the more predictable file names.

Also changed the file names to be consistent for nv data in pinxi/tools/lists/
  gpu.[amd|intel].full
  gpu.[amd|intel].full.sorted
  gpu.[amd|intel].manual
  gpu.amd.github
  gpu.intel.com
  gpu.nv.[driver].full
  gpu.nv.[driver].full.sorted
  gpu.nv.[driver].manual
  gpu.nv.[driver].raw

This let me bring all the lists up to date, and some manual fixes added in to
some driver sets.

1b. GRAPHICS: GPU_DATA: pinxi/tools/gpu_ids.pl - updated for Nvidia: new
messages, current eol, filled out legacy drivers with their eol based on last
nvidia driver release date.

2. CORE: there were some pointless globals being used, as part of the overall
effort to get rid of globals where sensible, else move them into hashes/arrays,
makes code easier to maintain long term.
 2023-10-31 15:37:14 -07:00
Harald Hope
bfbda726a4 readme edit 2023-10-18 17:55:28 -07:00
Harald Hope
cb15f8d88a PACKAGERS! inxi repos are moved to https://codeberg.org/smxi/inxi 
The repos will mirror to github for a short amount of time, until after 3.3.30
is released, then I am probably going to do some big changes in the structure of
the inxi repo. Make sure to update your packaging tools and scripts for this
change.

--------------------------------------------------------------------------------

Finally, a huge upgrade for Wayland future proofing, and other futures that are
maybe coming, by adding EGL API, and Vulkan for good measure. This should handle
wayland finally, that's been a stub forever, but finally realized eglinfo was a
thing, and that vulkan as well could be a contender to replace OpenGL, at least
that's what Mesa says on their site, and they should know.

This handles one of the longest standing weak points of inxi graphics, being
completely X11-centric, even though wayland support exists fairly extensively,
but this glxinfo dependent feature was a niggling annoyance, now it's fairly
ambivalent about which api tool you throw at it, the hardest is to give the
right message for no data, or incomplete data. Note that eglinfo supplies at
least software rendering out of X11 or Wayland, so we can now get some API data
in console, including if supported, OpenGL data. Not all of it, but some of it.

Also since now all the docs are split and granular, with the Graphics API
upgrades, added data sample files from glxinfo, eglinfo, vulkaninfo, and vainfo
for good measure, just to have some of the latter. This is one of the first time
all the data used to develope a feature, docs for that feature, and the feature
itself, are being shared and released at the same time.

--------------------------------------------------------------------------------
SPECIAL THANKS:

1a. GRAPHICS: API: Arch user Chrome30 on github for requesting vulkan data, and
providing the initial datasamples that made it possible to think about this new
API feature.

1b. CheckRecommends: Display packages: mrmazda, a frequent helper, checked and
updated OpenSUSE and Fedora vulkan/egl/glx API tool package names. Those have
been a bit fluid and many of the names I had were not right.

--------------------------------------------------------------------------------
KNOWN ISSUES:

1a. GRAPHICS: nothing is perfect, for sudo/root the detections fail for OpenGL
API messages, but fallbacks will make it a bit nicer than it was, with some
data, instead of none as before.

1b. GRAPHICS: API: I'm assuming that the greatest EGL version number found is
the actual version, and lower versions are what that platform supports. This is
an assumption, not a known fact, but finding this stuff clearly documented tends
towards near impossibility, or takes forever to determine, so that's the
assumption that is being used. Correct via issue and clear explanation with
links to resources if this is incorrect.

--------------------------------------------------------------------------------
BUGS:

1. Nothing to speak of.

--------------------------------------------------------------------------------
FIXES:

1. PARTITIONS: had wekafs as a zfs type fs, it's not, it's more like NAS, cloud.
Added to distributed list, and removed from zfs|btrfs|hammer list. I know, I
know, will it ever matter? Probably not. But just in case, wouldn't want your
local machine to report with petabytes of storage now would we!

2. CheckRecommends: corrected some Fedora, SUSE package names.

--------------------------------------------------------------------------------
ENHANCEMENTS:

1a. SYSTEM: DistroData: added Bodhi id method, /etc/bodhi/info file which is
similar to /etc/lsb_release, updated system base detection as well. System base
comes from /etc/os-release.

1b. SYSTEM: DistroData: Added Nitrux system base (debian). Why they try hide
this is beyond me. Maybe because they are not using a real PM, and don't include
apt, who knows.

2a. GRAPHICS: new nvidia gpu ids.

2b. Graphics: EGL API data:
* Shows eglinfo missing if appropriate, no data messages if appropriate.
* -G shows EGL version(s), drivers, active platforms.
* -Gx adds active/inactive platforms as sub items of platforms.
* -Gxx shows platforms by platform, with egl version, driver. EGL version only
shows if there were more than 1 detected, otherwise it shows with EGL v:
* -Gxxx shows hw based on driver, if found, like vulkan.

To avoid excess verbosity, does not show renderer OpenGL name per platform
because it would be way too long and repetetive. And besides, that would show
in OpenGL anyway, more or less, unless there are two different GPUs, which is a
case that is not fully handled.

2c. GRAPHICS: OpenGL data:
* If glxinfo not present, or with null output due to root/no display, and if
eglinfo available, and has OpenGL items, will populate most of OpenGL API with
data, except for Direct Rendering and GLX version. Shows appropriate messages
indicating it's EGL sourced for console, root, no data, or glxinfo missing.
* -Gx adds GLX version, if detected.
* -Gxx add: ES version, if detected; device-ID, if available. Also adds
display-ID, if Display-ID was not found in the Display line (which probably
means that xdpyinfo or xrandr were not installed). Does not always show since it
already appeared in Display line if it was discovered.
* -Ga adds device memory, and unified memory status (yes/no).

2d. GRAPHICS: Vulkan API data:
* Shows appropriate messages if vulkaninfo present, but no data found.
* -G shows Vulkan version, drivers, and surfaces.
* -Gx device counts.
* -Gxx adds device by id, type, driver report.
* -Gxxx adds layer count; adds device hardware vendor, based on mesa driver. Not
for nvidia driver, since that is self evident. Goes away with -Ga if device name
exists.
* -Ga adds full device report, including per device names, ids, drivers, driver
versions, surfaces.

3. UPDATE: Because the smxi.org server no longer accepts TSL 1.1 based HTTP
requests, added for extreme legacy systems a new update option, -U 4, which
uses direct FTP download from smxi.org ftp server. If system set to default to
perl downloader HTTP::Tiny it switches to using a non perl downloader
automatically, like wget or curl.

4. CPU: Microarch: got early zen5 possible IDs. Both Intel/AMD may have rough
ID working well before they ship in public. CPU stuff has slowed down a lot,
the 4,3n nodes are not easy, obviously.

5. DRIVES: Many more drive vendors and drive IDs.

6. RAM: More RAM vendors. Note that it's not unusual for a Drive vendor to also
make RAM, and vice versa.

--------------------------------------------------------------------------------
CHANGES:

1a. GRAPHICS: For API, show OpenGL mesa-v: x.x.x separate from main API v:
string. Also only shows the actual API version with v: now, like v: 4.5. Also
shows vendor: nvidia v: 340.23 for nvidia, without mesa. Falls back for
unhandled cases or syntaxes to the whole version string for v:.

1b. GRAPHICS: For OpenGL, shows compat-v: always if present, that was a mistake
not to show it unless -Gx, since otherwise you'd think you are running a
different version. Not a common situation, but on legacy hardware, can happen.

--------------------------------------------------------------------------------
DOCUMENTATION:

1a. DOCS: docs/inxi-cpu.txt - reorganized into more coherent sections, like with
like, etc. Added better top Sections navigation since there is so much data.

1b. DOCS: docs/inxi-resources.txt - moved last code tricks to
docs/tips-tricks.txt.

1c. DOCS: new docs/ files inxi-battery.txt, inxi-debuggers.txt,
inxi-devices.txt, inxi-kernel.txt, inxi-machine.txt, inxi-network.txt,
inxi-raid-logical.txt, inxi-start-client.txt, inxi-tty.txt, inxi-weather.

These new files cleaned out docs/inxi-data.txt and docs/inxi-resources.txt,
which are now merely placeholder files, and have no data in them beyond pointers
to the actual data files.

1d. DOCS: docs/inxi-custom-recommends.txt updated for SUSE/Fedora packag name
fixes and new eglinfo and vulkaninfo items.

2a. DATA: moved more data from non public data to shared. Refactored directories
to be better organized, and to follow the overall inxi data structures better.

2b. DATA: added many more eglinfo, glxinfo, vulkaninfo to data/graphics. Also
added some clinfo, vainfo just in case decide to support those APIs.

3a. MAN/OPTIONS: updated for new graphics API features, new verbsity features,
etc.

3b. MAN/OPTIONS: added -U arguments for man, for some reason I'd left those out.
Also removed options references to -U 1, 2, because those should never be used,
if those versions of inxi even exist, they are ancient. Added -U 4 option, and
explanation of when/why to use it.

--------------------------------------------------------------------------------
CODE:

1a. FAKE DATA: updated paths for fake data to reflect data reorganization.

1b. FAKE DATA: Added --fake egl,glx,vulkan for GRAPHICS API.

2. GRAPHICS: Fully refactored opengl_output, moved to gl_data/opengl_output.
Added egl_data, egl_output, and vulkan_data, vulkan_output, and some other
tools.

3. UPDATE: if downloader is set to 'perl', aka, Tiny::HTTP, and -U 4 is used,
which is a direct FTP download of the inxi/pinxi files, tiny is disabled, and
the next available downloader (wget/curl/fetch) is used instead.

4. DEBUGGER: added clinfo, eglinfo, es2_info, vainfo, vdpauinfo, vulkaninfo.
 2023-09-25 15:11:51 -07:00
Harald Hope
8fd8708bd3 readme update 2023-09-18 14:27:00 -07:00
Harald Hope
8bf3bae552 redme update 2023-09-17 21:20:49 -07:00
Harald Hope
089766b34e typo fix 2023-09-17 17:46:15 -07:00
Harald Hope
71cfe887a3 Updated for change to codeberg.org from github, updated readme, 
added a short term patch version so the master inxi has the right
urls in it.
 2023-09-17 17:42:36 -07:00
Harald Hope
209b979f1f Added TLS removal notice for inxi/pinxi install on README.txt 2023-09-13 19:15:33 -07:00
Harald Hope
9cca058f5d Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB 
network devices, and possibly some other USB device types. Also some nice new
features.

--------------------------------------------------------------------------------
SPECIAL THANKS:

1. SYSTEM: Github user chromer030 in issue  - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.

2. BLUETOOTH: Github user chromer030, issue  - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.

3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.

4. SWAP: Github user chromer030, again, issue  suggested some swap
zram/zswap data enhancements, seems good, so thanks.

5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.

6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.

--------------------------------------------------------------------------------
KNOWN ISSUES:

1. Nothing new.

--------------------------------------------------------------------------------
BUGS:

1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.

2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.

3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.

3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.

4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.

--------------------------------------------------------------------------------
FIXES:

1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.

1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.

1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.

2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.

3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.

4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.

--------------------------------------------------------------------------------
ENHANCEMENTS:

1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.

2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.

3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.

4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt

4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html

--------------------------------------------------------------------------------
CHANGES:

1. None that are obvious.

--------------------------------------------------------------------------------
DOCUMENTATION:

1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.

2a. DOCS: Made new docs/inxi-bluetooth.txt doc.

2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.

2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.

3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.

3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.

3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.

3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.

--------------------------------------------------------------------------------
CODE:

1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.

2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.

3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.

I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.

4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.

5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.

6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.

7. IpData: got rid of extra array copies for push, pointless.
 2023-08-15 20:07:26 -07:00
5 changed files with 2720 additions and 764 deletions

1
.gitattributes vendored Normal file
View file

@ -0,0 +1 @@
inxi linguist-language=Perl

162
README.txt
View file

@ -8,6 +8,46 @@ issue reports. The code in pre 2.9 versions literally no longer exists in inxi
3. Bugs from earlier versions cannot usually be solved in the new version since
the pre 2.9 and the 2.9 and later versions are completely different internally.
--------------------------------------------------------------------------------
CODEBERG SOURCE REPO
--------------------------------------------------------------------------------
Packagers: Make sure to change your package URLs and repos to use codeberg.org.
The previous inxi-perl, tarballs, and docs branches are now standalone repos
on codeberg.org:
docs > https://codeberg.org/smxi/inxi-docs master
inxi-perl > https://codeberg.org/smxi/pinxi master
master > https://codeberg.org/smxi/inxi master
tarballs > https://codeberg.org/smxi/inxi-tarballs master
inxi-perl has been rebuilt and now only contains the pinxi, pinxi.1 files, plus
a minimal README.txt for github users. docs and tarballs have been deleted. The
inxi-perl branch should not be used, and exists only so that current pinxi users
can update from there to get the new version with new URLs.
inxi master and inxi-perl/pinxi will be mirrored until late 2023, then they will
no longer get updates.
The inxi repo only contains master, plus the one, two branches, which are
obsolete.
--------------------------------------------------------------------------------
Please file issue reports or feature requests at:
https://codeberg.org/smxi/inxi
Please take the time to read this helpful article from the Software Freedom
Conservancy:
https://sfconservancy.org/GiveUpGitHub/
Any use of this project's code by GitHub Copilot, past or present, is done
without my permission. I do not consent to GitHub's use of this project's code
in Copilot.
--------------------------------------------------------------------------------
DONATE
--------------------------------------------------------------------------------
@ -16,7 +56,7 @@ Help support the project with a one time or a sustaining donation.
Paypal: https://www.paypal.com/donate/?hosted_button_id=77DQVM6A4L5E2
Open Collective: https://opencollective.com/inxi
LiberaPay (sustaining donations): https://liberapay.com/smxi/
================================================================================
DEVELOPMENT AND ISSUES
@ -68,32 +108,41 @@ See BSD/UNIX below for qualifications re BSDs, and OSX in particular.
SOURCE VERSION CONTROL
--------------------------------------------------------------------------------
https://github.com/smxi/inxi
inxi:
REPO: https://codeberg.org/smxi/inxi
MAIN BRANCH: master
DEVELOPMENT BRANCHES: inxi-perl, one, two
DEVELOPMENT BRANCHES [not used]: one, two
inxi-perl is the dev branch, the others are rarely if ever used. inxi itself has
the built in feature to be able to update itself from anywhere, including these
branches, which is very useful for development and debugging on various user
systems.
pinxi [development version for inxi]:
REPO: https://codeberg.org/smxi/pinxi
MAIN BRANCH: master
pinxi is the standalone development version of inxi. inxi branches one, two are
rarely if ever used. inxi has the built in feature to be able to update itself
from anywhere, including these branches, which is very useful for development
and debugging on various user systems.
Please: NEVER even think about looking at or using previous inxi commits,
previous to the current master version, as a base for a patch. If you do, your
patch / pull request will probably be rejected.
PULL REQUESTS: Please talk to me before starting to work on patches of any
reasonable complexity. inxi is hard to work on, and you have to understand how
it works before submitting patches, unless it's a trivial bug fix. Please: NEVER
even think about looking at or using previous inxi commits, previous to the
current master version, as a base for a patch. If you do, your patch / pull
request will probably be rejected. Developers, get your version from the
inxi-perl branch, pinxi, otherwise you may not be current to actual development
versions. inxi-perl pinxi is always equal to or ahead of master branch inxi.
it works before submitting patches, unless it's a trivial bug fix. Never work
with inxi master, always work with pinxi master, since it can be quite far ahead
of inxi. inxi master has only one purpose, to get updated to next inxi when
pinxi is ready to be copied over to inxi. pinxi is always equal to or ahead of
master branch inxi.
Man page updates, doc page updates, etc, of course, are easy and will probably
Man page updates, doc pages updates, etc, of course, are easy and will probably
be accepted, as long as they are properly formatted and logically coherent.
When under active development, inxi releases early, and releases often.
When under active development, pinxi releases early, and releases often. inxi
is stable and is generally only updated when a new tagged version is completed.
PACKAGERS: inxi has one and only one 'release', and that is the current
commit/version in the master branch (plus pinxi inxi-perl branch, of course, but
those should never be packaged).
PACKAGERS: inxi has one and only one 'release', and that is the current tagged
version in the master branch (plus pinxi repo, of course, but pinxi should in
general not be packaged).
--------------------------------------------------------------------------------
MASTER BRANCH
@ -103,48 +152,66 @@ This is the only supported branch, and the current latest commit/version is the
only supported 'release'. There are no 'releases' of inxi beyond the current
commit/version in master. All past versions are not supported.
git clone https://github.com/smxi/inxi --branch master --single-branch
git clone https://codeberg.org/smxi/inxi --branch master --single-branch
OR direct fast and easy install:
wget -O inxi https://github.com/smxi/inxi/raw/master/inxi
wget -O inxi https://codeberg.org/smxi/inxi/raw/master/inxi
OR easy to remember shortcut (which redirects to github):
OR easy to remember shortcut (which redirects to codeberg.org):
wget -O inxi https://smxi.org/inxi
wget -O inxi smxi.org/inxi
NOTE: Just because github calls tagged commits 'Releases' does not mean they are
releases! I can't change the words on the tag page. They are tagged commits,
period. A tag is a pointer to a commit, and has no further meaning.
NOTE: There are no 'Releases' per se. There are only tagged commits, period. A
tag is a pointer to a commit, and has no further meaning. A tagged commit
however is the target for packagers.
If your distribution has blocked -U self updater and you want a newer version:
Open /etc/inxi.conf and change false to true: B_ALLOW_UPDATE=true
--------------------------------------------------------------------------------
DEVELOPMENT BRANCH
SPECIAL NOTE FOR LEGACY OPERATING SYSTEMS WITH NO TLS 1.2 OR GREATER: Modern web
servers are dropping support for TLS 1.0, 1.1, and so has smxi.org, this means
to install inxi onto an older system with only TLS 1.0 or 1.1 available, you
will need to do this to install inxi onto the old system:
wget -O /usr/local/bin/inxi ftp://ftp.smxi.org/outgoing/inxi
then update inxi/man pages after that with inxi -U 4, which uses FTP, not HTTP,
to download the file.
For pinxi, just change inxi to pinxi above (add --man to get the man page), and
it will work the same.
--------------------------------------------------------------------------------
DEVELOPMENT VERSION (in pinxi repo)
--------------------------------------------------------------------------------
All active development is now done on the inxi-perl branch (pinxi):
All active development is done in the pinxi repo master branch.:
git clone https://github.com/smxi/inxi --branch inxi-perl --single-branch
git clone https://codeberg.org/smxi/pinxi
OR direct fast and easy install:
wget -O pinxi https://github.com/smxi/inxi/raw/inxi-perl/pinxi
wget -O pinxi https://codeberg.org/smxi/pinxi/raw/master/pinxi
OR easy to remember shortcut (which redirects to github):
OR easy to remember shortcut (which redirects to codeberg.org):
wget -O pinxi https://smxi.org/pinxi
wget -O pinxi smxi.org/pinxi
Once new features have been debugged, tested, and are reasonably stable, pinxi
is copied to inxi in the master branch.
is copied to inxi in the inxi master branch.
It's a good idea to check with pinxi if you want to make sure your issue has not
been corrected, since pinxi is always equal to or ahead of inxi.
See SPECIAL NOTE FOR LEGACY OPERATING SYSTEMS above to install pinxi on very old
operating systems with out of date TLS version.
--------------------------------------------------------------------------------
LEGACY INXI (in inxi-legacy repo)
--------------------------------------------------------------------------------
@ -154,9 +221,9 @@ inxi-legacy repo, as binxi in the /inxi-legacy directory:
Direct fast and easy install:
wget -O binxi https://github.com/smxi/inxi-legacy/raw/master/inxi-legacy/binxi
wget -O binxi https://codeberg.org/smxi/inxi-legacy/raw/master/binxi
OR easy to remember shortcut (which redirects to github):
OR easy to remember shortcut (which redirects to codeberg.org):
wget -O binxi https://smxi.org/binxi
@ -182,9 +249,9 @@ DOCUMENTATION
https://smxi.org/docs/inxi.htm
(smxi.org/docs/ is easier to remember, and is one click away from inxi.htm). The
one page wiki on github is only a pointer to the real resources.
one page wiki on codeberg.org is only a pointer to the real resources.
https://github.com/smxi/inxi/tree/inxi-perl/docs
https://codeberg.org/smxi/pinxi/src/branch/master/docs
Contains specific Perl inxi documentation, of interest mostly to developers.
Includes internal inxi tools, values, configuration items. Also has useful
@ -200,27 +267,30 @@ NOTE: Check the inxi version number on each doc page to see which version will
support the options listed. The man and options page also link to a legacy
version, pre 2.9.
https://github.com/smxi/inxi/wiki
https://codeberg.org/smxi/inxi/wiki
This is simply a page with links to actual inxi resources, which can be useful
for developers and people with technical questions. No attempt will be made
to reproduce those external resources here on github. You'll find stuff like
for developers and people with technical questions. No attempt will be made to
reproduce those external resources on codeberg.org. You'll find stuff like
how to export to json/xml there, and basic core philosophies, etc.
--------------------------------------------------------------------------------
IRC
--------------------------------------------------------------------------------
You can go to: irc.oftc.net or irc.libera.chat channel #smxi
You can go to:
irc.oftc.net or irc.libera.chat channel #smxi
but be prepared to wait around for a while to get a response. Generally it's
better to use github issues.
better to use codeberg.org issues.
--------------------------------------------------------------------------------
ISSUES
--------------------------------------------------------------------------------
https://github.com/smxi/inxi/issues
https://codeberg.org/smxi/inxi/issues
No issues accepted for non current inxi versions. See below for more on that.
Unfortunately as of 2.9, no support or issues can be accepted for older inxi's
because inxi 2.9 (Perl) and newer is a full rewrite, and legacy inxi is not
@ -317,10 +387,14 @@ SUPPORTED VERSIONS / DISTRO VERSIONS
Important: the only version of inxi that is supported is the latest current
master branch version/commit. No issue reports or bug reports will be accepted
for anything other than current master branch. No merges, attempts to patch old
code from old versions, will be considered or accepted. If you are not updated
to the latest inxi, do not file a bug report since it's probably been fixed ages
ago. If your distro isn't packaging a current inxi, then file a bug report with
your packager, not here.
code from old versions, will be considered or accepted on the master branch of
inxi. If you are not updated to the latest inxi, do not file a bug report since
it's probably been fixed ages ago. If your distro isn't packaging a current
inxi, then file a bug report with your packager, not here.
The development branch inxi-perl/pinxi has been moved to its own standalone
repo, pinxi, at https://codeberg.org/smxi/pinxi - this is the only place
development happens.
inxi is 'rolling release' software, just like Debian Sid, Gentoo, or Arch Linux
are rolling release GNU/Linux distributions, with no 'release points'.

2555
inxi
View file

File diff suppressed because it is too large Load diff

203
inxi.1
View file

@ -15,7 +15,7 @@
.\" with this program; if not, write to the Free Software Foundation, Inc.,
.\" 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
.\"
.TH INXI 1 "2023\-07\-10" "inxi" "inxi manual"
.TH INXI 1 "2023\-10\-31" "inxi" "inxi manual"
.SH NAME
inxi \- Command line system information script for console and IRC
@ -278,9 +278,9 @@ for many more features.
.TP
.B \-E\fR, \fB\-\-bluetooth\fR
Show bluetooth device(s), drivers. Show \fBReport:\fR with HCI ID, state,
address per device (requires \fBbt\-adapter\fR or \fBhciconfig\fR),
and if available (hciconfig only) bluetooth version (\fBbt\-v\fR).
See \fBExtra Data Options\fR for more.
address per device (requires \fBbtmgmt\fR, \fBbt\-adapter\fR, or
\fBhciconfig\fR), and if available (hciconfig, btmgmt only) bluetooth version
(\fBbt\-v\fR). See \fBExtra Data Options\fR for more.
If bluetooth shows as \fBstatus: down\fR, shows \fBbt\-service:\fR\fB state
and rfkill\fR software and hardware blocked states, and rfkill ID.
@ -357,10 +357,11 @@ If protocol is not detected, shows:
Adds \fBwith: Xwayland v:...\fR if xwayland server is installed, regardless of
protocol.
Also shows screen resolution(s) (per monitor/X screen). Shows graphics API used,
like OpenGL. For X.org: OpenGL renderer, OpenGL core profile version/OpenGL
version; for VESA: data (for Xvesa); for Wayland: GBM/EGL data (not
implemented).
Also shows screen resolution(s) (per monitor/X screen). Shows graphics API
information (if available). EGL: EGL version, drivers, acdtive platforms;
OpenGL: renderer, OpenGL core profile version/OpenGL version (if core/compat
versions different, shows that as well); Vulkan: Vulkan version, drivers,
surfaces;VESA: data (for Xvesa).
Compositor information will show if detected using \fB\-xx\fR option or always
if detected and Wayland since the compositor is the server with Wayland.
@ -697,8 +698,8 @@ Show distro repository data. Currently supported repo types:
\fBAPK\fR (Alpine Linux + derived versions)
\fBAPT\fR (Debian, Ubuntu + derived versions, as well as RPM based
APT distros like PCLinuxOS or Alt\-Linux)
\fBAPT\fR (Debian, Ubuntu + derived versions, as well as rpm based
apt distros like PCLinuxOS or Alt\-Linux)
\fBCARDS\fR (NuTyX + derived versions)
@ -840,14 +841,36 @@ Note \- Maintainer may have disabled this function.
If inxi \fB\-h\fR has no listing for \fB\-U\fR then it's disabled.
Auto\-update script. Note: if you installed as root, you must be root to
update, otherwise user is fine. Also installs / updates this man page to:
Auto\-update inxi or pinxi. Note: if you installed as root, you must be root to
update, otherwise user is fine. Also installs / updates current man page to:
\fB/usr/local/share/man/man1\fR (if \fB/usr/local/share/man/\fR exists
AND there is no inxi man page in \fB/usr/share/man/man1\fR, otherwise it
goes to \fB/usr/share/man/man1\fR). This requires that you be root to write
to that directory. See \fB\-\-man\fR or \fB\-\-no\-man\fR to force or disable
man install.
\fB\-U\fR accepts the following options (inxi and pinxi):
No arg \- Get from main git branch.
3 \- Get the dev server (smxi.org) version. Be aware that pinxi when taken from
here can be very unstable during active development! The inxi version is the
stable master branch version. Also useful to update if you have SSL issues and
\fB\-\-no\-ssl\fR works.
4 \- Get the dev server (smxi.org) FTP version (same as 3 version). Use if SSL
issues and \fB\-\-no\-ssl\fR doesn't work. For very old systems with SSL 1, you
will probably need to use this option, which bypasses HTTP downloading, and uses
straight FTP to get the file from smxi.org server.
[http|https|ftp] \- Get a version of $self_name from your own server. Use the
full download path, e.g.
\fB\inxi -U ^https://myserver.com/inxi\fR
For failed downloads, use the debug option \fB\-\-dbg 1\fR in addition to get
more verbose failure reports.
.TP
.B \-\-usb\fR
.br
@ -1358,9 +1381,9 @@ specific vendor [product] information.
\- Adds driver version (if available) for each device.
\- Adds (if available, and \fBhciconfig\fR only) LMP (HCI if no LMP data,
and HCI if HCI/LMP versions are different) version (if available)
for each HCI ID.
\- Adds (if available, \fBbtmgmt\fR, \fBhciconfig\fR only) LMP (HCI if no LMP
data, and HCI if HCI/LMP versions are different) version (if available) for each
HCI ID.
.TP
.B \-x \-G\fR
@ -1371,13 +1394,17 @@ for each HCI ID.
\- Adds (if available and/or relevant) \fBvendor:\fR item, which shows
specific vendor [product] information.
\- \fBX.org:\fR Adds direct rendering status.
\- \fBX.org:\fR Adds (for single GPU, nvidia driver) screen number that GPU is
running on.
\- Adds device temperature for each discrete device (Linux only).
\- For EGL, adds active/inactive platform report.
\- For OpenGL (\fBX.org\fR only) adds direct render status, GLX version.
\- For Vulkan, adds device count.
.TP
.B \-x \-i\fR
\- Adds IP v6 additional scope data, like Global, Site, Temporary for
@ -1555,14 +1582,14 @@ For a PCIe 3 NVMe drive, with speed of \fB8 GT/s\fR and \fB4\fR lanes
.B \-xx \-E\fR (\fB\-\-bluetooth\fR)
\- Adds vendor:product ID of each device.
\- Adds (\fBhciconfig \fRonly) LMP subversion (and/or HCI revision
if applicable) for each device.
\- Adds PCIe speed and lanes item (Linux only, and if PCIe bluetooth, which is
rare).
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
\- Adds (\fBhciconfig \fRonly) LMP subversion (and/or HCI revision if
applicable) for each device.
.TP
.B \-xx \-G\fR
Triggers much more complete Screen/Monitor output.
@ -1653,11 +1680,15 @@ grid of monitors that the \fBXorg\fR \fBScreen\fR is composed of.
real monitor size, not the Xorg full Screen diagonal size, which can be quite
different.
\- For free drivers, adds OpenGL compatibility version number if available. For
nonfree drivers, the core version and compatibility versions are usually the
same. Example:
\- For EGL, shows platform by specific platforms, with driver and egl version if
different from the main one.
\fBv: 3.3 Mesa 11.2.0 compat\-v: 3.0\fR
\- For OpenGL, adds ES version (\fBes\-v\fR) if available. If the Display line
did not find an X11 display ID, the ID (e.g. \fB:0.0\fR) will show here instead.
\- For OpenGL, Vulkan, adds \fBdevice-\ID\fR, if available.
\- For Vulkan, adds per Device ID report (type, driver, device\-ID).
.TP
.B \-xx \-I\fR
@ -1818,6 +1849,8 @@ are spinning, no rpm data will show.
.B \-xxx \-E\fR (\fB\-\-bluetooth\fR)
\- Adds, if present, PCI/USB class ID.
\- Adds, if present, bluetooth device class ID.
\- Adds (\fBhciconfig \fRonly) HCI version, revision.
.TP
@ -1845,6 +1878,12 @@ right.
\- \fBWayland:\fR Adds to Monitors \fBscale:\fR (if detected).
\- For EGL, shows hardware based driver(s) (\fBhw:\fR), with the related
hardware, like AMD or Intel.
\- For Vulkan, adds layer count, per device driver hardware vendor (not
displayed if device name is present with \fB\-a\fR).
.TP
.B \-xxx \-I\fR
\- For \fBUptime:\fR adds \fBwakeups:\fR to show how many times the machine
@ -1908,6 +1947,8 @@ RAID events)
.TP
.B \-xxx \-S\fR
\- Adds current kernel clock source, if available (Linux only).
\- Adds, if in X, or with \fB--display\fR, bar/dock/panel/tray items
(\fBinfo\fR). If none found, shows nothing. Supports desktop items like
gnome\-panel, lxpanel, xfce4\-panel, lxqt\-panel, tint2, cairo-dock, trayer,
@ -2141,6 +2182,9 @@ shown. Bluetooth PCIe rare).
\- Adds for USB devices USB mode (Linux only).
\- Adds, if present, bluetooth \fBstatus:\fR discoverable, active discoverable,
and pairing items.
.TP
.B \-a \-G\fR
\- Adds, if present, possible \fBalternate:\fR kernel modules capable of driving
@ -2211,36 +2255,50 @@ shown).
\- Adds to Monitors \fBbuilt:\fR, \fBgamma:\fR, \fBratio:\fR (if found).
\- Adds to OpenGL device memory and unified status, if present.
\- Adds to Vulkan full device report, with full device names, ids, drivers,
driver versions, surfaces.
X.org sample (with both \fBxdpyinfo\fR and \fBxrandr\fR data available):
.nf
\fBinxi \-aGz
Graphics:
Device\-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
driver: radeon v: kernel alternate: amdgpu arch: TeraScale\-2
code: Evergreen process: TSMC 32\-40nm built: 2009\-15 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link\-max: gen: 2 speed: 5 GT/s ports:
active: DVI\-I\-1,VGA\-1 empty: HDMI\-A\-1 bus\-ID: 0a:00.0
chip\-ID: 1002:68f9 class\-ID: 0300
Display: x11 server: X.Org v: 1.21.1.3 with: Xwayland v: 22.1.0
compositor: xfwm v: 4.16.1 driver: X: loaded: modesetting dri: r600
Device\-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series]
vendor: XFX Pine driver: radeon v: kernel alternate: amdgpu
arch: TeraScale\-2 code: Evergreen process: TSMC 32\-40nm
built: 2009\-15 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link\-max:
gen: 2 speed: 5 GT/s ports: active: DVI\-I\-1,VGA\-1 empty: HDMI\-A\-1
bus\-ID: 0a:00.0 chip\-ID: 1002:68f9 class\-ID: 0300 temp: 58.0 C
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9
compositor: xfwm v: 4.18.0 driver: X: loaded: modesetting dri: r600
gpu: radeon display\-ID: :0.0 screens: 1
Screen\-1: 0 s-res: 2560x1024 s-dpi: 96 s\-size: 677x270mm (26.65x10.63")
s\-diag: 729mm (28.7")
Screen\-1: 0 s\-res: 2560x1024 s\-dpi: 96
s\-size: 677x270mm (26.65x10.63") s\-diag: 729mm (28.7")
Monitor\-1: DVI\-I\-1 pos: primary,left model: Samsung SyncMaster
serial: <filter> built: 2004 res: 1280x1024 hz: 60 dpi: 96 gamma: 1.2
size: 338x270mm (13.31x10.63") diag: 433mm (17") ratio: 5:4 modes:
max: 1280x1024 min: 720x400
Monitor\-2: VGA\-1 pos: right model: Dell 1908FP serial: <filter>
built: 2008 res: 1280x1024 hz: 60 dpi: 86 gamma: 1.4
size: 376x301mm (14.8x11.85") diag: 482mm (19") ratio: 5:4 modes:
max: 1280x1024 min: 720x400
API: OpenGL renderer: AMD CEDAR (DRM 2.50.0 / 5.16.0-11.1\-liquorix-amd64 LLVM
12.0.1) v: 3.3 Mesa 21.2.6 compat\-v: 3.1 direct-render: Yes
....\fR
serial: H9NX842662 built: 2004 res: 1280x1024 hz: 60 dpi: 96
gamma: 1.2 size: 338x270mm (13.31x10.63") diag: 433mm (17")
ratio: 5:4 modes: max: 1280x1024 min: 720x400
Monitor\-2: VGA\-1 pos: right model: Dell 1908FP
serial: G434H87HRA2D built: 2008 res: 1280x1024 hz: 60 dpi: 86
gamma: 1.4 size: 376x301mm (14.8x11.85") diag: 482mm (19")
ratio: 5:4 modes: max: 1280x1024 min: 720x400
API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600
device: 1 drv: swrast gbm: egl: 1.4 drv: kms_swrast surfaceless:
drv: r600 x11: drv: r600 inactive: wayland
API: OpenGL v: 4.5 vendor: x.org mesa v: 22.3.6 glx\-v: 1.4
es\-v: 3.1 direct\-render: yes renderer: AMD CEDAR (DRM 2.50.0 /
6.4.3\-1\-liquorix\-amd64 LLVM 15.0.6) device\-ID: 1002:68f9
memory: 1000 MiB unified: no
API: Vulkan v: 1.3.250 layers: 3 device: 0 type: cpu
name: llvmpipe (LLVM 15.0.6 256 bits) driver: mesa llvmpipe
v: 22.3.6 (LLVM 15.0.6) device\-ID: 10005:0000 surfaces: xcb,xlib\fR
.fi
Wayland sample, with Sway/swaymsg:
.nf
\fBinxi \-aGz
\fB
inxi \-aGz
Graphics:
Device\-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
driver: radeon v: kernel alternate: amdgpu arch: TeraScale 2
@ -2248,7 +2306,7 @@ Graphics:
gen: 2 speed: 5 GT/s ports: active: DVI\-I\-1,VGA\-1 empty: HDMI\-A\-1
bus\-ID: 0a:00.0 chip\-ID: 1002:68f9 class\-ID: 0300
Display: wayland server: Xwayland v: 21.1.4 compositor: sway v: 1.6.1
driver: gpu: radeon d\-rect: 2560x1024
driver: dri: r600 gpu: radeon d\-rect: 2560x1024
Monitor-1: DVI\-I\-1 pos: right model: SyncMaster serial: <filter>
built: 2004 res: 1280x1024 hz: 60 dpi: 96 gamma: 1.2
size: 340x270mm (13.4x10.6") diag: 434mm (17.1") ratio: 5:4 modes:
@ -2257,8 +2315,12 @@ Graphics:
res: 1280x1024 hz: 60 gamma: 1.4 dpi: 86 gamma: 1.4
size: 380x300mm (15.0x11.8") diag: 484mm (19.1") ratio: 5:4 modes:
max: 1280x1024 min: 720x400
API: GBM/EGL
Message: Wayland GBM/EGL data currently not available.
API: OpenGL v: 4.6 compat\-v: 4.5 vendor: x.org mesa v: 22.3.6
glx\-v: 1.4 direct\-render: yes renderer: AMD CEDAR (DRM 2.50.0 /
6.4.3\-1\-liquorix\-amd64 LLVM 15.0.6) device\-ID: 1002:68f9
API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0
drv: r600 device: 1 drv: swrast surfaceless: drv: r600 wayland:
drv: r600 inactive: gbm,x11
.fi
.TP
@ -2295,6 +2357,13 @@ For \fB\-j\fR row 1 output:
\fBKernel: swappiness: 60 (default) cache\-pressure: 90 (default 100)\fR
\- Adds zswap data for row 1 output:
\fBzswap: [yes/no] compressor: [type] max-pool: xx%\fR
\- Adds for zram swap type: active compression type, available compression
types, and max compression streams.
\- Adds device kernel major:minor number (Linux only).
.TP
@ -2388,6 +2457,8 @@ Component report to 1 component per line.
.TP
.B \-a \-S\fR
\- Adds alternate kernel clock sources, if available (Linux only).
\- Adds kernel boot parameters to \fBKernel\fR section (if detected). Support
varies by OS type.
@ -2443,9 +2514,8 @@ basically forces the downloader selection to use \fBPerl 5.x\fR
may help bypass issues with downloading.
.TP
.B \-\-bt\-tool [bt\-adapter|hciconfig|rfkill]\fR
Force the use of the given tool for bluetooth report (\fB\-E\fR). \fBrfkill\fR
does not support mac address data.
.B \-\-bt\-tool [bt\-adapter|btmgmt|hciconfig|rfkill]\fR
See \fB\-\-force [tool name]\fR. Used to set \fB\-E\fR report tool.
.TP
.B \-\-dig\fR
@ -2484,6 +2554,10 @@ as a comma separated list:
\fBinxi \-MJ --force dmidecode,lsusb\fR
\- \fBbt\-adapter\fR \- Force use of bt\-adapter tool in \fB\-E\fR.
\- \fBbtmgmt\fR \- Force use of btmgmt tool in \fB\-E\fR.
\- \fBcolors\fR \- Same as \fB\-Y \-2\fR . Do not remove colors from piped or
redirected output.
@ -2492,18 +2566,25 @@ redirected output.
\- \fBhddtemp\fR \- Force use of hddtemp instead of /sys temp data for disks.
\- \fBifconfig\fR \- Force use of IF tool ifconfig for \fB\-i\fR.
\- \fBip\fR \- Force use of IF ip tool for \fB\-i\fR (default).
\- \fBlsusb\fR \- Forces the USB data generator to use \fBlsusb\fR as data
source (default). Overrides \fBUSB_SYS\fR in user configuration file(s).
\- \fBrpm\fR, \fBpkg\fR \- Force override of disabled RPM package counts on
primarily RPM run systems due to unacceptably slow execution times for this
\- \fBrfkill\fR \- Force use of rfkill tool in \fB\-E\fR. \fBrfkill\fR does not
support mac address data.
\- \fBrpm\fR, \fBpkg\fR \- Force override of disabled rpm package counts on
primarily rpm run systems due to unacceptably slow execution times for this
command:
.nf
\fBrpm \-qa \-\-nodigest \-\-nosignature\fR
.fi
Even on newer RPM systems, in virtual machines, running rpm package list query
Even on newer rpm systems, in virtual machines, running rpm package list query
takes more than 0.15 seconds (compared to 0.01 to 0.05 for dpkg, pacman, pkgtool
etc) for just this single feature, which is north of 10% of total execution time
for \fBinxi \-bar\fR. On bare metal this can hit 1 second or more in our tests.
@ -2542,6 +2623,10 @@ Temporary override of \fBNO_HTML_WAN\fR configuration item. Only use to test
w/wo HTML downloaders for WAN IP. Restores default behavior for WAN IP, which is
use HTML downloader if present and if dig failed.
.TP
.B \-\-ifconfig\fR
Shortcut. See \fB\-\-force ifconfig\fR.
.TP
.B \-\-man\fR
Updates / installs man page with \fB\-U\fR if \fBpinxi\fR or using \fB\-U 3\fR
@ -2674,7 +2759,7 @@ color codes in the output, use the \fB\-c [color ID]\fR flag.
The sign you need to use this is extra numbers before the key/value pairs of
the output of your program. These are IRC, not TTY, color codes. Please post a
github issue if you find you need to use \fB\-\-tty\fR (including the full
codeberg.org issue if you find you need to use \fB\-\-tty\fR (including the full
\fB\-Ixxx\fR line) so we can figure out how to add your program to the list of
whitelisted programs.
@ -2723,8 +2808,8 @@ Accepts one or more comma separated dbg specific debugging numbers.
and fetch. Shows more downloader action information. Shows some more information
for Perl downloader.
\fB1\-xx\fR \- See github \fBinxi\-perl/docs/inxi\-values.txt\fR for specific
specialized debugging options. There are a lot.
\fB1\-xx\fR \- See codeberg.org \fBinxi\-perl/docs/inxi\-values.txt\fR for
specific specialized debugging options. There are a lot.
.TP
.B \-\-debug [1\-3]\fR
@ -3041,7 +3126,7 @@ data inxi uses to parse out its report.
.TP
.B Issue Report
File an issue report:
.I https://github.com/smxi/inxi/issues
.I https://codeberg.org/smxi/inxi/issues
.TP
.B Forums
Post on inxi forums:
@ -3051,7 +3136,7 @@ Post on inxi forums:
You can also visit \fRchannel:\fI #smxi\fR to post issues on either network.
.SH HOMEPAGE
.I https://github.com/smxi/inxi
.I https://codeberg.org/smxi/inxi
\fR \- Home of the source code, and tech docs
(\fIinxi\-perl/docs\fR).

563
inxi.changelog
View file

@ -1,3 +1,564 @@
================================================================================
Version: 3.3.31
Patch: 00
Date: 2023-10-31
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------
Packagers: remember, inxi repos and issue reports are now on codeberg.org - make
sure to change your package scripts and URLs. Github will be mirrored for inxi
for a little bit more, maybe I will extend it one more quarter depending, but
source repos should be changed.
--------------------------------------------------------------------------------
A small point release, mainly for fixes and bugs, plus a few minor matching
table updates. Also some core tools updates, which make supporting gpu devices
easier over time, particularly nvidia ones. Also some gpu data updates, new
nvidia 545, which was unexpected, came out, extending the time to next legacy by
some months.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. GRAPHICS: GPU DATA: codeberg user malcolmlewis who also posted both the first
pinxi issue, and the first codeberg issue. I had not thought nvidia would forget
to add their own device IDs to their lists, but they did. This prompted an
upgrade to the gpu_raw.pl/gpu_ids.pl to better handle manual add files for
Nvidia, as well as better overall consistency for gpu data files and processing.
2. SYSTEM: Wakeups: Mint user senjoz for alerting me to the well done but
unfortunately localized to mint forums report on the wrong wakeup count report,
because the data source was not what I thought it was.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Any distro forum person who finds issues related to inxi maybe being wrong or
operating from false assumptions in terms of data sources should ideally find a
way to report these issues directly, either via a codeberg issue, an email, or
something else. It's not possible or practical to track every forum that uses
inxi to debug user issues, so if members of those forums can be more proactive
in terms of sending what appear to be valid issue reports to the inxi project,
that will help a lot.
2. GRAPHICS: GPU: no data for things like Biren and other non AMD/Intel/Nvidia
GPUs. If you are into GPUs, by all means, help us out here!
--------------------------------------------------------------------------------
BUGS:
1. INFO: main::get_wakeups(): I'd say that despite in the past largely being
correct, using /sys/power/wakeup_count is a bug, but a bug that is excusable
because the docs are just too opaque about what this thing actually refers to.
My assumption re its meaning was clearly wrong.
--------------------------------------------------------------------------------
FIXES:
1. INFO: main::get_wakeups(): Issue reported via a Mint forum posting which I
was alerted to.
https://forums.linuxmint.com/viewtopic.php?p=2378107#p2378107
This would have made it into inxi 3.3.30 easily since the patch is changing file
name, but I unfortunetly did not become aware of it until right after the
release, On my system, for example, with systemctl suspend instead of the not
working xfce suspend from gui, I get 7 wakeup_count type events counted for each
suspend event. On another system I have, almost same everything, except fully
functioning xfce suspend feature, the success and wakeup_counts are matched.
I found a value of 49000+ digging through my datasets, and I can find no
pattern, nor can I find this clearly documented, so the behavior is simply going
to be use the value, including 0, from /sys/power/suspend_stats/success and
using it if it is defined, and getting rid of /sys/power/wakeup_count completely
as a data source, which I am now no longer sure at all about the meaning of. 1
of my systems has 7 events per resume, one, almost the same setup, has 1.
2. GRAPHICS: GPU DATA: Many nvidia fixes, device ID lists updated and corrected.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. PARTITIONS: added puzzlefs, atomfs to excludes. It's unclear, but both sound
like they are like isofs or something like that.
2a. GRAPHICS: GPU DATA: added Nvidia Pascal, Hopper, Lovelace device IDs. See
Code 1 for fixes to detections. Added AMD, Intel newer GPU IDs, going with Code
1 and GPU data fixes.
2b. GRAPHICS: GPU DATA: updated lists, added Nvidia current EOL data, added
newer kernel/X.org last supported. Added two more memssage types for current,
legacy messages. Found a site that lists EOL for the drivers, that helps.
2c. GRAPHICS: GPU_DATA: added new 545 driver IDs, updated nv current to 545
3. SYSTEM: Distro: Added ubuntu noble 24.04 system base ID.
--------------------------------------------------------------------------------
CHANGES:
1. DATA: pinxi/tools/lists: made file names consistent for gpu data types.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DOCS: docs/inxi-graphics.txt, docs/inxi-partitions.txt - ongoing updates for
features. More GPU data added, new file system types.
--------------------------------------------------------------------------------
CODE:
1a. GRAPHICS: GPU DATA: pinxi/tools/gpu_raw.pl, pinxi/tools/gpu_ids.pl. Upgraded
to enable basic manual additions to nvidia drivers. Also fixed detections for
Hopper and Lovelace, those were too tight and I missed some device IDs there.
Redid tools/gpu_raw.pl and gpu_ids.pl to have the more predictable file names.
Also changed the file names to be consistent for nv data in pinxi/tools/lists/
gpu.[amd|intel].full
gpu.[amd|intel].full.sorted
gpu.[amd|intel].manual
gpu.amd.github
gpu.intel.com
gpu.nv.[driver].full
gpu.nv.[driver].full.sorted
gpu.nv.[driver].manual
gpu.nv.[driver].raw
This let me bring all the lists up to date, and some manual fixes added in to
some driver sets.
1b. GRAPHICS: GPU_DATA: pinxi/tools/gpu_ids.pl - updated for Nvidia: new
messages, current eol, filled out legacy drivers with their eol based on last
nvidia driver release date.
2. CORE: there were some pointless globals being used, as part of the overall
effort to get rid of globals where sensible, else move them into hashes/arrays,
makes code easier to maintain long term.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 31 Oct 2023 13:08:12 -0700
================================================================================
Version: 3.3.30
Patch: 00
Date: 2023-09-25
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------
PACKAGERS! inxi repos are moved to https://codeberg.org/smxi/inxi
The repos will mirror to github for a short amount of time, until after 3.3.30
is released, then I am probably going to do some big changes in the structure of
the inxi repo. Make sure to update your packaging tools and scripts for this
change.
--------------------------------------------------------------------------------
Finally, a huge upgrade for Wayland future proofing, and other futures that are
maybe coming, by adding EGL API, and Vulkan for good measure. This should handle
wayland finally, that's been a stub forever, but finally realized eglinfo was a
thing, and that vulkan as well could be a contender to replace OpenGL, at least
that's what Mesa says on their site, and they should know.
This handles one of the longest standing weak points of inxi graphics, being
completely X11-centric, even though wayland support exists fairly extensively,
but this glxinfo dependent feature was a niggling annoyance, now it's fairly
ambivalent about which api tool you throw at it, the hardest is to give the
right message for no data, or incomplete data. Note that eglinfo supplies at
least software rendering out of X11 or Wayland, so we can now get some API data
in console, including if supported, OpenGL data. Not all of it, but some of it.
Also since now all the docs are split and granular, with the Graphics API
upgrades, added data sample files from glxinfo, eglinfo, vulkaninfo, and vainfo
for good measure, just to have some of the latter. This is one of the first time
all the data used to develope a feature, docs for that feature, and the feature
itself, are being shared and released at the same time.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1a. GRAPHICS: API: Arch user Chrome30 on github for requesting vulkan data, and
providing the initial datasamples that made it possible to think about this new
API feature.
1b. CheckRecommends: Display packages: mrmazda, a frequent helper, checked and
updated OpenSUSE and Fedora vulkan/egl/glx API tool package names. Those have
been a bit fluid and many of the names I had were not right.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1a. GRAPHICS: nothing is perfect, for sudo/root the detections fail for OpenGL
API messages, but fallbacks will make it a bit nicer than it was, with some
data, instead of none as before.
1b. GRAPHICS: API: I'm assuming that the greatest EGL version number found is
the actual version, and lower versions are what that platform supports. This is
an assumption, not a known fact, but finding this stuff clearly documented tends
towards near impossibility, or takes forever to determine, so that's the
assumption that is being used. Correct via issue and clear explanation with
links to resources if this is incorrect.
--------------------------------------------------------------------------------
BUGS:
1. Nothing to speak of.
--------------------------------------------------------------------------------
FIXES:
1. PARTITIONS: had wekafs as a zfs type fs, it's not, it's more like NAS, cloud.
Added to distributed list, and removed from zfs|btrfs|hammer list. I know, I
know, will it ever matter? Probably not. But just in case, wouldn't want your
local machine to report with petabytes of storage now would we!
2. CheckRecommends: corrected some Fedora, SUSE package names.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1a. SYSTEM: DistroData: added Bodhi id method, /etc/bodhi/info file which is
similar to /etc/lsb_release, updated system base detection as well. System base
comes from /etc/os-release.
1b. SYSTEM: DistroData: Added Nitrux system base (debian). Why they try hide
this is beyond me. Maybe because they are not using a real PM, and don't include
apt, who knows.
2a. GRAPHICS: new nvidia gpu ids.
2b. Graphics: EGL API data:
* Shows eglinfo missing if appropriate, no data messages if appropriate.
* -G shows EGL version(s), drivers, active platforms.
* -Gx adds active/inactive platforms as sub items of platforms.
* -Gxx shows platforms by platform, with egl version, driver. EGL version only
shows if there were more than 1 detected, otherwise it shows with EGL v:
* -Gxxx shows hw based on driver, if found, like vulkan.
To avoid excess verbosity, does not show renderer OpenGL name per platform
because it would be way too long and repetetive. And besides, that would show
in OpenGL anyway, more or less, unless there are two different GPUs, which is a
case that is not fully handled.
2c. GRAPHICS: OpenGL data:
* If glxinfo not present, or with null output due to root/no display, and if
eglinfo available, and has OpenGL items, will populate most of OpenGL API with
data, except for Direct Rendering and GLX version. Shows appropriate messages
indicating it's EGL sourced for console, root, no data, or glxinfo missing.
* -Gx adds GLX version, if detected.
* -Gxx add: ES version, if detected; device-ID, if available. Also adds
display-ID, if Display-ID was not found in the Display line (which probably
means that xdpyinfo or xrandr were not installed). Does not always show since it
already appeared in Display line if it was discovered.
* -Ga adds device memory, and unified memory status (yes/no).
2d. GRAPHICS: Vulkan API data:
* Shows appropriate messages if vulkaninfo present, but no data found.
* -G shows Vulkan version, drivers, and surfaces.
* -Gx device counts.
* -Gxx adds device by id, type, driver report.
* -Gxxx adds layer count; adds device hardware vendor, based on mesa driver. Not
for nvidia driver, since that is self evident. Goes away with -Ga if device name
exists.
* -Ga adds full device report, including per device names, ids, drivers, driver
versions, surfaces.
3. UPDATE: Because the smxi.org server no longer accepts TSL 1.1 based HTTP
requests, added for extreme legacy systems a new update option, -U 4, which
uses direct FTP download from smxi.org ftp server. If system set to default to
perl downloader HTTP::Tiny it switches to using a non perl downloader
automatically, like wget or curl.
4. CPU: Microarch: got early zen5 possible IDs. Both Intel/AMD may have rough
ID working well before they ship in public. CPU stuff has slowed down a lot,
the 4,3n nodes are not easy, obviously.
5. DRIVES: Many more drive vendors and drive IDs.
6. RAM: More RAM vendors. Note that it's not unusual for a Drive vendor to also
make RAM, and vice versa.
--------------------------------------------------------------------------------
CHANGES:
1a. GRAPHICS: For API, show OpenGL mesa-v: x.x.x separate from main API v:
string. Also only shows the actual API version with v: now, like v: 4.5. Also
shows vendor: nvidia v: 340.23 for nvidia, without mesa. Falls back for
unhandled cases or syntaxes to the whole version string for v:.
1b. GRAPHICS: For OpenGL, shows compat-v: always if present, that was a mistake
not to show it unless -Gx, since otherwise you'd think you are running a
different version. Not a common situation, but on legacy hardware, can happen.
--------------------------------------------------------------------------------
DOCUMENTATION:
1a. DOCS: docs/inxi-cpu.txt - reorganized into more coherent sections, like with
like, etc. Added better top Sections navigation since there is so much data.
1b. DOCS: docs/inxi-resources.txt - moved last code tricks to
docs/tips-tricks.txt.
1c. DOCS: new docs/ files inxi-battery.txt, inxi-debuggers.txt,
inxi-devices.txt, inxi-kernel.txt, inxi-machine.txt, inxi-network.txt,
inxi-raid-logical.txt, inxi-start-client.txt, inxi-tty.txt, inxi-weather.
These new files cleaned out docs/inxi-data.txt and docs/inxi-resources.txt,
which are now merely placeholder files, and have no data in them beyond pointers
to the actual data files.
1d. DOCS: docs/inxi-custom-recommends.txt updated for SUSE/Fedora packag name
fixes and new eglinfo and vulkaninfo items.
2a. DATA: moved more data from non public data to shared. Refactored directories
to be better organized, and to follow the overall inxi data structures better.
2b. DATA: added many more eglinfo, glxinfo, vulkaninfo to data/graphics. Also
added some clinfo, vainfo just in case decide to support those APIs.
3a. MAN/OPTIONS: updated for new graphics API features, new verbsity features,
etc.
3b. MAN/OPTIONS: added -U arguments for man, for some reason I'd left those out.
Also removed options references to -U 1, 2, because those should never be used,
if those versions of inxi even exist, they are ancient. Added -U 4 option, and
explanation of when/why to use it.
--------------------------------------------------------------------------------
CODE:
1a. FAKE DATA: updated paths for fake data to reflect data reorganization.
1b. FAKE DATA: Added --fake egl,glx,vulkan for GRAPHICS API.
2. GRAPHICS: Fully refactored opengl_output, moved to gl_data/opengl_output.
Added egl_data, egl_output, and vulkan_data, vulkan_output, and some other
tools.
3. UPDATE: if downloader is set to 'perl', aka, Tiny::HTTP, and -U 4 is used,
which is a direct FTP download of the inxi/pinxi files, tiny is disabled, and
the next available downloader (wget/curl/fetch) is used instead.
4. DEBUGGER: added clinfo, eglinfo, es2_info, vainfo, vdpauinfo, vulkaninfo.
--------------------------------------------------------------------------------
-- Harald Hope - Mon, 25 Sep 2023 15:03:45 -0700
================================================================================
Version: 3.3.29
Patch: 00
Date: 2023-08-15
--------------------------------------------------------------------------------
RELEASE NOTES:
--------------------------------------------------------------------------------
Some significant bugs, 1 showstopper for FreeBSD, and one universal one for USB
network devices, and possibly some other USB device types. Also some nice new
features.
--------------------------------------------------------------------------------
SPECIAL THANKS:
1. SYSTEM: Github user chromer030 in issue #285 - a very nice small enhancement
to -Sxxx line, adding kernel clocksource, and with -Sa, adding available
clocksources. I wish all issues were this clean and easy to implemment, with
such clear benefit.
2. BLUETOOTH: Github user chromer030, issue #286 - extending and adding
bluetooth report feature. This required refactors and some cleanup of bad logic
to make -E more able to handle new data sources, and also made me fix the docs
and add debugger data files to make testing changes for various bluetooth
datasources easier. Adding btmgmt turned out to have a lot of long term benefits
to the bluetooth feature and internal inxi logic, I hadn't realized how hacked
on bluetooth feature was, but code review showed it clearly.
3. SYSTEM: Github user oleg-indeez found a break in FreeBSD compiler data, 2
glitches, one made inxi crash due to is array test on undefined reference, the
other maybe a bad copy paste in the past that assigned compiler data to wrong
hash. See CODE 3 for details on the ref issue.
4. SWAP: Github user chromer030, again, issue #290 suggested some swap
zram/zswap data enhancements, seems good, so thanks.
5. UsbData: Slackware/Linuxquestions.org poster J_W for posting on a device
missing in his output as of 3.3.27 inxi. This exposed bug 3, which usually was
npt visible since the fallback was catching most of the network matches, but
since he had a TP-Link, and it went missing, it triggered the issues, and also
exposed the inconsistent upper/lower case use in device type from kernel.
6. NETWORK: Slackware user babydr on linuxquestions.org tripped a bug in
network, was not counting correctly to limit IP list. Led to showing limit
message on 10th row of network report, not 10th IP of a device. See Bug 4.
--------------------------------------------------------------------------------
KNOWN ISSUES:
1. Nothing new.
--------------------------------------------------------------------------------
BUGS:
1. BLUETOOTH: with hciconfig, would show wrong LMP/HCI version because either
the syntax changed for those strings, or it was wrong always. I think it changed
because this worked correctly at one point. Should now show the right hci/lmp
versions, and the bluetooth version as expected for hcicconfig/btmgmt.
2. SYSTEM: CPU compiler broke for FreeBSD 13.2, caused by bad test for undefined
array in CompilerVersion::version_bsd(), and also, assigned kernel compiler data
to %dboot instead of %sysctl hash. Thanks oleg-indeez for spotting that one and
figuring it out.
3a. UsbData: Failure to use /i caseinsensitive on regex led to failure to detect
USB type using standard defaults, but then a further regex error, subtle, missed
a | between two elements of a pattern, led to the last fallback case for network
detection failing. This was coupled with a change in the Kernel, which now uses
Uppercase first sometimes, and sometimes lowercase first. I think that's a
change anyway. This resulted in some usb type hashes failing to load specific
devices, network in this case, TP-Link, which was the fallback pattern that
broke.
3b. UsbData::assign_usb_type() improper nesting of tests led to failures that
should not have happened, like a bluetooth device cascading down to network.
4. NETWORK: IP limit was limiting based on total row count, not the actual count
of IPs for that device. Not sure how that slipped up. Now correctly limits the
IPs, not the previous total rows in Network report. Thanks babydr / Slackware
forums for finding yet more issues.
--------------------------------------------------------------------------------
FIXES:
1a. BLUETOOTH: added in switches for fake bluetooth data for all bluetooth data
sources.
1b. BLUETOOTH: made --bt-tool load $force{[tool]} to be consistent with rest of
logic in inxi for forcing use of specific tools. No idea why I made a standalone
one only for Bluetooth.
1c. BLUETOOTH: the HCI/LMP version generators were mixing up bluetooth version
string and LMP, leading to wrong results. See BUGS 1. I think this was a syntax
change because I would not have generated this originally if the syntax had not
worked, at least I don't think I would have. See also DOCS DATA item, added in
samples for dev purposes to avoid this type of issue in future.
2. UsbData: Device type from /sys could be upper/lower case first, but inxi was
not testing for anything but lower case, which would lead to fallback tests for
Bluetooth, Network, at least, maybe others. This goes with BUG 3, which exposed
a small torrent of such potential failure cases. The fallback block of regex is
really only designed to catch the few that don't get caught by the generic type
tests.
3. NETWORK: UsbData::set_network_regex(). Bad regex caused bluetooth device:
"Intel Bluetooth wireless interface" to trip an overly loose regex for wireless.
See BUG 3b. The real issue was incorrect test nesting which led to a bluetooth
device falling down to network regex, which it should not have done. It also
failed test the product name for bluetooth, which led to failure as well.
4. SWAP: Was failing to capture some zram syntaxes, regex was too tight. Failed:
/run/initramfs/dev/zram0.
--------------------------------------------------------------------------------
ENHANCEMENTS:
1. SYSTEM: added kernel current clocksource for -Sxxx, and alternates for -Sa.
2. BLUETOOTH: added btmgmt as first fallback to hciconfig, that one also
supplies bt version via lmp version, like hciconfig. Note this tool has very
little useful information.
3. Added back in discoverable, active discovery, and pairing status with -Ea.
This data is also crudely available from btmgmt but I would not bet on those
items actually being right. I'm not totally convinced that's good data, so
making it admin for now. Put these in a 'status:' parent container.
4a. SWAP: Added zswap enabled, compressor, max_pool_percent for -ja swap general
features line. If no zswap data and Linux, shows 'N/A'.
https://www.kernel.org/doc/Documentation/vm/zswap.txt
4b. SWAP: Added zram comp_algorithm max_comp_streams to -j per line report, only
for zram, of course.
https://docs.kernel.org/admin-guide/blockdev/zram.html
--------------------------------------------------------------------------------
CHANGES:
1. None that are obvious.
--------------------------------------------------------------------------------
DOCUMENTATION:
1. DATA: Added new data/bluetooth/, with several sample 'btmgmt info' and
'hciconfig -a' outputs for debugging and reference purposes. These work with
the revised debuggers and force/fake data switches for bluetooth. Should add
some bt-adapter --info samples too to make testing/debugging easier.
2a. DOCS: Made new docs/inxi-bluetooth.txt doc.
2b. DOCS: Moved more data out of inxi-data.txt and inxi-resources.txt, into
inxi-bluetooth.txt, tips-tricks.txt, man-pages.txt. While I'm not going to do it
all at once, I am trying to move relevant data into granular doc file as I hit
that during dev.
2c. DOCS: Updated and organized docs/inxi-tools-mapping.txt more, new mapping
tools added. inxi has so many manually updated mapping tools that it's going to
get more and more important that this document is accurate, and is updated when
required.
3a. MAN/OPTIONS: Added BT tools to --force lists, and updated --bt-tool list.
Also added -Ea options, the status: stuff.
3b. MAN/OPTIONS: Made consistent, lower case rpm, both PM type rpm and rpm as
rotation were switching between RPM and rpm randomly.
3b. MAN/OPTIONS: Updated for --force ip/ifconfig, --ifconfig.
3c. MAN/OPTIONS: Updated for zswap, zram extra -ja data.
--------------------------------------------------------------------------------
CODE:
1. BLUETOOTH: added %force bluetoothctrl, bt-adapter, btmgmt, hciconfig, rfkill,
and added checks to enable $fake{'bluetooth'} in the main callers for each type.
This makes debugging and development a lot easier. Also removed the force tool
block in CheckTools, no idea, again, why I did it that way only for bluetooth.
2. CheckTools: got rid of set_forced_tools(), which was only used for bluetooth
tools, and didn't fit with the rest of the core logic.
3. SYSTEM: CompilerVersion: used array refs wrong, or rather, used refs wrong,
which led to various errors that were confusing. Corrected to start out with an
array ref, then to pass that as is, leaving it the same ref all through, for bsd
and linux. This is the method inxi should have always used for passing array/
hash refs around, create as ref, then pass around, and update, without assigning
a new ref to it.
I had failed to verify that the same ref was being used through the sequence.
Unfortunately this error is probably very widespread in inxi, because no
consistent rule was created and enforced from the first lines of Perl.
4. UsbData: added source type to --dbg 6 output, and added --dbg 55 to output
the per type arrays.
5. NETWORK: IpData:: added --ifconfig/--force [ip|ifconfig], --fake ip-if to
allow for basic debugging for -n / -i IP data sources. Not super useful since so
much comes from /sys, but there was nothing there at all, which is weird for
networking.
6. SWAP: Changed to passing data using scalar references, not returning an
array of the items, and got rid of the copies in the swap_data_advanced() tool.
It's less readable, but incurs basically very little overhead, and with the new
function / method arg lists I'm using more now, it's clear what the references
are.
7. IpData: got rid of extra array copies for push, pointless.
--------------------------------------------------------------------------------
-- Harald Hope - Tue, 15 Aug 2023 19:45:54 -0700
================================================================================
Version: 3.3.28
Patch: 00
@ -5998,7 +6559,7 @@ 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
3. For -A, -G, -N, and -E, new item for -xxx, class-ID, 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!