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

...

23 commits
3.3.25-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
Harald Hope
7a79e846de small fix 2023-07-10 15:40:08 -07:00
Harald Hope
2434d89d0c New version, new man. Continuing the Memory info rollout started in 3.3.27. 
--------------------------------------------------------------------------------
SPECIAL THANKS:

1. Thanks to linuxquestions.org Slackware forums for poking around a bit at the
new Memory total logic.

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

1a. MEMORY: The memory total: has to be synthesized in some cases, based on some
math and educated guessing. When these guesses fall outside of predetermined
ranges, inxi will show note: est. to let the user know the total was synthesized
and possibly incorrect. For detected virtual machines, inxi does not try to
synthesize the total because a VM can have any amount of RAM assigned.

If superuser, and -m used, shows the real total from dmidecode if any RAM was
found. Not all systems have DMI RAM data however, or have dmidecode installed.
Will fallback to sythetic method in that case, which is usually right.

1b. MEMORY: With the superuser /proc/iomem method, if on a VM and not using even
GiB sized RAM ollocation, and -M is not triggered (which usually lets inxi know
it's a VM), the total will get rounded up or down based on a set of rules. For
example, 2.5 GiB real would become 3 GiB. I don't see any solution to this,
either assume the /proc/iomem is right but needs rounding up, or assume the /sys
block counts are right, or remove the feature.

Shows note: est. in cases where the rounded total is greater than a dynamic
factor difference from the internal total amount.

2. GENERAL/GRAPHICS: The problem of users showing up, requesting a feature, then
not doing any work, research, supplying energy, interest, and dare I say,
passion - nothing, expecting 'someone else' to do the work for them, continues,
sadly, with the recent request for vulkan data for Graphics. This appears to be
a problem more with the modern generation of free software users, I don't
remember this type of attitude 20 years ago, but I did watch it as it started
getting more common. Demotivating to be honest, but maybe one day someone will
show up who actually cares enough to help get the features they want developed.

While I am leaving that up as a low priority feature request, I am not
personally interested in that feature, nor is anyone else I asked, and given how
much raw data there is, and how difficult it is to parse, I'll just leave it as
an existing issue which might get work in a few years time, or not, basically
will require someone showing up who actually actively cares.

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

1. DISK: total: used: report could have had wrong results for used:, like used
being > total: because the filter lists were missing some file systems for
exclusion. More of a fix than a bug, but users might see it as a bug.

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

1. INFO: get_gcc_data(): was showing same GCC version as main and alternate.
Failed to filter out the discovered primary, that is. This is because usually
name is gcc-11 but sometimes it's the whole version, like gcc-11.2.0, the full
version string. This is the case in Slackware for example.

2. SHORT: MEMORY: BSD: did not show '%' for memory used percent, just the
number.

3. DRIVES/PARTITIONS: PartitionItem::set_filters() added many more exclude
types, that will help avoid both creating wrong disk used totals, and also not
show label:/uuid: fields for filesystem types that don't have uuid/labels. There
were a lot missing: encrypted, distributed, stackable, remote. Should clean up
wrong disk used values in some cases.

4a. PARTITIONS: PartitionItem::set_filters(). Added a lot of file systems, many
fuse, distributed, stackable types.

4b. PARTITIONS: Extended remote file system ID by fs, and added fuse fs for
local mounts, like gvfs, mtp, ptp and many other variants, that's things like
mounting apple partition, android, iphone, archives, etc. This should correct an
entire class of source: ERR-102 outputs.

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

1. BATTERY: Added 'power' to battery report. That's the amount of watts its
using at that moment, so not super useful since it's running inxi at that
moment. But the data was there, so might as well show it. Only for -Bxx since it
will be so variable. Shows after the charge/condition item.

2. SYSTEM: DistroData: added Oracle id and system base. Added Springdale/PUIAS
system base support. Note, unusually, Eurolinux, ScientificLinux 'just worked'
re id and system base even though that had never been explicitly added. This is
because their os-release file contains 'centos' string.

3. SYSTEM: DistroData: Added ubuntu mantic minotaur to ubuntu id matching table.
This only really is used by Mint, but there you have it. Also added Debian 14
codename Forky.

4a. MEMORY: Add total RAM from one of following:

* /sys/devices/system/memory (if it's available). This directory has to be
compiled into kernel, so is not always present. This source has advantage of
being user readable. If out of set bounds, shows note: est. to let user know
it's an estimate.

* If superuser and /proc/iomme, gets the total from /proc/iomem using some
tricks and synthetic methods, which in general is pretty accurate, but when out
of the bounds set, shows note: est. to let user know results are only estimates.
This overrides /sys total.

* If -m and dmidecode data found, uses the real RAM module total. For Linux and
superuser. This overrides iomem and /sys totals.

4b. MEMORY: add iGPU RAM from /proc/iomem when detected. Requires sudo/root.

4c. MEMORY: using the real -m/RAM total for memory total when available, since
that is the actual value we want, not the estimated stuff from /proc/iomem or
/sys/devices/system.

5. RAM: added a long time oversight, lack of per array RAM installed size and
occupied slots (modules). Those are now part of the Array line for each set of
modules. Since total already shows in System RAM line above, the granular per
array installed size total only shows if > 1 array is present, ie, almost never.

6. DRIVES: disk vendors, added more matches and vendors. We'll know the world is
changing in a significant way when no new vendors appear for a while, but that's
unlikely in the near term.

7. CPU: cpu_arch(), a few new ids added.

8. GRAPHICS: new amd, intel, nvidia ids, updates to driver version etc.

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

1. SHORT: for Memory:, switched to using MiB/GiB/TiB, these numbers are just
getting too big to be readable. This is also dynamic, if both used and available
are the same unit, shows x/y [unit], otherwise shows x [unit]/y [unit].

2. MEMORY: changed gpu: to igpu: to avoid confusing it with standalone gpu.
Since only raspberry pi had gpu ram data before, almost nobody would have seen
this in general anyway.

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

1. MAN/OPTIONS: Updated for -Bxx, battery power now.

2. MAN: updated to better define where the System RAM: total:.. available etc
come from, and what they refer to. Also added explanation in -m section about
what the stuff is, and what the field names refer to.

2a. DOCS: docs/inxi-ram.txt added, and more info moved from inxi-data.txt and
inxi-resources.txt. Goal is to remove both those files and move all their data,
and any new data, into granular inxi-xxx.txt files. Also moved some RAM data
from inx-unit-handling.txt to inxi-ram.txt.

2b. DOCS: docs/inxi-unit-handling.txt: updated with more ram / memory units,
code, etc, to better fit with the concept of the inxi-unit-handling.txt doc.

2c. DOCS: docs/inxi-partitions.txt: updated, added more sources for partition
file system types, cleaned up, more useful as a reference now.

2d. DOCS: docs/inxi-distros.txt: NEW, merged data from inxi-data.txt,
inxi-resources.txt. Updated and added more info.

2e. DOCS: docs/inxi-tools-mapping.txt split off from inxi-tools.txt, makes it
easier to find the mapping functions and features, which are hard to remember.
Also updated and improved its usability. This is kind of a key document because
it's hard to remember all the mapping tools internally, and this also connects
those tools to their relevant granular inxi-xxx.txt docs. Not that it will help
get helpers for these tedious tasks, but one can always dream, can't one?

3. DATA: data/graphics/ added for first vulkaninfo output file.

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

1a. RAM: Fixed an irregularity, for RamItem, it used MiB as internal unit, this
was silly because inxi uses KiB everywhere else. This correction was relatively
easy to do, and allows the values to be used by other parts of inxi, like
MemoryData.

1b. RAM: Added return of ram total for memory.

2a. INFO/RAM/PROCESSES: When MEMORY active, now uses row reference to create the
fields. For INFO, now uses MemoryData::row() to generate the row fields instead
of doing the logic in the info line generator. This simplifies the processing
and allows for more granular control of output.

2b. INFO/RAM/PROCESSES: Added debugger switches --dbg 53 (show raw KiB/count
values for /sys/devices/system/memory and /proc/iomem. Added --dbg 54, which
shows per line size for iomem, in human readable units, and a final summary
report of iomem and /sys data, this speeds up debugging.

2c. INFO/RAM/PROCESSES: Added --fake iomem, --fake sys-mem for debugging and
testing.

3. MEMORY: MemoryData::short_data(): added so one tool generates output for all
sources for short data. Easier to track and make consistent, and to make more
granular and robust.

4. DRIVES/PARTITIONS: PartitionItem::partition_filters(),
PartitionItem::fs_excludes(): refactored into PartitionItem::get_filters(),
PartitionItem::set_filters(). Cleaned up, organized better, made comments much
more useful. Goes with DOCS 2c updates. Now there's just one sub that does this
filter/exclude work, which makes it easier to maintain long term.

5. GLOBAL: Used a trick I just learned, declaring variables in the bracket scope
of a class, but not inside the package/class declaration. This makes it work
like a static variable, which Perl 5.008 doesn't support. You have to use a sub
inside the bracket scope to return the data outside that scope, but that is easy
to do.

6. MACHINE: Added return of b_vm for VM detection in MEMORY.

7. SYSTEM: CompilerVersion: Failed to properly use references when passing
$compiler around, not actually sure why it worked, but now is consistent.
 2023-07-10 14:18:45 -07:00
Harald Hope
ed7049fcc1 Completion of the audio fixes and improvements of 3.3.26. Added less common 
sound servers like EsounD and aRts, and made state reports more accurate for
ALSA.

Major USB code and data upgrades/refactors. The USB changes prepare inxi for USB
4, and adds lanes and Si/IEC speeds to the report. It is important to determine
what USB mode you are running in with 3.x and 4. These changes conform more
closely to how the USB consortium wants USB speeds refered to.

With more robust USB data, this data now appears in a similar form as pcie: data
for Devices, -A, -E, -G, -N, and for -D drives, as usb: plus rev, speed, lanes,
mode, with the -xx/-a options, like pcie. This has been a long standing
oversight and weakness of inxi USB and Device data, but now the two are fully
integrated, including for drives, which was quite tricky to get working.

Added netpkg and Zenwalk support to packages and repos. Also added repos support
for sbopkg and slpkg, and updated package tools for Slackware.

And more distros added to system base feature, and a few more for main ID.

Improved --recommends report quite a bit, now it's more granular for missing
packages and package manager reports, and also fixed a long standing missing
current shell + version issue. Added the final package manager type, pkgtool
(Slackware), that will be supported, which makes for 4, which is enough. Note
that other package managers can be added following the documentation
instructions for packagers, but this is enough for out of the box pm handling.

Fixed a long standing oddity with how free / /proc/meminfo report MemTotal vs
the actual physical RAM. I believe this issue also showed with GPU assigned RAM,
but now for all but short form, shows Memory/RAM: available: ... used: ...

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

1. To the Slackware people at linuxquestions.org forums, who helped, again, on
this audio feature, even finding current or not too old systems that use some of
the new / old audio servers (EsoundD) running in the wild, which I never
expected to see. And also for exposing some weak spots in the USB advanced
logic, and helping with the sbopkg and slpkg repo logic and tools reports.

2. To the Manjaro forum users, for providing cases that show where inxi can be
improved. The audio server/api issue, the current USB 3/4 upgrade, were
initiated by threads pointing to things that could be improved in inxi. So I
guess the real thanks are for using inxi enough to trigger cases that show where
it's weak or can be better. Note that this requires that I follow roughly their
forums, however I only look at threads that seem like they might be of general
interest, or which suggest a possible weak spot in inxi, and I don't follow them
consistently. More reliable is to file github issues, since I will always see
those.

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

1. DesktopData: at one point, BunsenLabs Debian OpenBox had XDG_CURRENT_DESKTOP
set to XFCE, which it isn't, but inxi can't work around such hacks, plus I don't
even know if Bunsen is around anymore anyway.

2. DesktopData: CODE 1 reminds us that the time to depend on x tools like xprop
for anything re desktop/wm detections is fast drawing to a close, true Wayland
will not have xprop, unless it's running on xwayland, which is not something
that should be relied on. Maybe recheck Moksha/Enlightenment which depend on
xprop for version detection.

The list of xprop detected wm/desktops in get_env_xprop_misc_data() is almost
all X only wm/desktops, so those should be safe unless one of them decides to
work on a wayland comositor.

3. BSD: ongoing weaknesses in BSD data sources make maintaining feature parity
impossible, but I am trying to get the BSD data as clean and consistent as
possible. I wish this were not the case, but the fact is, /sys is expanding and
creating excellent and reliable data sources with every major Linux kernel
update, and so far nothing comparable has appeared in the BSDs. This is just
reality, it's not a condemnation, but something like the /proc then /sys file
systems are an excellent idea, well worth emulating.

4. For the RAM available/total clarification, there's a slight issue because
free/meminfo show MemAvailable as Free for use RAM, but dmesg shows available
meaning what was available to the system during boot, minus the reserved
percentage. Since we needed one term, available to System offers the closest
in terms of technical precision without being too verbose. Technically available
in this context means: total physical minus 'kernel code' minus 'reserved'.

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

1. CheckRecommends: See Fix 6b, more or less a bug, but really just a fix.

2. AUDIO: for USB devices, put extra data into row 0, no matter which row the
USB device is. This led to the extra data for USB being assigned to the wrong
row. Sigh.

3. OptionsHandler: When show{'ram'} was set, for bsd, set use{'bsd-raid'}, which
makes both show raid and ram fail for BSD. Oops. User mode RAM data only seen in
OpenBSD so far. This made loading $dboot{'ram'} fail, and any raid as well,
sigh, unless -m was also tripped.

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

1. DistroData: typo for Arch base: was ctios, was supposed to be ctlos.

2a. DesktopData: found case where xprop -root not present (Void Linux), so xfce
test failed. Split to new function dedicated to xfce detection that doesn't use
xprop data. Also, XFCE is working on their Wayland version, which would in
theory not even have xprop by default.

Also, the base version number test for xfce depended on xprop, but
xprop doesn't even have that xfce version data anymore, so just checking if
xfce(4|5|)-panel exist and assigning primary version based on that test.

2b. DesktopData: Also see See CODE 1a,1b for further xprop and test fixes that
could have led to false positive or negative test conditions for the items that
used xprop tests. These tests are all xprop agnostic now, if it's there, they
will use it, if not, do the best they can.

3. PackageData: fixed legacy dpkg-query, old version did not support -f shortcut
for --showformat. This made dpkg package listing fail.

4a. GRAPHICS: Added legacy XFree86.0.log to X log path detection, that was an
oversight. Also added legacy module syntax _drv.o (not _drv.so). This gets X
driver data now for very old systems.

4b. GRAPHICS: fixed corner case where no x driver data, running as root, was not
supposed to show 'note: X driver n/a' message, that was a holdover from before
driver output was cleaned up and driver: N/A shows when no drivers at all found.
Just forgot to remove it when doing recent updates in the driver section, maybe?

5. REPOS/PackageData: For netpkg Zenwalk Slackware systems, showed only slackpkg
repo data, empty, and showed the Slackware pm, not netpkg for pm. See
Enhancements 5, 6.

6. REPOS: removed slapt_get file /etc/slapt-get/pubring.kbx, that's not a repo
file. Thanks chrisreturn for pointing that out.

7a. CheckRecommends: See also CODE 6. Fixed case where > 1 package manager is
detected on system, now lists them one by one for detected, and shows package
install options as well. Before only picked first detected, which could lead
to wrong results for Missing Package lists.

7b. CheckRecommends: Fixed glitch, forgot to update the current shell/version
when ShellData was refactored, this led to no current shell + version showing
up in recommends core tools report.

8. RAM: fixed speed_mapper string match to allow for older syntaxes. This is as
far as known OpenBSD only, from dboot data. Matches then converts PC2700 to
PC-2700 which then allows for mapping.

9. RAM/PROCESSES/INFO/SHORT: Finally tracked down a long time oddity, where for
example:
 RAM: total: 31.28 GiB
does not match 32 GiB physical installed. This is because that is the total
available after kernel and system reserved RAM is deducted, and in some cases,
GPU allocated RAM. There are also corner cases where the listed amount can be
less due to physical RAM damage, but that's uncommon.

Added explanation of why it's different, and what available is referring to in
man -m/--memory.

Changed -m, -tm to show:

System RAM: available: 31.28 GiB used 26.23 GiB (83.9%)

and -I to show:

Memory: available: 31.28 GiB used 26.23 GiB (83.9%)

You can get the 'reserved' and 'kernel code' data from dmesg, but since Debian
made that root/sudo tool, can't count on being able to parse that out of dmesg,
plus you can never count no dmesg anyway since it can get overwritten by kernel
oops or wonky device etc. inxi doesn't use dmesg data for Linux for this reason.

... [    0.000000] Memory: 32784756K/33435864K available (10252K kernel code,
1243K rwdata, 3324K rodata, 1584K init, 2280K bss, 651108K reserved, 0K
cma-reserved)

Also removed Raspberry Pi video RAM added back in to total now that it's clear
it's what is available. This may also make systems with GPU using system RAM
more correct.

9. SENSORS: sensors /sys tried to create concatenated string with $unit $value
but these are not necessarily defined, that needed to be protected with defined
tests.

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

1a. AUDIO: JACK: added helper nsmd (new session manager), and its recommended
gui agordejo. That's the drop in replacement for non-session-manager, the dev of
which apparently lost interest in that project. But the ID method will work fine
for for either, since both ran as nsmd.

1b. AUDIO: PULSE: added pulseaudio-alsa plugin support for helpers. This is like
pipewire-alsa plugin, just alsa config file. Only seen in Arch Linux so far, but
if others use similar paths for the glob pattern, they will also work fine.

Also added pulseaudio-esound-compat plugin, which is easier to detect with
/usr/bin/esdcompat.

Also added paman, pulseaudio manager.

1c. AUDIO: ESOUND,ARTS: added legacy esd (EsounD aka: Enlightened Sound Daemon)
and aRts sound server support, with basic help/tools. These are quite old, but
are still occasionally seen in the wild on newer systems, surprisingly enough.

1d. AUDIO: ALSA: added alsactl to alsa tools. Missed that one, it's an /sbin
type utility.

1e. AUDIO: ALSA: First try at ALSA compiled in but inactive report,  previously
depended on active only state of the API. Now uses compiled in SND_ kernel
switch using the /boot/config-[kernel] file, which is a big expensive parse but
only will activate on Linux kernels with no /proc/asound present. This fallback
fails if kernel config file not present: /boot/config-$(uname -r).

1f. AUDIO: OSS: added tool ossctl.

1g. AUDIO: NAS: added helper: audiooss which is an OSS compat layer.

2a. DistroData: added Arch base distros: ArchEX, Bridge Linux, Condres OS,
Feliz, LiriOS, Magpie, Namib, Porteus, RevengeOS, SalientOS, VeltOS.

None of these are verified. Some don't exist anymore.
Source: https://www.slant.co/topics/7603/~arch-linux-based-distributions

2b. DistroData: added ubuntu lunar 23-4 release id.

2c. DistroData: added porteux, added porteux, zenwalk to slackware systembase

3. DesktopData/GRAPHICS: added Smithay Wayland compositor. Not verified.

4a. UsbData/UsbItem: added USB lanes (-Jxx) and mode (-Ja), to add more useful
data about USB revision and mode names the USB group has created. Otherwise it's
too difficult to try to explain it. Note that -Jxx lanes follows other inxi
items that show PCIe lanes as an -xx item to try to keep it consistent.

This also consolidates the bsd and linux data sources, see CODE 5.

Note modes and lanes are Linux only because the revision number, lanes, and
speed used to determine mode are only natively available in Linux as actual
internal data values. If this changes BSD support will be added in the future.

The BSD rev and speed data is synthesized completely by inxi using some string
values, and thus is not reliable, which means that pretending inxi can get this
granular with data that is not coming directly from the system itself is
probably not a good idea.

Following wikipedia mode names: https://en.wikipedia.org/wiki/USB4

These are the known possible combinations:
rev: 1.0 mode: 1.0 lanes: 1 speed: 1.5 Mbps
rev: 1.1 mode: 1.0 lanes: 1 speed: 1.5 Mbps
rev: 1.1 mode: 1.1 lanes: 1 speed: 12 Mbps
rev: 2.0 mode: 1.0 lanes: 1 speed: 1.5 Mbps
rev: 2.0 mode: 1.1 lanes: 1 speed: 12 Mbps
rev: 2.0 mode: 2.0 lanes: 1 speed: 480 Mbps
rev: 2.1 mode: 2.0 lanes: 1 speed: 480 Mbps
rev: 3.0 mode: 3.2 gen-1x1 lanes: 1 speed:  5 Gbps
rev: 3.0 mode: 3.2 gen-1x2 lanes: 2 speed: 10 Gbps
rev: 3.1 mode: 3.2 gen-1x1 lanes: 1 speed:  5 Gbps
rev: 3.1 mode: 3.2 gen-1x2 lanes: 2 speed: 10 Gbps
rev: 3.1 mode: 3.2 gen-2x2 lanes: 2 speed: 20 Gbps [seen this case]
rev: 3.2 mode: 3.2 gen-1x1 lanes: 1 speed:  5 Gbps [wrong rev: seen this case]
rev: 3.2 mode: 3.2 gen-1x2 lanes: 2 speed: 10 Gbps [wrong rev: possible case]
rev: 3.2 mode: 3.2 gen-2x1 lanes: 1 speed: 10 Gbps
rev: 3.2 mode: 3.2 gen-2x2 lanes: 2 speed: 20 Gbps
rev: 3.2 mode: 4-v1 gen-3x2 lanes: 2 speed: 40 Gbps [not seen, but possible]
rev: 4 mode: 4-v1 gen-2x1 lanes; 1 speed: 10 Gbps
rev: 4 mode: 4-v1 gen-2x2 lanes: 2 speed: 20 Gbps
rev: 4 mode: 4-v1 gen-3x1 lanes: 1 speed: 20 Gbps
rev: 4 mode: 4-v2 gen-3x2 lanes: 2 speed: 40 Gbps
rev: 4 mode: 4-v2 gen-4x1 lanes: 1 speed: 40 Gbps
rev: 4 mode: 4-v2 gen-4x2 lanes: 2 speed: 80 Gbps
rev: 4 mode: 4-v2 gen-4x3-asymmetric lanes: 3 up, 1 down speed:120 Gbps

I believe 120Gbps takes the 2 lanes of tx/rx and converts 2 rx lanes to tx so
the entire lane is dedicated to transmit. and the third lane is dedicated to rx.

Includes error message for unknown usb 3/4 rev/speed match combos. These can be
bad hardware self reporting or unknown other issues.

4b. USB: Added Si/IEC speeds (base 2, base 10). -Ja triggers extra IEC, base 2
Bytes (xxx [MG]iB/s). -Jx triggers basic standard Si xxx [MG]b/s base 10 bits.

5a. PackageData: added netpkg as package tool. This stores data in same location
as slackpkg, but assume if exists directory /var/netpkg, then the system is
using netpkg as pm, not slackpkg.

5b. PackageData: added Slackware sbopkg, sboui as tools for pkgtool and netpkg.

6a. REPOS: added netpkg (Zenwalk Slackware based pm) repo report.

6b. REPOS: added sbopkg basic repo report. This handles both value syntax types,
as well as the ability of /root config file to overwrite /etc config repo.

6c. REPOS: added slpkg repo report. This handles their old and newer syntax.

7a. CheckRecommends: For Slackware users, added pkgtool missing package name,
also will use netpkg so hopefully Zenwalk uses same package names.

7b. CheckRecommends: Added radeon to kernel modules checks.

8. AUDIO/BLUETOOTH/DRIVES/GRAPHICS/NETWORK: For USB, -[ADEGN]xx adds rev, speed,
lanes. -[ADEGN]a adds mode.

9. RAM: Updated RAM PC DDR in speed_mapper(), which is as far as I know only
used by OpenBSD, which allows for MT/s speeds as non-root user, which is nice.
That list hadn't been updated in a long time, so filled out DDR 1-5 PCx-yyyy
ids.

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

1a. USB: For -Jxy1, speed is now a child of rev: parent. This goes along with
mode: and lanes: being children of rev:. This follows how USB consortium wants
to refer to USB revisions now: by speed, lanes, and modes, the latter being the
technical term, the speed being the marketing term.

1b. USB: If no speed data found, show N/A. This should almost never happen
except for very old Linux and rarely with BSD.

1c. USB: Device type is lower cased except for abbreviations (type-C, HID). This
makes it more consistent as a value.

1d. USB: Show basic Si speed with -Jx, and adds new IEC speed with -Ja.

2. CheckRecommends: See ENHANCEMENT, CODE 6. Now showing row by row package
managers and missing packages, by package manager(s).

3. DRIVES: Changed long standing redundant use of 'type':
type: USB ... type: HDD
to:
type: USB ... tech: HDD
'tech:' means the technology used, HDD, SDD, and if we can ever figure out how
to detect it, Hybrid Hard Drive (HHD),

4. AUDIO/BLUETOOTH/DRIVES/GRAPHIC/NETWORK: moved 'type: USB' pair to after
driver for -A/-E/-G/-N, which allows it to be the parent of the new USB data
block. Negative is it moves it a bit further back in the line.

For Drives, it moves it from after /dev.. maj-min to after block-size, However,
with -D/-Dx, it's last in the line, which is nice. This is the only way I could
find to make it more consistent across all possible USB device/drive type
reports.

5. INFO/RAM/PROCESSES: Changed -I:

Memory: [total] used:
to:
Memory: available: [total] used:

Changed -tm/-m to be consistent:

Memory: RAM: total: .. used..
to:
Memory: System RAM: available: ... used:..

This corrects a long standing inaccuracy where MemTotal is not actually the full
system RAM, but is the RAM minus reserved stuff for system and kernel, and GPU
memory in some cases.

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

1a. DOCS: docs/inxi-audio.txt: ongoing updates, adding more information, more
on helpers, detection methods, etc.

1b. DOCS: New: docs/inxi-usb.txt: USB info, update, added more, a work in
progress.

1c. DOCS: docs/inxi-custom-recommends.txt: name in inxi comment did not match,
and updated to new comment cleaned up syntax in example. Fixed inxi comment file
name.

1d. DOCS: New: docs/inxi-unit-handling.txt: To document how inxi handles
size/speed data internally, and ideally, to help integrate all those methods
into one big tool one day, not spread across many area.

1e. DOCS: New: docs/inxi-repo-package-manager.txt: To start to document arcana
and methods and commands and outputs for package managers. Since this is a late
start, will take time to complete, but better late than never.

2a. MAN/OPTIONS: updated for USB -Jx, -Jxx, -Ja, adding lanes, mode, iec speed
items.

2b. MAN/OPTIONS: fixed error which had USB speed as -Jxxx instead of -Jxx. Also
then changed speed to be -Jx.

2c. MAN/OPTIONS: updated for repos for SBOPKG, SBOUI, SLPKG, and added
SLAPT_GET, I'd forgotten that one.

2d. MAN/OPTIONS: updated for -xx[ADEGN] USB rev, speed, lanes; for -a[ADEGN]
updated for USB mode.

2e. MAN/OPTIONS: updated for memory available/used changed.

3. MAN: fixed some inconsistent use of short/long form display in extra data
options.

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

1a. DesktopData: New function for xfce only detections, turns out xprop is not
necessarily installed, Void Linux for example had failed ID. Old version
required xprop to do the tests, which was not robust and failed in this case.
Function: get_env_xfce_data(). Also made xprop data optional for all the
xxx_xprop_data desktop tests, not just some of them. This will forward proof
the desktops

1b. DesktopData: Fixed bad parens in test cases, was not correctly organized.
if (a || b || (c || d) && e)
was supposed to be:
if (a || b || ((c || d) && e))
Odd how those types of glitches creep in, one fix is also to just make the lines
break more reasonably so the conditions are easier to parse visually.

2a. DEBUGGER: Added /etc/X11/XF86Config-4 xorg conf file to debugger.

2b. DEBUGGER: audio_data(): added audio server versions to cover all known ones.

3. MemoryData: changed all $memory to array references, got rid of split :
separators, which were clearly legacy items leftover from bash/gawk days. Also
changed MemoryData::get('splits') to get('full') to reflect this change.

This change should be transparent though it may introduce corner case undefined
value situation but that should not happen since array values are defined first.

4. UsbData: Refactor of usb speed, rev, added lanes, mode. Refactored most of
the bsd/linux rev/speed logic, merged some of bsd speed/rev into the new
version_data() function, which loads all the data based on what is calling it.
This helps consolidate the logic across usb data sources.

5a. GLOBAL: made functions/methods use same comment syntax for args:
 args: 0:...; 1:...
always starting with 0, to match array index. Same syntax for return array index
values. In some cases simply note a variable is passed by ref:
 args: $value passed by reference.

5b. GLOBAL: made all sub/functions/methods follow the same spacing syntax. This
seems to be a good compromise for space/readability. Note that adding in these
new lines added about 400 lines to the total length, plus the line breaks that
were already there. Yes, inxi has a lot of sub routines! aka functions and
sometimes aka methods.

[empty line]
[comments]
sub [name] {

Packages/classes now also all follow the same spacing rules:

[empty line]
[comments]
{
package [name];
[empty line]
[comments]
sub [name] {
...
}
}

Internally, subs generally do not use any empty lines unless it makes sense to
do so for some specific reason.

5c: GLOBAL: made start of sub comments be upper case, I have a bad habit of
typing comments in lower case, easier to read if it's reads like a normal
sentence.

6. CheckRecommends: refactored entire items logic, set global hash for test
items. Made support > 1 detected package manager.

7. REPOS: cleaned up comments for package manager/repo blocks.

8. SENSORS: sensors_sys failed to reset to undefined $unit and $value, and also
failed to test if they were defined before using them in concatenation.
 2023-05-07 11:59:56 -07:00
Harald Hope
beddf67370 undid oops 2023-04-29 20:20:35 -07:00
Harald Hope
a2a955d870 oops 2023-04-29 20:18:50 -07:00
Harald Hope
f22449a205 man fix 2023-03-28 14:54:49 -07:00
Harald Hope
5ee29fa022 Significant upgrade to sound server running detections, much more granular and 
hopefully more accurate, with more useful reporting values. Also added some nice
useful audio api/server tool and info items.

Packagers: this corrects possibly wrong or misleading audio server reports,
particularly related to PulseAudio/PipeWire, which can lead to support issues
and lack of clarity due to ambiguous or wrong reports about sound Servers
present, active, or off. Upgrading your package is highly recommended.

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

1. Thanks to people like Chimera dev Daniel "q66" Kolesa for experimenting with
non systemd (uses dinit/dinitctl), non GCC, non GNU linux, and for making early
pre-alpha versions run in vm, and for being easy to test!

Not so much because I personally want or care about or view as a positive
skipping GNU tools or GCC in favor of clang and BSD tools, but more because
these experiments help make the general overall Linux ecosystem more robust.
Including inxi.

2. Thanks for the Manjaro people for noting this issue on their forums.

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

1a. AUDIO: jack_control and pw-cli won't run as root, exit with error. This
forces back to fallback process present tests for active running state.

1b. AUDIO: pactl will start pipewire/pipewire-pulse/pulseaudio if stopped and
not masked, so not using since that would make inxi alter the state of the
system.

1c. AUDIO: pipewire-alsa, pulseaudio-jack depend on file exist globs, tested on
Arch Linux, Debian base, but unknown if paths exist on other Linux pimary
distros. Easy to add to globbing tests, but no going to check them all!

2. SERVICES: systemctl status [service] can fail if service loaded using --user
which is a new one on me, not sure how to handle that.

3. It would be nice to get inxi issues like the sound server/api glitches
handled by filing an issue on inxi github, and not to rely on my seeing a random
distro forum post, which I only found by pure coincidence.

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

1. AUDIO: See Fixes 3a,b,c. In some cases false report of pulseaudio and
pipewire running: yes create unclear output and results, or misleading. Thanks
to manjaro users to noticing this and mentioning it in a forum post.

Note: it's much more effective to file issues on inxi github than to hope I will
see a random forum post one day.

2. DEBUGGER: Bug in debugger, somewhere introduced '-- list' (instead of
'--list') for bluetoothctl which made older systems hang when running the
debugger. No idea when or how that space got introduced.

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

1. INFO: Compilers showed Compilers: gcc: N/A when clang/gcc not installed, this
was not intended, but was a small glitch in main::get_gcc_data(), where it
assigned undef as array contents when gcc not defined. This was exposed by
Chimera, which uses clang, but would have happened any time gcc not installed on
system.

2. SYSTEM: tiny fix, was getting ',' at end of kernel compiler version.

3a. AUDIO: For pipewire, made process detection test more robust, now excludes
pipewire-pulse in case where that might be running without pipewire on/enabled.

3b. AUDIO: bigger fix, more robust tests for audio servers running for jack,
pipewire, pulseaudio, these look for more explicit server tool reports. Certain
not to be reliable always, and fail for superuser, will probably need more
tweaking. Also notes for jack, pulse, pipewire if only positive detection found
via ps aux: active (process) to avoid incorrect data, and root specific messages
depending on situation.

3c. AUDIO: was testing for pactl to determine if pulseaudio installed, but found
case where pactl could be installed without pulseaudio. Now tests for pulseaudio
installed.

3d. AUDIO: weak fix for Linux OSS4 version, using /etc/oss4/version.dat file,
which may or may not exist on all distros.

3e. AUDIO: alsa-oss compat can create /dev/sndstat file, which would then lead
to positive OSS detection even if it's not present. This is corrected, and will
not show if asound/version exists and no ossinfo. For linux, relying on ossinfo
presence, which comes from oss4-base.

3f. AUDIO: Older ALSA /proc/asound/version had a date string in parentheses
after the Driver Version, so now explicitly get the string after Version.

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

1. REPOS: added support for /etc/apk/repositories.d/*.list, which works pretty
much the same as /etc/apt/sources.list.d/*.list. This is to make Chimera apk
repos show up, previously only supported /etc/apk/repositories file read.

2a. DistroData: Added Feren to distro system base. This was much trickier than
it should be due to inconsistent use of os-release field names, but that's how
it goes.

2b. DistroData: new Arch derived distro XeroLinux added to system base. I know,
I know, it's a never-ending endeavor (get it?) since these pop up all the time,
but might as well add them now and then as they appear.

3a. AUDIO: inxi now handles pipewire-pulse as top layer audio daemon, along with
several other server/api helpers. Note that pw-jack does not appear to be a
daemon, just a plugin, so shows 'plugin'. Extra sound server helpers added when
discovered or requested.

  API: ALSA
    v: k5.19.0-16.2-liquorix-amd64
    status: kernel-api
  Server-1: PulseAudio
    v: 16.1
    status: off (on pipewire-pulse)
  Server-2: PipeWire
    v: 0.3.65
    status: active
    with:
      1: pipewire-pulse
        status: active
      2: pw-jack
        type: plugin

3b. AUDIO: For -Aa, added tools: report. Currently supports these basic tools:

alsa: alsamixer alsamixergui amixer
jack: cadence jack_control jack_mixer qjackctl
oss: dsbmixer mixer ossinfo ossmix ossxmix vmixctl
nas: auctl auinfo
pipewire: pw-cat pw-cli wpctl) [+pactl if pipewire-pulse and no pulseaudio
pulse: pacat pactl pamix pamixer pavucontrol pulsemixer
roar: roarcat roarctl
sndiod: aucat midicat mixerctl sndioctl

Note that inxi-perl/docs/inxi-audio.txt has lists of alternates or rejected
helpers and tools, but we want to keep that output short and sane.

3c. AUDIO: For BSDs, if sndiod is detected, adds an API line for sndio. Note
this may create 2 API lines for FreeBSD using OSS.

3d. AUDIO: Added basic support for roar sound server, NAS (Network Audio
System).

4. CPU: new Intel and AMD cpu model matches for latest and future, Luna Lake,
Zen 4c.

5. GRAPHICS: new nvidia current, AMD, and Intel GPU ids.

6. DRIVES: more disk vendors, ids! The list never stops, but sadly, so many are
not identifiable. Check: inxi-perl/tools/lists/disks_unhandled to see if you
can positively identify any of those.

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

1a. AUDIO: Changed main API/Server running: to status: [status], that syntax is
more able to handle different circumstances.

1b. AUDIO: With change to status:, now uses granular fixes above, and adds root
notes if no active detections.

1c. AUDIO: Changed 'Sound API', 'Sound Server' to 'API', 'Server'. This avoids
ambiguity with some types, it's the Audio section, and those are the APIs and
Servers for that Audio section. Makes it match Graphics as well. and is shorter.

1d. AUDIO: Changed 'Sound Interface' for sndiod to 'Server', which is how it's
listed, and for BSD, added API: sndio item. Also changed 'sndio' to 'sndiod' for
the Server: item.

1e. AUDIO: Changed ALSA/BSD sndio to show: status: api since saying an api
is running makes little sense, it's there or it's not there. OSS can be enabled
or disabled so shows status: active/off for Linux, but kernel-api for BSDs.

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

1a. MAN: Added note for helpers item: with: pipewire-pulse/pw-jack etc to -Axx.

1b. MAN: Added -Aa item for audio server tools.

2. OPTIONS: Updated for -Axx helpers, -Aa tools.

3. DOCS: Created inxi-perl/docs/inxi-audio.txt doc file. Too many odd factoids
to forget about during this upgrade!

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

1. REPOS: Moved %keys to %repo_keys and set it only once with set_repo_keys(),
those big hash assigns per iteration are really expensive, now stores it
globally in RepoItem and sets only once.

2. INFO: main::get_gcc_data() failed to handle case where there is no gcc at all
installed, resulted in returning an array with content of 'undef', not an empty
array as intended. This made the array not set test fail for Compilers, so gcc
showed as N/A, which was not intended.

3. DistroData: changed internal lsb/osr $distro to $distro_lsb/$distro_osr,
which lets inxi update the distro name during system base processing in cases
where the data is redundant. Stupid hack, sigh, should not be necessary, but
that's life, /etc/os-release was poorly designed so it leads to such confusions.

4a. AUDIO: Added --dbg 52 to output results of pw-cli.

4b. AUDIO: refactored sound_data, renamed, added {jack,pipewire,pulse}_status(),
sound_helpers(), sound_tools() utilities.

5. DEBUGGER: added more pactl and pw-cli outputs, and pipewire-pulse,
pipewire-jack --version.

6. main::get_driver_modules(): add space after ',' if total string > 40
characters to allow splitting very long unbroken strings of modules that
otherwise would not break as expected.
 2023-03-28 14:48:52 -07:00
5 changed files with 6970 additions and 2047 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'.

6903
inxi
View file

File diff suppressed because it is too large Load diff

428
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\-02\-07" "inxi" "inxi manual"
.TH INXI 1 "2023\-10\-31" "inxi" "inxi manual"
.SH NAME
inxi \- Command line system information script for console and IRC
@ -128,8 +128,26 @@ keep things simple.
.TP
.B \-A \fR, \fB\-\-audio\fR
Show Audio/sound device(s) information, including device driver. Show running
sound server(s). See \fB\-xxA\fR to show all sound servers detected.
Show Audio/sound device(s) information, including device driver. Shows active
sound API(s) and sound server(s).
Supported APIs: ALSA, OSS, sndio. Supported servers: aRts (artsd), Enlightened
Sound Daemon (esound, esd), JACK, NAS (Network Audio System, nasd), PipeWire,
PulseAudio, RoarAudio, sndiod.
Use \fB\-Ax\fR to show all sound APIs/servers detected, including inactive,
\fB\-Axx\fR to see API/Server helper daemons/plugin/modules, and \fB\-Aa\fR to
see API/sound server tools.
.nf
\fBAudio:
Device\-1: C-Media CMI8788 [Oxygen HD Audio] driver: snd_virtuoso
Device\-2: AMD Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series]
driver: snd_hda_intel
Device\-3: AMD Family 17h HD Audio driver: snd_hda_intel
API: ALSA v: k5.19.0\-16.2\-liquorix\-amd64 status: kernel\-api
Server\-1: PulseAudio v: 16.1 status: active\fR
.if
.TP
.B \-b \fR, \fB\-\-basic\fR
@ -225,7 +243,7 @@ Sample:
.TP
.B \-d \fR, \fB\-\-disk\-full\fR,\fB\-\-optical\fR
Show optical drive data as well as \fB\-D\fR hard drive data. With \fB\-x\fR,
Show optical drive data as well as \fB\-D\fR HDD/SSD drive data. With \fB\-x\fR,
adds a feature line to the output. Also shows floppy disks if present. Note
that there is no current way to get any information about the floppy device
that we are aware of, so it will simply show the floppy ID without any extra
@ -233,9 +251,9 @@ data. \fB\-xx\fR adds a few more features.
.TP
.B \-D \fR, \fB\-\-disk\fR
Show Hard Disk info. Shows total disk space and used percentage. The disk used
percentage includes space used by swap partition(s), since those are not usable
for data storage. Also, unmounted partitions are not counted in disk use
Show HDD/SSD drive info. Shows total drive space and used percentage. The drive
used percentage includes space used by swap partition(s), since those are not
usable for data storage. Also, unmounted partitions are not counted in drive use
percentages since inxi has no access to the used amount.
If the system has RAID or other logical storage, and if inxi can determine
@ -252,17 +270,17 @@ Without logical storage detected:
\fBLocal Storage: total: 2.89 TiB used: 1.51 TiB (52.3%)\fR
Also shows per disk information: Disk ID, type (if present), vendor (if
detected), model, and size. See \fBExtra Data Options\fR (\fB\-x\fR options)
and \fBAdmin Extra Data Options\fR (\fB\-\-admin\fR options) for many more
features.
Also shows per drive information: Disk ID, type (FireWire, Removable, USB if
present), vendor (if detected), model, and size. See \fBExtra Data Options\fR
(\fB\-x\fR options) and \fBAdmin Extra Data Options\fR (\fB\-\-admin\fR options)
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.
@ -339,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.
@ -369,12 +388,10 @@ Show Information: processes, uptime, memory, IRC client (or shell type if run
in shell, not IRC), inxi version. See \fB\-Ix\fR, \fB\-Ixx\fR, and \fB\-Ia\fR
for extra information (init type/version, runlevel/target, packages).
Note: if \fB\-m\fR is used or triggered, the memory item will show in the main
Memory: report of \fB\-m\fR, not in \fB\Info:\fR.
Note: if \fB\-m\fR or \fB\-tm\fR are active, the memory item will show in the
main Memory: report of \fB\-m\fR/\fB\-tm\fR/, not in \fB\Info:\fR.
Raspberry Pi only: uses \fBvcgencmd get_mem gpu\fR to get gpu RAM amount, if
user is in video group and \fBvcgencmd\fR is installed. Uses this result to
increase the \fBMemory:\fR amount and \fBused:\fR amounts.
See \fB\-m\fR for explanation of \fBMemory:\fR fields and values..
.TP
.B \-j\fR, \fB\-\-swap\fR
@ -401,7 +418,10 @@ generally shows BusID / DeviceID (except for tree view, which shows ports).
Examples: \fBDevice\-3: 4\-3.2.1:2\fR or \fBHub: 4\-0:1\fR
The \fBrev: 2.0\fR item refers to the USB revision number, like \fB1.0\fR or
\fB3.1\fR.
\fB3.1\fR.
Use \fB\-Jx\fR for basic Si base 10 bits/s speed, \fB\-Jxx\fR for Si and IEC
base 2 Bytes/s speeds. \fB\-Ja\fR adds USB mode.
.TP
.B \-l \fR, \fB\-\-label\fR
@ -497,7 +517,7 @@ to permit dmidecode to read \fB/dev/mem\fR as user. \fBspeed\fR and
\fBbus\-width\fR will not show if \fBNo Module Installed\fR is found in
\fBsize\fR.
Note: If \fB\-m\fR is triggered RAM total/used report will appear in this
Note: If \fB\-m\fR is triggered RAM available/used report will appear in this
section, not in \fB\-I\fR or \fB\-tm\fR items.
Because \fBdmidecode\fR data is extremely unreliable, inxi will try to make
@ -515,9 +535,9 @@ Under dmidecode, \fBSpeed:\fR is the expected speed of the memory
is what the actual speed is now. To handle this, if speed and configured speed
values are different, you will see this instead:
\fBspeed: spec: [specified speed] MT/S actual: [actual] MT/S\fR
\fBspeed: spec: [specified speed] MT/s actual: [actual] MT/s\fR
Also, if DDR, and speed in MHz, will change to: \fBspeed: [speed] MT/S
Also, if DDR, and speed in MHz, will change to: \fBspeed: [speed] MT/s
([speed] MHz)\fR
If the detected speed is logically absurd, like 1 MT/s or 69910 MT/s, adds:
@ -525,7 +545,8 @@ If the detected speed is logically absurd, like 1 MT/s or 69910 MT/s, adds:
.nf
\fBMemory:
RAM: total: 31.38 GiB used: 20.65 GiB (65.8%)
System RAM: total: 32 GiB note: est. available: 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 type: DDR3 size: 8 GiB speed: 1600 MT/s (800 MHz)
Device\-2: DIMM_A2 type: DDR3 size: 8 GiB speed: spec: 1600 MT/s (800 MHz)
@ -538,6 +559,50 @@ If the detected speed is logically absurd, like 1 MT/s or 69910 MT/s, adds:
See \fB\-\-memory\-modules\fR and \fB\-\-memory\-short\fR if you want a
shorter report.
Notes on \fBSystem RAM:\fR / \fBMemory:\fR report item:
* \fBtotal:\fR and \fBigpu:\fR do not show for short form.
* The \fBtotal:\fR can come from several possible sources:
\- If not superuser, and if \fI/sys/devices/system/memory\fR exists, it will
estimate the total RAM based on how many RAM blocks and their size. Sometimes
the block count is not an exact match to installed RAM, and inxi will attempt to
guess the actual RAM amount, except for virtual machines. When it synthesizes
the actual physical RAM total, it will show \fBnote: est.\fR.
Note that not all kernels are compiled to support generating this /sys
directory (kernel needs to be compiled with \fBCONFIG_MEMORY_HOTPLUG\fR).
\- For OpenBSD and not superuser, the total comes from the detected RAM in
dboot, if available.
\- If superuser, and if \fB\-m\fR used, it comes from the dmidecode RAM totals
if available, and if not, it comes from counting up the System RAM ranges in
\fI/proc/iomem\fR (Linux only), then rounding up, since that total is usually
slightly under the actual physical RAM total. If inxi is unsure about the total,
it will show \fBnote: est.\fB.
If no total data found, shows \fBtotal: N/A\fB.
* The \fBavailable:\fR item is the total installed RAM minus some reserved and
kernel code RAM (and in some cases iGPU assigned main system RAM) that is
allocated on system boot, and thus is generally less than the actual physical
RAM installed. This is called MemTotal in free/meminfo even though it isn't,
though it is the total available the kernel has to work with.
* The \fBused:\fR is the percent of the available RAM used, NOT of the total
physical RAM.
* The \fBigpu:\fR item either comes from Raspberry Pi gpu RAM, or from
\fI/proc/iomem\fR. The latter source is Linux + superuser only, and is not
guaranteed to be accurate, but sometimes is. That is for iGPU system RAM used,
not for standalone GPUs with their own internal RAM. Not all types of internal
VRAM are detectable, it depends on how the hardware assigns RAM to iGPU.
Raspberry Pi uses \fBvcgencmd get_mem gpu\fR to get gpu RAM amount, if
user is in video group and \fBvcgencmd\fR is installed.
.TP
.B \-\-memory\-modules\fR, \fB\-\-mm\fR
Memory (RAM) data. Show only RAM arrays and modules in Memory report.
@ -633,13 +698,15 @@ 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)
\fBEOPKG\fR (Solus)
\fBNETPKG\fR (Zenwalk/Slackware)
\fBNIX\fR (NixOS + other distros as alternate package manager)
\fBPACMAN\fR (Arch Linux, KaOS + derived versions)
@ -654,10 +721,18 @@ APT distros like PCLinuxOS or Alt\-Linux)
\fBPORTS\fR (OpenBSD, FreeBSD, NetBSD + derived OS types)
\fBSBOPKG\fR (Slackware + derived versions)
\fBSBOUI\fR (Slackware + derived versions)
\fBSCRATCHPKG\fR (Venom + derived versions)
\fBSLACKPKG\fR (Slackware + derived versions)
\fBSLAPT_GET\fR (Slackware + derived versions)
\fBSLPKG\fR (Slackware + derived versions)
\fBTCE\fR (TinyCore)
\fBURPMI\fR (Mandriva, Mageia + derived versions)
@ -746,6 +821,8 @@ Make sure that there is no space between letters and numbers (e.g. write as
If the \fB\-I\fR or \fB\-m\fR lines are not triggered, will also show the
system RAM used/total information.
See \fB\-m\fR for explanation of \fBSystem RAM:\fR fields and values.
.TP
.B \-t cm\fR
\- CPU+memory. With \fB\-x\fR, shows also CPU or memory for that process on
@ -764,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
@ -816,7 +915,7 @@ min/max speeds, if available) + \fB\-G\fR + basic Disk + \fB\-I\fR.
.TP
.B \-v 4
\- Adds partition size/used data (\fB\-P\fR) for (if present): \fB/ /home /var/
/boot\fR. Shows full disk data (\fB\-D\fR)
/boot\fR. Shows full drive data (\fB\-D\fR)
.TP
.B \-v 5
@ -1185,7 +1284,7 @@ vendor [product] information.
\- Adds PCI/USB ID of each device.
\- Adds non-running sound servers, if detected.
\- Adds inactive sound servers/APIs, if detected.
.TP
.B \-x \-B\fR
@ -1269,7 +1368,7 @@ doas users: see \fBman doas.conf\fR for setup.
You can force use of \fBhddtemp\fR for all drives using \fB\-\-hddtemp\fR.
\- If free LVM volume group size detected (root required), show \fBlvm-free:\fR
\- If free LVM volume group size detected (root required), show \fBlvm\-free:\fR
on Local Storage line. This is how much unused space the VGs contain, that is,
space not assigned to LVs.
@ -1282,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
@ -1295,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
@ -1349,15 +1452,21 @@ discover those.
available.
.TP
.B \-x \-j\fR, \fB\-x \-\-swap\fR
.B \-x \-j\fR (\fB\-\-swap\fR)
Add \fBmapper:\fR. See \fB\-x \-o\fR.
.TP
.B \-x \-J\fR (\fB\-\-usb\fR)
\- For Devices, adds driver(s).
\- Adds, if available, USB speed in base 10 bits/s (Si) units \fBMb/s\fR or
\fBGb/s\fR (may be incorrect on BSDs due to non reliable data source). These are
base 10 bits per second. This unit corresponds to the standard units the USB
consortium uses to indicate speeds, but not to how most of the rest of your
system reports sizes. Use \fB\-Jxx\fR to add base 2 IEC Byte/second speeds.
.TP
.B \-x \-L\fR, \fB\-x \-\-logical\fR
.B \-x \-L\fR (\fB\-\-logical\fR)
\- Adds \fBdm: dm-x\fR to VG > LV and other Device types. This can help
tracking down which device belongs to what.
@ -1433,15 +1542,22 @@ found for each distribution system base detection.
\- Adds PCIe speed and lanes item (Linux only, if detected).
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
\- Adds \fBwith: [item] \fBstatus: [state/plugin]\fR helper daemons/plugins for
the sound API/server.
.TP
.B \-xx \-B\fR
\- Adds current power use, in watts.
\- Adds serial number.
.TP
.B \-xx \-D\fR
\- Adds disk serial number.
\- Adds HDD/SSD drive serial number.
\- Adds disk speed (if available). This is the theoretical top speed of the
\- Adds drive speed (if available). This is the theoretical top speed of the
device as reported. This speed may be restricted by system board limits,
eg. a SATA 3 drive on a SATA 2 board may report SATA 2 speeds, but this is
not completely consistent, sometimes a SATA 3 device on a SATA 2 board reports
@ -1458,18 +1574,22 @@ For a PCIe 3 NVMe drive, with speed of \fB8 GT/s\fR and \fB4\fR lanes
\fBspeed: 31.6 Gb/s lanes: 4\fR
\- Adds disk duid, if available. Some BSDs have it.
\- Adds HDD/SSD drive duid, if available. Some BSDs have it.
\- Adds for USB drives USB rev, speed, lanes (lanes Linux only).
.TP
.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.
@ -1497,6 +1617,8 @@ or more \fBMonitors\fR.
\- Adds PCIe speed and lanes item (Linux only, and if PCIe device and detected).
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
\- Adds output port IDs, active, off (connected but disabled, like a closed
laptop lid) and empty. Example:
@ -1558,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
@ -1589,8 +1715,12 @@ swap types (for \fB\-j\fR).
.B \-xx \-J\fR (\fB\-\-usb\fR)
\- Adds vendor:chip id.
\- Adds USB lanes. Uses tx (transmit) lane count for total unless rx and tx
counts are different (eg: \fBlanes: rx: 2 tx: 4\fR). Linux only.
See \fB\-Ja\fR for sample output.
.TP
.B \-xx \-L\fR, \fB\-xx \-\-logical\fR
.B \-xx \-L\fR (\fB\-\-logical\fR)
\- Adds internal LVM Logical volumes, like raid image and meta data volumes.
\- Adds full list of Components, sub\-components, and their physical devices.
@ -1627,6 +1757,8 @@ ROM size if using \fBdmidecode\fR.
\- Adds PCIe speed and lanes item (Linux only, and if PCIe device and detected).
\- Adds for USB devices USB rev, speed, lanes (lanes Linux only).
.TP
.B \-xx \-r\fR
\- Adds to \fBPackages:\fR info. See \fB\-Ixx\fR
@ -1701,22 +1833,24 @@ CPU does not support SMT.
.TP
.B \-xxx \-D\fR
\- Adds disk firmware revision number (if available).
\- Adds HDD/SSD drive firmware revision number (if available).
\- Adds disk partition scheme (in most cases), e.g. \fBscheme: GPT\fR.
\- Adds drive partition scheme (in most cases), e.g. \fBscheme: GPT\fR.
Currently not able to detect all schemes, but handles the most common, e.g.
\fBGPT\fR or \fBMBR\fR.
\- Adds disk type (\fBHDD\fR/\fBSSD\fR), rotation speed (in some but not all
cases), e.g. \fBtype: HDD rpm: 7200\fR, or \fBtype: SSD\fR if positive SSD
\- Adds drive tech (\fBHDD\fR/\fBSSD\fR), rotation speed (in some but not all
cases), e.g. \fBtech: HDD rpm: 7200\fR, or \fBtech: SSD\fR if positive SSD
identification was made. If no HDD, rotation, or positive SSD ID found, shows
\fBtype: N/A\fR. Not all HDD spinning disks report their speed, so even if they
\fBtech: N/A\fR. Not all HDD spinning disks report their speed, so even if they
are spinning, no rpm data will show.
.TP
.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
@ -1744,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
@ -1764,8 +1904,6 @@ uses the \fBwhoami\fR test.
\- Adds \fBinterfaces:\fR for non hub devices.
\- Adds, if available, USB speed in \fBMbits/s\fR or \fBGbits/s\fR.
\- Adds, if present, USB class ID.
\- Adds, if non 0, max power in mA.
@ -1809,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,
@ -1847,6 +1987,11 @@ knows could possibly be used instead.
or lanes, \fBlink\-max: gen: speed: lanes:\fR (only items different from primary
shown).
\- Adds list of detected audio server tools (\fBtools: [tools]\fR) to API/Server
lines, like alsamixer, jack_control, pactl, pavuctl, pw-cli, sndioctl, etc.
\- Adds for USB devices USB mode (Linux only).
.TP
.B \-a \-C\fR
.br
@ -2019,8 +2164,11 @@ any further action.
\- Adds, for USB or other external drives, actual model name/serial if
available, and different from enclosure model/serial, and corrects block sizes
if necessary. Adds in drive temperature for some drives as well, and other
useful data.
if necessary.
\- Adds for USB drives USB mode (Linux only).
\- Adds in drive temperature for some drives as well, and other useful data.
.TP
.B \-a \-E\fR (\fB\-\-bluetooth\fR)
@ -2032,6 +2180,11 @@ and Service Classes.
or lanes, \fBlink\-max: gen: speed: lanes:\fR (only items different from primary
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
@ -2054,6 +2207,8 @@ Includes extended non free Nvidia legacy informatin (Linux and Nvidia only), and
issues, shows extra data that can help diagnose/debug. Adds \fBcode:\fR item if
found and not the same as \fBarch:\fR.
\- Adds for USB devices USB mode (Linux only).
.nf
\fBinxi \-Gaz
Graphics:
@ -2100,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
@ -2137,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:
@ -2146,9 +2315,14 @@ 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
.B \-a \-I\fR
\- Adds to Packages number of lib packages detected per package manager. Also
@ -2170,7 +2344,7 @@ rc\-service rcctl service sv /etc/rc.d /etc/init.d\fR. Can be useful to know
which you need when using an unfamiliar machine.
.TP
.B \-a \-j\fR, \fB\-a \-P\fR [swap], \fB\-a \-P\fR [swap]
.B \-a \-j\fR (\fB\-\-swap\fR), \fB\-a \-P\fR [swap], \fB\-a \-P\fR [swap]
\- Adds swappiness and vfs cache pressure, and a message to indicate if the
value is the default value or not (Linux only, and only if available). If not
the default value, shows default value as well, e.g.
@ -2183,10 +2357,48 @@ 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
.B \-a \-L\fR
.B \-a \-J\fR (\fB\-\-usb)\fR
\- Adds, if available, USB speed in IEC units \fBMiB/s\fR or \fBGiB/s\fR (may
be incorrect on BSDs due to non reliable data source). These are base 2 Bytes
per second.
\- Adds USB mode (Linux only), which is the technical terms the USB group uses
to describe USB revisions. In cases where speed and rev are an unknown
combination, (and probably at least one is wrong) shows message.
There are no granular data sources in BSDs for accurate revision/lane/speed
information, so mode cannot be determined.
Sample:
.nf
\fB
Hub\-1: 1\-0:1 info: hi\-speed hub with single TT ports: 14 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip\-ID: 1d6b:0002
class\-ID: 0900
Device\-1: 1-4:2 info: Wacom ET\-0405A [Graphire2 (4x5)] type: mouse
driver: usbhid,wacom interfaces: 1 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s)
lanes: 1 mode: 1.0 power: 40mA chip\-ID: 056a:0011 class\-ID: 0301
Hub\-2: 2\-0:1 info: Super\-speed hub ports: 8 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen\-2x1 chip\-ID: 1d6b:0003
class\-ID: 0900
Device\-1: 2\-8:5 info: SanDisk Ultra type: mass storage driver: usb\-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen\-1x1
power: 896mA chip\-ID: 0781:5581 class\-ID: 0806
serial: <filter>\fR
.fi
.TP
.B \-a \-L\fR (\fB\-\-logical)
\- Expands Component report, shows size / maj-min of components and devices, and
mapped name for logical components. Puts each component/device on its own line.
@ -2208,6 +2420,8 @@ knows could possibly be used instead.
or lanes, \fBlink\-max: gen: speed: lanes:\fR (only items different from primary
shown).
\- Adds for USB devices USB mode (Linux only).
.TP
.B \-a \-o\fR
\- Adds device kernel major:minor number (Linux only).
@ -2243,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.
@ -2298,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
@ -2339,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.
@ -2347,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.
@ -2397,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
@ -2529,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.
@ -2578,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
@ -2896,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:
@ -2906,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).

1523
inxi.changelog
View file

File diff suppressed because it is too large Load diff